CreativeBloq: New version of Photoshop is less likely to crash.
The update seems to have restored my OpenCL behavior to normal. I’ll know more tonight, after the day’s photo.
Later: Nope, still throws the error. Damn.
BonjourLife: Shortcut-S Photoshop Keyboard.
That, and a Wacom tablet, and you’d be set. Maybe. I spend more time screwing with brush sizes and specs, which I don’t see on this ‘board.
Julieanne Kost’s Blog: Creating Collections within Collection Sets in Lightroom.
Huh? I had no idea you could do this.
“Flash Player Update … please quit:”
A little red ‘x’ next to Safari. While I’m running Chrome. Confidence-inspiring.
DP Review: 10 essential time-saving Photoshop tips.
Once you use them, and get a benefit in speed/usability, you’ll remember ‘em.
OpenCL error message in latest Photoshop update.
Anyone else getting “OpenCL” errors? They just started to occur. I took graphics card performance down to “normal”, and it’s still happening. Whenever I open a JPG.
Macworld Bugs & Fixes: Stop Adobe Reader from blocking PDFs in Safari.
DesignYourWay: Tools For Photoshop.
Yeah, yeah, yeah … one of those sites. There were some tools here I hadn’t come across before. So I thought I’d share.
SmashingMag: The Present And Future Of Adobe Fireworks.
Try as I might, I never got on with Fireworks. It felt dated very swiftly, though it (still) hides great power. Modernize the UI, it would still be useful.
Adobe/Richard Curtis: Creative Cloud Desktop App, version 18.104.22.1682.
Julieanne Kost’s Blog: Docking Tools and Panels in Photoshop.
Docking panels on the left? Weirdsville. Gotta try it.
John Nack on Adobe: Russell Brown’s new Layer Namer for Photoshop.
Interesting. There are other plugins that do this sort of thing, too, but for a premium price.
Lightroom Killer Tips: Bringing Back The Old Fill Light Slider in Lightroom 5.
Every tool is useful; even if ‘old’.
Blogs.Adobe.com: Editing your pictures with local adjustments using Lightroom.
These are techniques I use on all my photos. If you’re not familiar with ‘em all, this is a really good short overview of the astonishing things you can do to improve a mundane image. [Just be bloody careful about overexposing shadow areas, and always check 1:1 before publishing!]
Another Creative Cloud App update.
One crash, one successful install, for a total of two attempts. Second time in a row. C’mon Adobe … you can get it down to one successful install, I know you can.
Lightroom workflow change.
In the past, I’ve just imported .CR2’s (Canon Raw Format) and done my work in Lightroom. I heard a rumor, and performed a small test over the weekend. DNG’s are significantly faster to process in Lightroom 5. 5’s been significantly slower on my system than 4, so any speed gain is to the good. DNG’s preview faster, show changes faster - everything’s faster. So now I during import, I copy my original .CR2’s to a separate backup drive, while creating a DNG and using the DNG as my main editable file on my working system. This may cause some backup nightmares, but I’m working that out at the moment. I’ll let you know how I get along with this setup, over the longer term.
CSO: Adobe confirms stolen passwords were encrypted, not hashed.
Ouch. It would be helpful if all online services would tell us how they store our account information now, wouldn’t it? Or some sort of voluntary security body that assigned graphical badges so we could know if a service was using proper programming practices.
Creative Cloud Desktop update improvement.
It only crashed once in the update process - for a total of two tries, second one successful. It was four or five last go-round.
Lightroom Killer Tips: Video – Retouching Tips in Lightroom.
Nice tip … I found this by happenstance over the last couple of weeks.
CNet: Adobe hack attack affected 38 million accounts.
“We have completed e-mail notification of these users. We also have reset the passwords for all Adobe IDs with valid, encrypted passwords that we believe were involved in the incident — regardless of whether those users are active or not.” Erm, I was never notified by email. I received a physical mailed notification that looked like an advertisement. When I received it, I went to Adobe.com immediately, and found they were requiring me to reset my password. Yet I had been running Creative Cloud with my existing password for a few weeks since the hacking.
Whether or not you’ve been notified by Adobe - if you haven’t reset your password, do it now.
Adobe/Curtis: Lightroom 5.2 – Clone/Heal tool feathering.
Yes, but. If that’s going to be enlarged (say, a 16x20 print), I’d sure see it. I’d clone in smaller pieces, using multiple clones to rebuild a coherent root structure, matching the lighting, textures and gradients … and being very wary of ‘soft’ mask edges. If I can barely detect it at 1:1, then it’s OK. I’ll still make a test print to verify.
Lightroom 5.2 update bizarreness.
After my update, it asked for registration information (never done this before). Then, when the interface built onscreen, all my images were gone. Everything. Zip. Zero. Nada. Nothing in Lightroom at all (I knew my images were still on disk - and backed up on external).
I waited. After about three minutes, the images began to show up, folders first. It doesn’t seem to be rebuilding a catalog or anything, but something is getting processed between first startup and display of existing catalogs.
So don’t panic. Just wait.
Creative Cloud is screwed up this morning.
Be patient. Don’t go reinstalling CC.
Later: Mine’s working. Quit CC in the menu bar, restart from the App folder (mine somehow managed to restart an older version at one point). Leave it be so it can synch for a couple of minutes, and your updates should start showing again.
Adobe/Monahan: Enabling CUDA for Premiere Pro and After Effects in the MacBook Pro Retina.
Creative Cloud desktop observations.
Used to be, the desktop app only needed two installs (first always failed) to get it updated. Now I’m up to four installs to get an update applied. That’s a record for software, for me. Trick is, damn the error messages, keep installing. If it quits, restart it, restart the update procedure. When it finally starts and takes a really, really long time to update — that’s the good one.