Skip to main content
Participating Frequently
July 29, 2008
Question

Lightroom 2.0 will not export to Photoshop CS3

  • July 29, 2008
  • 368 replies
  • 28153 views
OK,

So I downloaded and installed lightroom 2.0 this morning and things are not working well.

System: Macpro 2.8, 8 gb ram, os x 10.5.4, nikon d300 raw files

The problem...

It started with Lightroom not exporting any images to photoshop. Doesn't matter if I try to send 1 or 20, I get a spinning beach ball, then nothing. if photoshop is closed it will open it, but nothing gets loaded into it. Plain export, merge to panoramic, edit as smart object, nothing does anything.

Tried in both 32 and 64 bit modes, tried re-installing Lightroom 2.0 from scratch. still nothing. I sent a sample raw file into adobe and am waiting to hear back, but figured I'd see what everyone else thinks as well.
    This topic has been closed for replies.

    368 replies

    Participant
    September 21, 2008
    Okay, I'm new here and have just read through a ton of messages and still don't know how to manually fix the problem.

    FYI, the problem I'm referring to is the same as that of the original poster. I've got a new MacPro dual 2.8, CS3 and Lightroom 2.0. CS3 has been updated and I can't get the "edit in Photoshop" options to work. None of them. I've set up Photoshop as the secondary editor and still nothing except for the basic "edit in Photoshop" option. Can't Merge to HDR, can't open as smart object. Photoshop opens (if it's not already) but nothing happens.

    The more I read the messages in this thread, the more confused I get as the OP is on a MAC and the thread seems to have been taken over by Windows users.

    Can someone possibly point me to the post (if it exists) on how to manually fix this problem on a MAC/Leopard?
    Participating Frequently
    September 21, 2008
    Is this the way it should work?: I ctrl-E on a jpg and send as a copy with adjustments. I add an adjustment layer and ctrl-s to save. Because it's now a psd cs3 needs to Save As. I have to choose the folder. Back in LR, there is an superfluous uncorrected copy of the jpg but no corrected psd. I then have to synchronize the folder to see the psd, delete the excess jpg and then stack the psd and jpg. I guess I was hoping this would be more automatic. Didn't it work better before?
    September 21, 2008
    Just to add my latest: RC 2.1 works for me.
    That is to say it resolved the 'ghost' folder problem. Thus far it all works as designed.

    Thank you Adobe, well worth the wait to get such a great bit of software working.
    Participating Frequently
    September 21, 2008
    >So, yes, Lightroom can't fix it. But the stated approach to fixing it with the current 10.0.1 seems to work for many people.

    Well I tried remedial actions #278 to #887 and thought that #395 worked for me but now it seems it doesn't, at least not reliably. Photoshop CS3 now opens sometimes with Scripting Support 10.0.1 and other times with 10.0, and LR "Edit In..." behaves or misbehaves accordingly. What determines which version of Scripting Support opens I have not determined. How this can happen is a complete mystery to me. I've not received any response or ideas on this, nor seen any target for correction of the problem.

    Just more grist to the nightmare, to mix metaphors horribly.

    Of course if we don't get a fix soon from Adobe, we'll all just have to buy CS4 upgrade to solve the problem. Just like I bought Lightroom 2 specifically to fix the shortcomings of version 1. This is a strange marketing technique.
    Participating Frequently
    September 20, 2008
    > So if the current update does not address the problem of CS3 scripting changing to 10.0.1 does this mean LR2 users with that problem are going to have to wait for the Photoshop engineers to come up with a solution?

    It's a PS installer bug, from what I understand. So, yes, Lightroom can't fix it. But the stated approach to fixing it with the current 10.0.1 seems to work for many people.

    Kevin Tieskoetter, "Lightroom 2.0 will not export to Photoshop CS3" #228, 13 Aug 2008 2:59 pm
    Participant
    September 20, 2008
    So if the current update does not address the problem of CS3 scripting changing to 10.0.1 does this mean LR2 users with that problem are going to have to wait for the Photoshop engineers to come up with a solution? Can't help thinking that this has not even begun given their preoccupation with CS4 release. If so troubled users like me are left well out into the cold ...

    BTW the last post link does not work I had to go through all 334 posts to get to here!
    September 20, 2008
    Addendum to my last post:
    Since rebooting the OS, 2.1 RC1 works well: The "...Photoshop could not be launched..." issue disappeared. PSDs created as result of the PS editing are instantly imported and show up in the catalog.
    Well done, this feature really eases up a lot my common workflow!
    Participating Frequently
    September 20, 2008
    I am also running Vista x64. Since the 2.1rc1 update, the Edit in CS3 option is now working flawlessly for the first time. Not sure if this makes a difference, but I ran the install over the top of the original version 2 install if that helps? I.e. chose the same directory "C:\Program Files\Adobe\Adobe Photoshop Lightroom 2" - I have the 64bit version installed only.

    LR is still randomly hanging though if I access files on the SAN, even browsing through files in the grid view causes the hang and subsequent Windows (Not Responding) message in the LR title bar, then 30 seconds later it springs back to life. Seems a little less frequent though now.

    Remember this is a release candidate, and that Adobe did say in an earlier message that the fix being worked on would not address the PS CS3 Scripting support issue. I don't exactly agree with this, as there is still an obvious issue for some people with the PS side of the equation - In light of Adobe's comments though I can only assume that the PS dev team woukd be looking at the 10.0.1 scripting update issue, rather than the LR team. Lets hope they collaborate on the fix to get this one sorted once and for all.

    From my experience though with the scripting update issue in CS3, I was originally unable to successfully apply the 10.0.1 (Scripting update still sat at 10.0), and found several peculiarities in my CS3 install, which turned out to be to do with the fact that it was originally upgraded from CS2, and that this obviously hadn't done it's job properly. I ended up re-building my system with Vista which involved a re-install of CS3 from scratch, and the automatic update installed the 10.0.1 update without even a glitch, and as I say the subsequent LR 2.1 update works fine now with the CS3 integration (for the first time).

    Not sure what the process for feeding back experiences on the release candidate are exactly, but I would assume there is some way you could register any issues with Adobe.

    Pity the 2.1 version doesn't support Canon's new 5dMkII yet!

    Cheers, Paul A
    September 20, 2008
    Good morning all,
    looks like we're seeing some kind of regression in LR2.1 RC1:
    On my system (vista x64)RC1 breaks function "Edit in Photoshop CS3" (PS CS3 with manually updated scripting support (10.0.1)).
    It ends up with "The file could not be edited because Photoshop could not be launched"
    In 2.0 concerning this respect, things worked well (after applying the patches discussed in the forum).

    @Adobe: Is somebody working on a bugfix for the PS updater?
    Would be a gentle attitude if the PS-team could OFFICIALLY comment on this.

    I mean, many of us here have proven, that the PS-updater infact updates nothing beside the main executable on some systems and, in my case, I have filed a qualified bug-report concerning this issue - sofar no feedback. I personally get easily tired when discussions seem to render as one-ways.

    No hard feelings,
    Armin.
    Participant
    September 19, 2008
    This issue ("the picture can't be edited because Photoshop cannot launch" - when it has launched) appears still to be a problem in LR2.1RC. I have never had it before, but have it now :(