Help - Search - Members - Calendar
Full Version: LightRoom Mac Glitch Help!!
OpenSourcePhoto > Digital Photography > Post Processing > Lightroom
davidmcclain
A new glitch popped up in LightRoom for me today. I believe I have narrowed it down to an issue with Leopard.

If I try to export an image from Lightroom in its "Original" format, the exported file seems to be corrupt.



If I try to select it in the Finder under the colums view (with the preview in the last column) it causes the Finder to crash and relaunch.



If I view it in cover flow there is no "preview".



Try to open it with the Preview Application - Preview opens but the file will not. In Fotomagico, if I select the folder in which the corrupt file is in, Fotomagico crashes. I can export into the other formats fine. Also, seems to be limited to .jpg files - meaning if I import a folder of jpgs into LR and then export any of them with "Original" format specified. I can export .CR2s into their "Original" format just fine.

Also what really chaps me about it - I can open up the files fine on a Windows machine. I am supposed to be making my partners Windows machines look bad, and I hate having to sit in front of XP to do work.

Anyone have this issue? Anyone have any input? I am searching the Adobe forums and support.

Here are my Specs:

Leopard 10.5.1
Lightroom 1.3

Problem happens on both computers:
PowerMac G5 dual 2.0 (early 2005)
Macbook Pro 2.4 Intel Core 2 Duo
davidmcclain
So many replies, I don't know which one to answer first:)

anyhow if you read this, it is a confirmed Leopard glitch - you can read about it here
David from Puerto Rico
I am not sure why is doing that to you but I tried what you did on a G4, MACBOOKPRO and and a MACPRO to see if it would happen to me but I found no problems. Works fine.

If you are "exporting" the file in the original format Lightroom doesn't do anything to it... it is the original file. Questions,

(1) If you import the file from you camera to your desktop, can you see it fine?
(2) What camera are you shooting with? Make sure you have done the latest update for the MAc that support that file.

You may want to try this: If you want to export the original file, why don't you just select show in finder and copy those you need? Or use Bridge for it. See what happens then.

I read the link but I am not sure it applies to you as your finder is not crashing. Like I said I tried it and worked fine.

Good luck

davidmcclain
QUOTE(David from Puerto Rico @ December 6 2007, 01:40 PM) *
I am not sure why is doing that to you but I tried what you did on a G4, MACBOOKPRO and and a MACPRO to see if it would happen to me but I found no problems. Works fine.

If you are "exporting" the file in the original format Lightroom doesn't do anything to it... it is the original file. Questions,

(1) If you import the file from you camera to your desktop, can you see it fine?
(2) What camera are you shooting with? Make sure you have done the latest update for the MAc that support that file.

You may want to try this: If you want to export the original file, why don't you just select show in finder and copy those you need? Or use Bridge for it. See what happens then.

I read the link but I am not sure it applies to you as your finder is not crashing. Like I said I tried it and worked fine.

Good luck


My finder is crashing. when you try to "preview" the file in the finder, it makes the Finder freeze and then automatically relaunch. That link describes my problem exactly.

I ruled out the camera. It does not matter if I use a 5D file, 40D file, 20D, 10D. It also happens with a scanned image. So far the problem is exclusive to JPG's that I import into Lightroom so that Lightroom is treating them as "Originals"

Bridge is a good workaround. In fact I know 20 different ways to do what I was trying to do, but LR is supposed to do it, so I wanted to see what the problem was.

Thanks for the suggestions
David from Puerto Rico
Not sure if this is a real alternative for you, but try erasing the side car when you export or export without the xmp side cart. It seems that the problem resides there.
Jasont
Have you downloaded the latest version? It was suppose to fix some bugs that were causing problems in Leopard.
davidmcclain
QUOTE(David from Puerto Rico @ December 6 2007, 04:23 PM) *
Not sure if this is a real alternative for you, but try erasing the side car when you export or export without the xmp side cart. It seems that the problem resides there.


There is not xmp sidecar file. the problem resides in the file itself. I did turn off the function that writes the metadate into the jpegs and tiffs though.
David from Puerto Rico
QUOTE(JasonTench @ December 6 2007, 07:28 PM) *
Have you downloaded the latest version? It was suppose to fix some bugs that were causing problems in Leopard.


Those problems he describes are in the newest version 1.3. It fixed some but not all. We are still waiting for Adobe to fix them all. This is the official scoop:

The Lightroom 1.3 release addresses many Leopard OS X 10.5 issues but a few outstanding problems remain or have been discovered.
  • Time Machine compatibility still remains unclear at this time. Running Time Machine backup or restore operations while Lightroom is in use is not recommended until more information can be obtained. Interim solutions:
  • Have Time Machine exclude the directories where Lightroom catalogs are stored and use Lightroom to backup the catalog files
  • Run Time Machine when Lightroom is not running.
  • There is a bug in the Lightroom 1.3 Print Module that can cause the application to crash on either OS X 10.5 or 10.5.1. Minimizing the template preview in the upper left corner can help reduce the frequency of this issue.
  • The Finder in Mac OS X 10.5 and 10.5.1 can crash when viewing files that contain Lightroom XMP Snapshot data created in the develop module. This is an error in how the Finder reads metadata and will require an operating system update to solve. (I believe that this occurs more frequently with JPEG or TIFF files)
  • Importing directly from a card may not copy all of the image files or may fail. Please copy the images to a local drive using the Finder first if you experience problems.
    We will provide an update to address the print module issue but have not set a release date for that update.




David from Puerto Rico
Hey, David, I don't think 1.3.1 fix your problem. Read this:

"the Finder in Mac OS X 10.5 and 10.5.1 can crash when viewing files that contain Lightroom XMP Snapshot data created in the develop module. This is an error in how the Finder reads metadata and will require an operating system update to solve. The error can be reduced for additional files going forward by modifying the Lightroom preference to *not* save Develop settings within JPEG, TIFF or PSD files. (Preferences: Catalog Settings: Metadata)"

From the Lightroom Journal
LoriWo
It's ironic that Apple's currently running ads suggesting that users are downgrading from Vista to XP when the fact is the bugs like this in Leopard are causing people to downgrade. Until Mac releases a fix for how Loepard's fil finder reads metadata you will have this problem.
davidmcclain
QUOTE(LoriWo @ December 8 2007, 04:38 PM) *
It's ironic that Apple's currently running ads suggesting that users are downgrading from Vista to XP when the fact is the bugs like this in Leopard are causing people to downgrade. Until Mac releases a fix for how Loepard's fil finder reads metadata you will have this problem.


True, but this problem is very minor compared to a crash on a windows machine. This just causes the Finder to relaunch itself, while none of your running/open applications are affected. It happens for a second or two and the Mac still keeps on working. It is an easy workaround (change a LightRoom preference) where as the Vista problems had minor or no resolutions.

There will always be compatibility issues and resulting updates. With Apple, at least I know it will not cripple my workflow or cause my blood pressure to rise.

I do agree with the ironic situation, but I have to defend my Mac's they are very sensitive to criticism and only work harder to dispell any doubts about their superiority:) This is the first time that I have experienced any real problems with an Apple update, and they are still minor.
r-lr
QUOTE(davidmcclain @ December 6 2007, 12:22 PM) *
So many replies, I don't know which one to answer first:)

anyhow if you read this, it is a confirmed Leopard glitch - you can read about it here


i am having the same problems with since i updated 1.3 and don't have leopord (though i have heard the glitches for that.) i have downgraded to 1.2 but still problems...

i am screaming at my computer at the moment....
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.