Tag Archives: Adobe

Coolness from Adobe

Today, Adobe announced that the release of Photoshop CS5 is imminent. That’s cool.

What’s even cooler is that it looks like Adobe has now created a path for upgrades from CS4 Extended to CS5 regular version. That is waaaay cool! I bought the Extended version a while back — CS3, I think — and have found that I’m really not using the “extended” parts. The downside was that there was no real way to upgrade numeric versions from a downlevel Extended to an uplevel non-Extended version.

Now, it appears that Adobe has solved that little problem, and all is happy in the Deauxmayne!

More on Adobe Camera Raw

After spending most of last weekend playing with various RAW converters — both for output and speed — I finally believe I found the foundational problem in my workflow. ACR was defaulting to Adobe Standard as the camera profile. There were also some other settings that needed tweaking as my defaults, but this was the root of my evil problems. I remember long ago making a change in ACR that had things coming out of it looking good, but somehow with the loading of ACR 5.6, my settings went bye-bye. Or it could’ve been the addition of images from my new 7D. No matter, it’s more or less resolved now. (Thanks Tim!) [BTW, Tim is also doing a Project 365 exercise.]

Of course, ACR can do tons to the image, and this weekend, I swallowed my ignorance, and purchased Real World Camera Raw with Adobe Photoshop CS4. I’ve plowed through the foundational chapters, not yet touching a single control. But that day is coming, and I really do feel more confident in treating ACR as another tool in the workflow, rather than a Ron Popeil “set it and forget it” gateway through which my RAW images stroll.

Canon 7D and Software Updates

Having had my Canon 7D for a few weeks, I can safely say that I really like it. Not yet love it, but I like. Why not love? Well, I just haven’t had enough time to exercise it enough to fall in love. I’m in love with its potential, but I haven’t realized that potential practically yet. Mine own dang fault… along with the fact that there’s only 24 hours in a day. Dumb ol’ plantary rotation.

One thing that frankly had kinda slowed me down from getting too far down the path for making gobs of shots was that Apple’s Snow Leopard and Adobe products weren’t quite there with support for the new RAW format from the 7D. There’s been a release candidate for Lightroom that supported it, but after reading some of the forum info about that RC, I was concerned that I might end up having to re-import my images or some such nonsense to get them correctly rendered in the future production version of LR when it was released.

Today, both issues are solved: Adobe has released LR 2.6 officially, and Apple has update Snow Leopard to handle the 7D’s RAW files. Both are great news for me, and just in the nick of time.

Tomorrow morning, a gaggle from work are getting together at Forest Park to photograph, and it’ll be the first real world test for me with the 7D. Now that my tools are up to snuff for reading the images I’ll create, that just makes the pot sweeter. Woo-hoo!

I’d be remiss if I didn’t put my Grandpa Simpson voice on and mention the speed of the upgrades. I was downloading the almost 100MB upgrade to Lightroom at just a tick over 1MB/sec. That would’ve been just about one 3.5″ floppy disk every second for just under two minutes. It’s crazy to think about moving that kind of data around that quickly. And man, am I loving it!

Now to go to the camera store and see if there’s any used lenses I need! 🙂

Snow Leopard! Genuine Fractals! Oh, the Humanity!

I was sitting around today, when my iPhone jingled, telling me that I’d received an e-mail. It was a monthly newsletter from OnOne about their products. I’m a Genuine Fractals 6 Professional user. I don’t use it real often, but when I do, I need it.

So what was the topmost bullet in the newsletter? A strong suggestion to deactivate OnOne products before upgrading OS X to Snow Leopard. Eh? Really?

And with my next breath, I realized that the newsletter was telling me that GF6 was not going to work until I contacted customer support. Period. Oh fudge. Only I didn’t say fudge.

Being in Missouri, there was a healthy dose of “show me”, and I tried GF6 in Photoshop CS4E and Lightroom 2.5… no dice. What I read was right — I was hosed.

So now I’m waiting for OnOne to respond with a hopefully painless way to salvage my investment in GF6.

Frankly, activation that is that deeply rooted in the OS seems a little overboard. The product’s great — nothing else can touch it — so I suppose it’s worth the pain, but I’m blown away that an OS upgrade can cause this kind of problem. Sure wish I’d had this info before I’d done the upgrade — and I’m betting that OnOne does too. It looks like they’re fielding quite a few questions on this one.

Stay tuned.

The Patient Survived!

Doc Oc has his new OS and apps loded. Yahoo! In this entry, I’m gonna try to capture the things I’ve modified/augmented, so next time I have to do this, I can deal with it from a documented position.

My basic plan was to keep things clean, only installing things I use, and trying hard to avoid importing settings and drivers from the old boot drive, which takes the Migration Assistant out of the mix… generally.

  • >Documents and Stuff : I have loads of this kind of thing… ya know, Apple commercials, some images (not my photo library; that’s on another spindle), genealogy stuff, etc. Migration Assistant seemed like it would move all this, but I really wanted to do it myself, as I’m not comfortable with Migration Assistant’s scope, and knowing just much it would copy.
  • Mail : Mail is a biggie for me. I archive waaaaay too much mail in my mailboxes, and it’s always been one of those things I’ll fix “one of these days”. Today is not that day. So how to get my mail setup manually? I copied /Users/me/Library/Mail and /Users/me/Library/Mail Downloads to the newly installed OS image. I also copied /Users/me/Library/Preferences/com.apple.mail.plist, and after getting everything over, I opened Mail, and there was everything. The only thing that wasn’t in place was my passwords, which isn’t a big surprise.
  • Adobe Applications : I fully expected CS3 to bark about being reinstalled on the same machine, but apparently it was smart enough to figure it out. I saw several other apps that somehow knew their license serial numbers, and worked well. In fact, the only app that I had to “deactivate” and “reactivate” was Genuine Fractals 6.
  • iTunes : I have had challenges in the past with moving my iTunes library around. This go ’round though, I had no problems. I use an alias to point to the library location, and once I repointed that, iTunes was all smiles.

At this point, Doc is happy again, although I’m sure I’ll run into things here and there that aren’t quite as they were. However, all things considered, I’m happy with where things are right now… Especially given all the “learning experiences” that were part of this!!

Adobe, CS4, CS4E and 64 Shiny Glorious Bits

This week was full of announcements about the forthcoming Adobe Creative Suite releases. To me, the important part of that gaggle o’ code is Photoshop CS4 and Photoshop CS4 Extended (CS4E). I picked up CS3E less than a year ago, taking advantage of an upgrade path from CS2 to CS3E for a premium cost over an CS2 to CS3 upgrade. More on that later.

With the announcements came the confirmation that CS4/CS4E on the Mac platform will still only be 32-bit. I lamented about this a while ago, but it’s worth mentioning again that I’m not happy about being boxed in to only 4GB of addressable memory space. Nothing I’m doing right now is using anything beyond a GB of RAM, so it’s not the end of the world… yet. Adobe is dismissing this as a non-issue, as they measure the impact with an eye toward speed. Speed is great, and I want all of that I can get, but I also want to have wide, green pastures available to me, even if I don’t use it all. 64 bits of addressing would definitely help.

The other interesting thing about the new Photoshop is utilization of hardware acceleration on the graphics card for a variety of typical tasks. However, it kinda reads that the Nvidia cards (GeForce and Quadro) are the favored cards. I’m still trying to see if there’s any benefit from my stock ATI Radeon HD 2600 XT card. To upgrade the video card, Apple sells the Nvidia GeForce 8800 GT (512MB) for close to $300; a Quadro is easily twice that. Unless my card will drag some love out of Adobe, I’m probably outta luck on getting any benefit from this upgrade.

This release is the first upgrade to the CS Extended environment, and I expected to see a similar price for CS3E to CS4E as there is from CS3 to CS4. That ain’t the case. CS3 to CS4 is $199, but the move to CS4E from CS, CS2, CS3 or CS3E is $349! I already paid that version change tax once, and it’s ludicrous of Adobe to expect that same path to be paved in my gold twice, especially when there’s not that much benefit in the CS Extended versions for me… for now.

With the lack of functional benefit for me, the appearance that the hardware accelerator may pass me by, the lack of 64-bit love, and the crazy upgrade policy, I believe I’ll end up waiting for CS5E, and see if the pot’s a bit sweeter.

Bad Adobe, Good Adobe

I can always tell when something is happening out in the wastelands of the tech world. NewsFire will be screaming at me with multitudes of new feed-matter. Tonight, NewsFire was definitely screaming, and Adobe figured prominently in two threads of thought and chatter.

The first was the Good News. Adobe released the first public beta of Lightroom 2.0. This is claimed to be 64-bit ready code, and chocked full of new features. I haven’t had a chance to load it yet — I wanna see if there’s any caveats about keeping a separate library, etc. You can bet I’ll be playing with it this weekend, and seeing what I can do with it. Currently, I only use Lightroom for DAM, and really don’t use it for quick touches, printing, web site building, and all that other good stuff it does well. Casey keeps nudging toward using it for more than just that. His site is mostly built with Lightroom, and it looks pretty dang good. That’s a pretty good endorsement.

And then came the Bad News. Adobe released some word on the Next Big Thing: Photoshop CS4. (And the crowd goes wild…) And it’ll be 64-bit…. (wait for it)… if you’re on Windows. Yep, the big ol’ Macs like mine will still have to contend with 4GB of memory for the beastliest images we can put together, with our Windows-based brethren able to address vast amounts of memory. From this interview, the guess is that the performance boost would be in the neighborhood of 10 percent, unless of course you’re loaded gigapixel sized images where, with enough memory, the 64-bit version could be 10 times faster!

One path to get around this is to dual boot the Octoputer, running 64-bit Vista (Adobe says that’ll be the supported platform). That would be just like a native Windows machine, but would require me to purchase a new Photoshop license. Currently, I don’t believe Adobe allows you to upgrade version and change platforms in the same fell swoop. The other path to get tasty 64-bit goodness would be to virtualize a 64-bit Vista environment through VMWare (Parallels doesn’t currently support this), and run CS4 in that environment. The big question there is whether you’d burn up the benefit of the 64-bit code by virtualizing it.

So in one day, Adobe delivers both Good stuff and Bad stuff. I’m not sure whether I should be happy or mad. Or both. Or neither.

Wait for it… and the crowd goes “boooooo”

Adobe Giveth, and Adobe Taketh Away

OK, color me gullible, color me masochistic, color me with rose-tinted glasses, but when a software update is released, I kinda expect it to work reasonably well. I don’t expect the update to be pulled, and I don’t expect me to have to uninstall an app and re-install just to recover.

On the 13th, Adobe released a new version of Camera Raw and an update to Lightroom. Neither of these had earth-shattering implications for me, but I try to stay pretty current on things, just in case. In my world at work, the first question the dude in support asks you is if you have the latest versions of everything, so that flavors my judgement to trust the vendors when they release patches and fixes. So, swallowing the Kool-Aid, I pounced on the upgrades, and loaded them on both Doc Oc and the Little MacBook That Could.

Fast forward to today, and there’s word all over the place about both packages being pulled, and how it’s necessary to uninstall Lightroom to downgrade to the previous version. Now admittedly, that’s not a tough thing, but that ain’t right!

So tonight, it’s the uninstall-o-rama, along with the downgrade-o-rama, and a little bit trepedation of whether I’ve hurt anything by using the new version, and whether I’m gonna lose anything by performing the surgery necessary to fix the fumble by Adobe.

In their defense, Adobe usually does a good job of keeping things on the right side of the error-line. Why two packages released together would be withdrawn so quickly is beyond me, but I’ve gotta hope that the next update will go a little better!

A 40D Wart

Having shot almost a week’s worth of random shots with the new rig, all is well on the rig side. The computer side… well, that’s another story.

Adobe quickly released Adobe Camera Raw 4.2 to quieten the screaming hordes that had bought a shiny new 40D, only to discover that none of the Adobe suite of products would read anything other than the jpegs coming from the camera. And all was well — jpegs and RAW files were importing just fine — or so I thought.

The problem is that ACR doesn’t work with the new sRAW files the 40D can produce, which means that neither Photoshop nor Lightroom can read ’em. These funny little files are getting a lot of press as being a quick-and-dirty RAW format for folks that don’t need big file sizes, but need some of the advantages of RAW. It’s a nifty idea that may be ideal for some folks. However, neither the Adobe line, nor my Mac’s Preview, will display them at all. Heck, the Mac still can’t display a 40D RAW file in Preview!

These are just growing pains, and this too shall pass, but you’d think that Adobe, Apple and Canon would at least have had a powwow prior to the camera hitting the street!

So, for those of you looking for images shot since I picked up the 40D, you may have to wait a bit. My automation is really tied to ACR, and if it can’t read some of the files that I’ve shot, I’ll just have to re-import ’em again, and I’d really rather not do that. Thanks for your patience!