Lightroom disaster/workflow

[CaptZoom]

Advertisement (gone after registration)

It could be the X2 causing the problem rather than LR.

 

 

I had my very own disaster with Lightroom V5 on Mac, never ever select "Copy As DNG" on import.

 

The DNG files from my X2 are readable by most applications as is, after importing to Lightroom using "Copy As DNG", the file system no longer shows a preview icon, Aperture cannot read them, Preview cannot read them, Corel Aftershot Pro or Capture One cannot read them.

 

It seems that Lightroom creates it own DNG format files unreadable by other applications.

 

Frankly this by itself is enough to make me leave Lightroom, there should at least be some "Compatibility Mode" to prevent this from happening.

 

You can also destroy an existing "good" file in the same way by right clicking->Metadata-> Update DNG Preview and Metadata.

 

Seriously Adobe WTF? DNG has turned out to be more proprietary than *any* native raw file.

 

PS Can anybody tell me how to recover the files so that they are readable by other applications. I can convert to TIF, that seems the only way

 

EDIT: This seems to be camera dependant, I can still read my M8 files after this procedure although NOT my X2 files.

[Advertisement]

The Leica Q3 is available for pre-order at B&H Photo Video and Adorama

[Chuck68]

Thanks, but unfortunately not a camera fault, rather a problem with the DNG format itself.

I guess Adobe is adding some additional data that other programs don't know how to handle.

There are other cameras that have the same problem,

 

The thread Adobe Community: DNG files showing no thumbnails mac osx 10.8.2 is one example.

[CaptZoom]

Thanks, but unfortunately not a camera fault, rather a problem with the DNG format itself.

I guess Adobe is adding some additional data that other programs don't know how to handle.

There are other cameras that have the same problem,

 

The thread Adobe Community: DNG files showing no thumbnails mac osx 10.8.2 is one example.

 

That's bummer.

[jaapv]

There used to be the same problem with Monochrom DNGs but that has been solved:http://www.l-camera-forum.com/leica-forum/digital-post-processing-forum/297355-apples-aperture-now-supports-mm-m.html

 

If you run your files through Adobe's DNG converter, OS10 should recognize them again.

The problem is not so much Adobe fiddling with the files, but Mac, who did not implement all aspects of the format.

[kdriceman]

I had my very own disaster with Lightroom V5 on Mac, never ever select "Copy As DNG" on import.

 

The DNG files from my X2 are readable by most applications as is, after importing to Lightroom using "Copy As DNG", the file system no longer shows a preview icon, Aperture cannot read them, Preview cannot read them, Corel Aftershot Pro or Capture One cannot read them.

 

It seems that Lightroom creates it own DNG format files unreadable by other applications.

 

Frankly this by itself is enough to make me leave Lightroom, there should at least be some "Compatibility Mode" to prevent this from happening.

 

You can also destroy an existing "good" file in the same way by right clicking->Metadata-> Update DNG Preview and Metadata.

 

Seriously Adobe WTF? DNG has turned out to be more proprietary than *any* native raw file.

 

PS Can anybody tell me how to recover the files so that they are readable by other applications. I can convert to TIF, that seems the only way

 

EDIT: This seems to be camera dependant, I can still read my M8 files after this procedure although NOT my X2 files.

 

I would think your original raw file might be embedded somewhere in the Adobe DNG. It may work to execute a "Reset All Settings" command in the Develop Module for those pictures affected.

 

http://livedocs.adobe.com/en_US/Lightroom/1.0/help.html?content=WS9AB9509C-05BE-4396-9ED2-313C0FF8A154.html

 

Also, I have found Adobe's technical support very helpful when dealing with these kind of issues, especially when using a chat session. Sorry I don't have the link but its relatively easy to find navigating the Adobe website.

 

Good luck.

[kdriceman]

I had my very own disaster with Lightroom V5 on Mac, never ever select "Copy As DNG" on import.

 

The DNG files from my X2 are readable by most applications as is, after importing to Lightroom using "Copy As DNG", the file system no longer shows a preview icon, Aperture cannot read them, Preview cannot read them, Corel Aftershot Pro or Capture One cannot read them.

 

It seems that Lightroom creates it own DNG format files unreadable by other applications.

 

Frankly this by itself is enough to make me leave Lightroom, there should at least be some "Compatibility Mode" to prevent this from happening.

 

You can also destroy an existing "good" file in the same way by right clicking->Metadata-> Update DNG Preview and Metadata.

 

Seriously Adobe WTF? DNG has turned out to be more proprietary than *any* native raw file.

 

PS Can anybody tell me how to recover the files so that they are readable by other applications. I can convert to TIF, that seems the only way

 

EDIT: This seems to be camera dependant, I can still read my M8 files after this procedure although NOT my X2 files.

 

Also, I had something like this happen with LR 4 and a Sony RX100 MkII when it first came out. Adobe didn't provide an update for that camera's raw file in LR4. Annoying. I had to upgrade to LR5 to process the RX100II raw files. You might make sure your LR5 has the latest update.

[Chuck68]

Advertisement (gone after registration)

Thank you for your responses, I have the latest Adobe updates and the reset did not work because the file itself was rewritten on import, even though the out of camera was a (different format) DNG so there is nothing to reset. ( I should have made a copy of the original before import: silly me)

 

I tried the Adobe Raw Converter which did not help, although I discovered I can read the new DNGs in Lightzone.

 

Guess I will be more careful in the future and will be using Lightroom very conservatively.

 

In my opinion, seems the DNG format is getting fractured with various applications supporting different versions and different specific cameras but no clear explanation of the differences or compatibility matrix.

 

It seems to be more of a commercial play for influence on Adobes part rather than a real benefit for users.

 

Just my 2 cents, thank you again for your suggestions.

 

Cheers

 

S

[Guest WPalank]

Chuck, seems as if you found some sort of work around.

 

But why in the world would you select "Copy as DNG" when it is already in the DNG Format?

 

I could see if there was a readability issue on first try,then leaving the SD Card untouched until sorted...

[jsjxyz]

In LR you don't need to copy DNG just create virtual copy.

 

the thing LR is hassled is you really need to backup the catalog often, just in case accident happened like corrupted file. And also moving from note book to other computer is not as simple as drag and drop.

 

Here is a link to learn how better LR comparing to Bridge

 

 

 

http://photoshopuser.com/lightroom/

 

100 Ways Adobe Lightroom Kicks Adobe Bridge's - NAPP

[kdriceman]

Chuck, seems as if you found some sort of work around.

 

But why in the world would you select "Copy as DNG" when it is already in the DNG Format?

 

I could see if there was a readability issue on first try,then leaving the SD Card untouched until sorted...

 

I usually have my LR import settings set at "Copy as DNG" because I import raw files from several different cameras and want to standardize my file formats in a file type that will withstand the test of time and I believed Adobe DNG would be supported for the very long term. If the DNG format is mutating variations, this completely changes my strategy (and pisses me off). I would really like to know what Adobe themselves have to say about this. I wonder if Chuck68 has contacted Adobe technical support about this issue.

[CaptZoom]

From what I've gathered this far, it isn't Adobe but rather OSX that's lagging (though I use Macs, and have not encountered the problem the OP is having).

 

 

 

I usually have my LR import settings set at "Copy as DNG" because I import raw files from several different cameras and want to standardize my file formats in a file type that will withstand the test of time and I believed Adobe DNG would be supported for the very long term. If the DNG format is mutating variations, this completely changes my strategy (and pisses me off). I would really like to know what Adobe themselves have to say about this. I wonder if Chuck68 has contacted Adobe technical support about this issue.

[Guest WPalank]

I usually have my LR import settings set at "Copy as DNG" because I import raw files from several different cameras and want to standardize my file formats in a file type that will withstand the test of time and I believed Adobe DNG would be supported for the very long term. If the DNG format is mutating variations, this completely changes my strategy (and pisses me off). I would really like to know what Adobe themselves have to say about this. I wonder if Chuck68 has contacted Adobe technical support about this issue.

 

That makes sense (multiple cameras). I'm the same way, push one button and let it ride.

Agreed, the DNG thing isn't turning out like the original plan.

[jaapv]

It would be if Mac used the complete standard.

[kdriceman]

I don't understand the Mac issue here. What is happening? I use Mac exclusively, with LR on 3 different Macs (iMac, Mac Mini, MacBook Air). The only problem I have had like this was corrected with a LR update - thus it was likely a LR issue.

[CaptZoom]

I don't understand the Mac issue here. What is happening? I use Mac exclusively, with LR on 3 different Macs (iMac, Mac Mini, MacBook Air). The only problem I have had like this was corrected with a LR update - thus it was likely a LR issue.

 

I'm no expert in this; based on this thread (and links) it seems that OSX supports portions of DNG formatting and LR has to be amended in a manner so the resulting DNGs are compatible with OSX. It seems Apple is setting a specific standard/criteria for DNG files that is different from the standard DNG. If this is true, then it does make seem like an LR issue (not making files OSX compatible) and it is also the case that OSX is changing the DNG standard/format.

 

In any case, some one more knowledgeable should weigh in.

[Jeff S]

I use Mac exclusively, with LR on 3 different Macs (iMac, Mac Mini, MacBook Air).

 

Just curious, why not LR 5? It has many significant advantages over LR 3 IMO.

 

Jeff

[kdriceman]

Just curious, why not LR 5? It has many significant advantages over LR 3 IMO.

 

Jeff

 

Jeff, sorry for my poor context. I should have written "LR5 on 3 different Macs"

[Jeff S]

My mistake...read it too fast.

 

Jeff

[Advertisement]

Hallo,

Look here: Interesting Leica gear

[qvsm]

OP, here is my workflow, supposing I want to prepare an image for print, plus make a suitable web copy, in the case of it helping:

 

1. Create a folder under Pictures (or other parent folder containing all images) with the following naming convention 2013-09-fun-on-leica-forum.
   
2. Within, create the following folders 0-raw, 1-ps-edits, 2-print, 3-web.
   
3. Copy your RAWs into 0-raw.
   
4. Import (Copy) the 2013-09-fun-on-leica-forum folder. Your RAWs files from 0-raw will now show in LR.
   
5. Sift through the images, marking up files I want to work on.
   
6. Do adjustments in LR on virtual copies.
   
7. If I want to do any adjustments of a file in PS, open from LR, save output as TIFF to 1-ps-edits. These can now also be brought into LR by syncing your folder, since LR is just showing you whats on your file system.
   
8. To prepare a 'finished' file for print, open in PS, prepare (canvas changes, sharpening, profiling etc), save output to 2-print. These files are what I send to my printer.
   
9. To prepare a web copy, open a 'finished' file in LR or 1-ps-edits and correct for web, saving output to 3-web.
   

 

Its fairly crude, there may be many better ways to organising, or of automating this, but I don't work on 500 files each weekend, usually 1-2 a weekend, so this suits me very well - and certainly makes the file system take lead on what is where, in what state etc. I'd find very often that I'd want to go to a folder and get a file in a particular state that I had created previously (eg a print ready version of the image), therefore didn't want to have to open LR/PS every time to make the desired export. Storing multiple states works well for me, at the expense of disk space.

 

I used to use C1 rather than LR, as I really prefer the colours for M8/9 files. However, I find it irritating to use, plus fairly unstable, so have started to use LR again. The above workflow works fine for me in both apps however.

[jaapv]

Interesting remark about stability - as I was annoyed at CS6 this weekend which kept hanging ( probably have to do a re-install), as opposed to C1, which always works rather smoothly without hangups.