Skip to main content
_
_jj_pod_
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

    Show previous replies
    _
    _Brent_Walton_
    Participating Frequently
    August 6, 2008
    Nope. Oh, and don't forget. Mine always works on my drive C which has a volume name of HPC, but fails on my drive E which has a volume name of HPE. I thought I'd mention that just so it shows a consistency there too. Ownership of the files and folders does not seem to have any bearing on the problem. (I tested that too.)

    Brent
    _
    _Kevin_Tieskoetter_
    Participating Frequently
    August 6, 2008
    Jim, the root cause for the ghosting - at least on Windows - was that (as some users in this thread surmised earlier) at one point in the process we were getting a lowercase drive letter (e.g. 'l' instead of 'L') and were treating that as a new drive.

    We have a fix for this now, as well as for the single-quote bug, and the ampersand bug.

    The one thing we haven't been able to verify in-house yet is the ghost drive problem on the Mac - if you're on a Mac and are seeing this problem, please contact me!

    Unfortunately, I don't yet know when the next release will happen.

    -kevin
    _
    _dlibrach_
    Participant
    August 6, 2008
    Kevin,

    Yes, my external had an apostrophe in its title. I removed it, reinstalled Camera Raw 4.5 and......it works now!!! :) Tested a bunch of files and CS3 opens it without any problems. Thanks for the help.

    Cheers,
    Dave
    A
    andrewn_artist
    Participating Frequently
    August 6, 2008
    Thanks Kevin - that certainly explains how it arose. Do you have any sense of how and when a fix will be made available...
    Andrew
    _
    _Jim_Camelford_
    Participating Frequently
    August 6, 2008
    Kevin, is there any chance that your embedded version of SQL Lite is simply not seeing the two drive dtrins as EQUAL - and that is what is causing the creation of the new 'volume' ?

    jc
    _
    _Robert_Munoz_
    Participating Frequently
    August 6, 2008
    Kevin,

    Thanks for your response. As a matter of fact, the path does have an ampersand (in one of the parent folders). I hope it's that simple. I'll do some testing later today.

    Robert
    _
    _Kevin_Tieskoetter_
    Participating Frequently
    August 6, 2008
    Robert, that's my next thing to tackle. The file that you're working with - does it happen to have an & in the name, or anywhere in the path to the file?

    Earlier today, Jim Burgess brought it to my attention that LR will not import a file back from PS if it has an ampersand anywhere in the path. This'll also be fixed in the next release.

    -kevin
    _
    _dlibrach_
    Participant
    August 6, 2008
    "Let's be a little careful about accepting other systems/software as being the problem...as in....".

    Yes, I agree. Until I came across this thread, I thought I was the only one with this problem. Obviously others are experiencing the same thing.

    I was only relaying what we tried and what we thought was the source of the problem.

    I will give kudos to the adobe agent that I spoke with though as he was quite patient and genuinely concerned about the problem as we went through all the various tests over the course of the three hours. I believe my file is still open with them and that they were supposed to still be looking into it further. Still no word though.
    _
    _Kevin_Tieskoetter_
    Participating Frequently
    August 6, 2008
    dlibrach, can you also check for an apostrophe anywhere in your file path (including the name of the volume)? Any other uncommon characters?

    -kevin
    _
    _Kevin_Tieskoetter_
    Participating Frequently
    August 6, 2008
    Brent, is there any chance there's an apostrophe anywhere in folder path for the file you're trying to edit?

    Does it work if you import a fresh raw file from the root of your C drive and try edit-in-PS on that?

    -kevin
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices