Photoshop Updates

Adobe Photoshop and Lightroom are a double-act that I can’t really do without where my workflow is concerned. Lightroom is used to organise my raw captures, convert them into perfectly exposed jpegs, and Photoshop is used to blend the exposures together and tidy everything else up, and edit details. The two apps integrate really well, so I’m more than happy to pay the monthly subscription to keep using the ecosystem.

Whenever there’s a major update, there can be glitches in the apps that usually seem to affect the core functions of the programs. The focus on more and more AI features which are there to make shitty images look good is becoming all-consuming at the expense of keeping the software stable.

The major gripe is the common effect on the “edit as layers in Photoshop” command. I use this in every job I do to layer up multiple frames from Lightroom into Photoshop. A javascipt then puts masks on the relevant layers, and blend modes are changed so the file is ready to edit with my style. In previous versions of Photoshop, this function has failed to work at all - forcing me to change back to a previous version until a patch is introduced.

The introduction of Photoshop 27.8 has brought in some weird glitch that causes this process to flash up the previous image I’d imported a few times, then start on the current layering. Consequently, it doubles the time it takes to open the layered files. Not a massive problem in the grand scheme, but it shouldn’t happen seeing as the process has been stable for the past 10 or so updates.

Adobe does has a method of reporting bugs apparently, but I can’t seem to find it. The digital behemoths don’t really want people contacting them in person, so they always hide this sort of stuff behind layers of help pages and forum searches. I managed to force my way to the end of the reporting process, but it turned out that it just creates a post which can be answered by other registered Adobe users - who all seem to be argumentative, “know-it-all” types. Imagine that…..on the internet.

A screen recording of the glitch is shown above.