Suddenly, Trouble Editing in CS3

  • Thread starter Thread starter KED
  • Start date Start date
Status
Not open for further replies.
K

KED

Guest
I have had LR2 for a long time now, and up until yesterday, have had no issues moving images out to CS3 for editing (although some issues with the return trip but that's a different topic). All of a sudden yesterday, when I click Photo > Edit In > CS3 (my primary external edit option), the command causes CS3 to open, but the image is not exported to it, and LR doesn't even "get out of the way" on the screen. I haven't touched my LR External Editor Preferences, and they are as they should be. Nor can I think of anything else that I have changed anywhere recently.

Any thoughts on what is going on here?

Addendum: The same issue exists for my secondary editor, PTLens. Invoking the command causes the app to open, but the image is not exported to it (although in this case, LR did make a PSD copy, it just didn't export it.
 
Sort by date Sort by votes
I have had this as well but haven't seen it with 2.1RC, Maybe you want to try that out as well.
 
Upvote 0 Downvote
I have now discovered that this phenomenon relates to files whose metadata has been changed (in my case by geotagging). I cannot begin to fathom the connection!!
 
Upvote 0 Downvote
Kent, don't know if this is pertinent, but here's a thread here at LR forums, halfway down the thread in my post is a link out to the flickr LR forum. It explains dealing with some metadata issues 'Edit in ....' . I don't think that's what's going on with your problem, but maybe it'll spark an idea.
 
Upvote 0 Downvote
Last edited by a moderator:
Upvote 0 Downvote
Brad Snyder said:
duh!

http://www.lightroomqueen.com/community/showthread.php?t=3288&highlight=flickr

And as I said, inside that thread is a link to the flickr forum thread.
Click to expand...
Thanks -- I just checked it and it seems to be a different, though may be related, issue. Lord knows I have brought it to Adobe's attention as well -- kinda got the Heisman treatment from them for any further discussion after their offering up the ubiquitous "CS3-as-Second-External-Editor solution".

I can deal with this. The intersection of shots that I geotag (landscapes, etc.) and those that I micro-edit in CS3 (mostly noise reduction and other plug-ins) is small. It's the intellectual disconnect (between metadata alteration and ability to transition to CS3) that drives me crazy!
 
Last edited by a moderator:
Upvote 0 Downvote
Upvote 0 Downvote
That's pretty sensible as a general rule Kent. That said, 2.1' rc's been out a while now, and it's probably safer than 2.'. Up to you though.
 
Upvote 0 Downvote
Yes, Kent, we have a thread going here, in an 'administrative' forum, and the consensus around 2.1RC is universally positive, with one teensy exception. By design, the mouse scroll wheel no longer moves the sliders, and some folks miss that capability.
 
Upvote 0 Downvote
OK I am persuaded and am now at 2.1 (having read the notes at Adobe Labs Wiki, I didn't see any downside) -- but Vic and Brad, I make you a friendly wager that this particular issue persists. It'll be a week or more before I can test it, but the next time I go hiking, I will geo-tag first and then seen what happens; I'll report back. Thanks as always.
 
Upvote 0 Downvote
KED said:
OK I am persuaded and am now at 2.1 (having read the notes at Adobe Labs Wiki, I didn't see any downside) -- but Vic and Brad, I make you a friendly wager that this particular issue persists. It'll be a week or more before I can test it, but the next time I go hiking, I will geo-tag first and then seen what happens; I'll report back. Thanks as always.
Click to expand...

I'm curious, what are you wagering ??:cheesy::cheesy::shock::evil::roll:
 
Upvote 0 Downvote
Status
Not open for further replies.
Back
Top