Skip to main content
Participating Frequently
July 29, 2008
Question

Lightroom 2.0 will not export to Photoshop CS3

  • July 29, 2008
  • 368 replies
  • 28150 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
    August 19, 2008
    I followed the procedure above (Duncan Grove 269) and it worked for me.
    I've now found another bug in the print module: When I'm in picture package and I click on the down arrow to change from "Printer Manages Colors" to "Other" to select my HP Premium Plus paper the whole program hangs and I have to use Ctrl+Alt+Del to shut it down.

    However, if I go to "Contact Sheet" first and set the color management in there. Then go back to "Picture Package" I can adjust the settings without it hanging. Weird!!!
    Participant
    August 19, 2008
    This advice from a third party worked for me:-

    For me the key to getting the Smart Objects working in CS3/Win has been to copy a file called 1015 from the Photoshop 10.0.1 patcher temporary folder and rename it as the scripting plug-in.

    Simplistically, find ScriptingSupport.8li in temporary files;-

    Find 10.0.1 updater in C:\Documents and Settings\"User"\Local Settings\Temp\Patcher. You copy it to "Local drive":\Program Files\Adobe\Adobe Photoshop CS3\Plug-Ins\Automate and rename it to ScriptingSupport.8li (if ones there already, rename it to ~ScriptingSupport.8li - the tilde makes PS ignore a file).

    I am pleased to find a resolution but still think it should have worked straight out of the box!
    August 19, 2008
    Andrew - I would have tried this already but I have been making full use of the merge to panorama and open as layers options in LR2. You know how it is when you get a new toy :)
    I'll certainly use it for normal edits though; much better than syncing and adding to collections.

    Cheers.
    Participating Frequently
    August 19, 2008
    Damon:

    Until it's fixed, use the work around that has been described several times herein - i.e. set up PS as the additional editor, then edit using Ctrl-Alt-E. LR2 then behaves as it did in LR1...no ghost and the edited file is auto-stacked.

    To clean up the ghosts you have, after synchronizing, try using the "auto Stack By Capture Time" command to establish the stack groups between the edited file and its original raw counterpart...

    Hope that helps...and it does appear a fix is coming according to several posts from Adobe staff...

    Andrew
    Participant
    August 19, 2008
    The (partial) solution to the ghost folder is of course to re-synch the library, as Damon says, but this is so terribly slow. I have tried re-synching only the individual folder to try to reduce the waiting time, but even this is glacial. I have a folder of 1,800 files which I tried to re-synch after 3 ghost foldered edits last night: I just gave up waiting in the end. With LR 1.x this would have identified the number of new files in a few seconds, but after quite a few minutes (sorry, I did not time it - I was actually trying to get something done!) it had not even managed to count the 3 new imports. This was a second attempt, after I had optimised the database and rebooted, but it made no perceptible difference. So now I delete the ghost folders, but generally do not have the new files imported into my database. Maybe I should have left it running overnight!
    August 19, 2008
    This is getting *really* annoying now.
    My catalogue is starting to get in a bit of a mess because of this ghost folder thing. I can live with having to re-sync the library but not having it stack the photo (with no way to do it manually) with the original is annoying. If you edit a photo in PS from within a collection then it gets really messy and you spend more time figuring out where your damn photos are meant to be located than actually editing/printing/publishing.

    Kevin - **Please** can you nag your colleagues/bosses to get a fix for this released?

    On the up side, the Adobe store finally delivered my boxed copy, only 3 weeks after placing the order.
    Nice pretty packaging btw ;)
    Participating Frequently
    August 19, 2008
    Jason,

    That is the idea. In LR 2.0 RAW files open directly in PS. It doesn't create a Tiff (or whatever way you had set it up in the past). When saving the file after processing it in PS it should save back in its original folder (which it does) but this is where the "ghost folder" problem pops its head up. You will see duplicate folders in LR 2.0. One which is your original folder and a copy of the folder with the edited photo in it. The only way to get around this is to delete the ghost folder and re sync LR 2.0
    Participant
    August 18, 2008
    My problems seems to be classified under bullet #5.

    I am using Lightroom 2.0 (upgraded from 1.4) and Photoshop CS3 10.0.1 on Windows XP SP3 ...

    I know this issue was working properly ... but as of yesterday ... now when I click edit in PS... instead of opening the dialog box asking me what I want to do ... it goes directly to PS and opens the image. It does not create a new file in LR either. If I click edit in PS multiple times it does not create copies of the edit file ... it just copies over the original.

    Once I'm done editing in PS. I have to physically import the "edit" file into LR and then create stacking rules.

    I just uninstalled LR, rebooted and reinstalled but it still doesn't work properly.

    Jason
    Participant
    August 18, 2008
    I carried out the manual update as detailed earlier and on my Vista machine these are the only files that needed updating,
    Merge to HDR.jsx, CreateImageStack.jsx, ScriptingSupport.8li, Terminology.jsx.
    This has fixed my Photoshop problem. So thanks to those above who put me onto this workaround. I am now concerned how many other Adobe updates did not complete. Especially as i have to use MSConfig to stop alot of programs that run in the background before i can install CS3 both suites. I have also had to use subinacl.exe with a cmd file to overcome Adobe messing with registry permissions (not Adobes cmd file that did not Work)
    Participating Frequently
    August 17, 2008
    Aha, I wasn't running the batch file as administrator, so it wasn't copying everything - thanks very much for your help, Fredrik.