Month: October 2017

Morro Bay Day 1: Rediscovering Landscape Photography

(Note: All of the images from this trip are available for viewing over on my SmugMug site) As I’ve talked about before, I’ve been struggling to get my photography on track, and while I’m pretty happy with my bird/wildlife work these days, my landscape work has continued to mostly piss me off and feel forced and uninteresting. I finally decided that what I needed to do was go and just take myself back to the basics. Since I recently interviewed for a job that really interested me and I thought I’d done well in interviews, not getting it put...

Read More

Oh no! Adobe changed things on me!

While I was in Morro Bay, Adobe made a bunch of announcements about Lightroom and Photoshop, and I first heard about them when Twitter exploded. I’ve been digging into this to try to make sense of it and how it impacts me, and let me try to summarize what I think right now. Lightroom 6, the standalone/shrinkwrap version, is end of life, which means if you’re still using it or an earlier version of Lightroom than Lightroom CC, it’s time to start thinking about what you want to use instead. It’s dead, Jim and joining Aperture out on the old software farm where it’ll be able to play in the meadows with the other retired software tools like Freehand and Pagemaker. Lightroom CC has been renamed to Lightroom CC Classic, mostly because I think Adobe wanted to confuse us and get us arguing about the name change rather than the underlying product strategies it implies. Lightroom CC is the new thing they’re doing that sucks in Lightroom Mobile and creates a new image processing platform that is very mobile aware and cloud centric. My take, but I admit to just starting to dig into this as I dig out from the trip I just finished, is that other than the name change, if you’re using an Adobe product, nothing really changes (with one exception). So if you went to...

Read More

The “because I’m the mommy” clause

A community I use recently had a problem that wasn’t covered by the Code of Conduct but which a number of members felt required some kind of administrative action. Ultimately the community owner decided they were right and imposed sanctions on another member over the situation. I sent the administrator a private note letting them know I’d have made the same decision and that I’d have felt awful for having to do it. I also mentioned that this is why I like to have a “because I’m the mommy” clause in the code of conducts for communities I manage. A reality of most codes of conduct is they’re backward facing: to some degree, you are attempting to prevent situations that have happened before from happening again, and giving you the opportunity take action when they do happen without a lot of debate. The problem is, as a community grows and matures, the problems that crop up tend to be more complex and nuanced and often aren’t cleanly covered by the CoC, and so it’s in the best interest of the community for the Administrator to have a way to handle those kind of issues without turning every situation into a “this isn’t in the rules” meta debate or a chance for the lawyers to try to argue their way out of a reprimand by nitpicking rule language (which has...

Read More

Moss Landing Harbor August 17: Some days things just click

This is a trip from mid-august that I’m just catching up on image processing for. One reason: it was an extremely successful outing. I went down to Moss Landing to do some experimenting with the autofocus on the X-T2 and because the reports were that a few thousand Elegant Terns had returned from nesting in Mexico and were hanging out. Turns out, they were: I’m really loving the X-T2 and moving to it has been a lot of fun; the much higher megapixel sensor than the X-T1 gives me a lot more crop ability and a lot more detail...

Read More

Be careful about assigning blame until you know what caused the problem

I’ve been running High Sierra on my computers since some of the last developer betas, and for me it’s been working fine. Well, mostly fine. I have been having weird audio cutouts on my bluetooth headset (the Bose QC35), where I’d bring up a video and I’d get no sound, or when watching Youtube, I’d see the pre-roll ad, switch to the video, and have the video start with no sound. To fix it, I had to stop the video, power off the headphones, wait a beat and turn them back on and let them re-pair. Then they’d work for a while (or until the next Youtube video with an ad). Since I’d recently updated to the final GM candidate of High Sierra, I assumed this was a High Sierra bug, because, well, that’s what I changed and then it broke things. I got into a conversation about this on twitter, and found out a few other people were seeing similar problems, and so I assumed that meant High Sierra was broken, end of story. Except… A friend of mine made some suggestions to try to debug it it, and if those failed, file a RADAR on it, so I went digging into the problem. First thing I found was that I hadn’t actually upgraded to the final production release of High Sierra, I was still a release back;...

Read More