Lightroom 32bit mode for 32bit DNG files

When I open 32bit (floating point) TIFF files in Lightroom (5.7.1) it opens them as expected - in 32bit mode - and allows me to adjust the exposure slider in the range of -10ev to +10ev.
However, when I open 32bit (floating point) DNG files, it opens them in 16bit mode and allows the exposure slider to range only from -5ev to +5ev.
Does anyone know why it works this way?
Is there a way to open 32bit DNG files in 32bit mode?
Note that a 32bit DNG file can be converted to 32bit TIFF using "dng_validate.exe -3 <output.tif> <input.dng>"
This way I can convert my 32bit DNG files to TIFF, but I lose the control over WB and I end up with huge TIFF files.
I'm obtaining my 32bit DNG files using HDRMerge. This can be used as a reference:
https://dl.dropboxusercontent.com/u/21642925/PC211276-211280.dng
I also tried 32bit DNGs that were created by CeroNoice and I get the same result (LR opens them in 16bit mode rather than 32bit and restricts the exposure slider to -5ev - +5ev).
It could be that HDRMerge or CeroNoice do not produce the DNG correctly. However, I tried to run the output of HDRMerge through a DNG to DNG conversion using Adobe DNG Converter and it didn't help either.

Thanks for taking a look at this.
I think that converting 32bit tiff files to dng only changes the wrapping. So in a way it's understandable that they are opened in 32bit mode. I still don't understand why normal 32bit dng files can't.
Thanks for the top about the GND filter. I thought about using a brush all over the frame, but a GND can also be used. I suspect that if LR opens my dng file in 16bit mode than it uses a narrower pipeline for the tone curve and color manipulation so the result will be inferior compared to a 32bit tiff file (developed with the same settings). That's why I'm trying to find a way to open the dng files directly in 32bit mode.

Similar Messages

Recovery for corrupt DNG files?

I have many DNG files that are showing as corrupt--files copied from a failing hard drive. The file sizes seem right--around 26MB each, shot with a Canon 5DMIII and converted to DNG via Lightroom.
The bad hard drive is dead now, I can't run recovery software on it, but I do have the files on a healthy drive.
Anyone know of software that might be able to open corrupt DNG files? Some of the photo recovery software I've used in the past works by scanning media, but I have thousands of media files on the drive--I'm looking for recovery software that will let me open specific files and try to recover them. I'm on a Mac. I've tried Photoshop CC, and LR 5.6. When I try to open the .dng files, I get: "Could not complete your request because Photoshop does not recognize this type of file."

Sorry, they're dead.
There's a plugin that will extract your Lightroom preview as a jpg. It won't get your raw files back, but the jpegs ought to be good enough to print.
Best practice says that you need to keep at least two copies of your originals. On separate physical devices.
Hal
p.s. That website I referenced also points to a more full featured program that does the same thing.

How do I update Date Time Digitized to match an updated Capture Time for a DNG file?

I am updating capture time based on GPS Time (a bit OCD, I know) but when I change Capture Time the Date Time Digitized value does not change. This in in LR 4.3 and is not affected by whether on not the Catalog is set to 'Write date or time changes into proprietary raw files'. Maybe this is a problem for DNG files only.

GreSep wrote: I saw another LR discussion that said that with LR 4.3 updating Capture Time would also update Date Time Digitized but it does not do so for me on my DNGs (and as of last month ALL my images were converted to DNGs).
One or two intermediate versions of LR 3 (perhaps Lr 3.6) set DateTimeDigitized when you gave the Metadata > Edit Capture Time command. But for people managing scans in which the capture time of the original image was different than the scan time, this behavior overwrote their scan times, so Adobe backed out of that change. Before and since those versions, the Metadata > Edit Capture Time command just changes the EXIF:DateTimeOriginal and related fields in XMP and IPTC.

Why won't Lightroom 3.3 send a dng file to Photoshop CS5?

I am using a Windows 7 64 bit platform, Lightroom 3.3, Camera Raw 6.3 and Photoshop CS5 also 64 bit. I have my photos (from a Nikon D3100) in dng format but when I try to open it in Photoship using the Edit in command to send it either as a dng file or a smart object I get a notice that the file couldn't open because Photoshop couldn't be opened. In fact Photoshop does open (or it is already open). Sometimes, the file will eventually open in Photoshop, but it takes several minutes -- like 5 or more, other times it never opens.
Can anyone offer any suggestions or help?
P

Quote <Is there a setting LR or on the camera that I can use to allow LR to recognise (and render) the NEF file from the camera?>
No. LR will only show the thumbnail rendered by the camera,if it is possible. The better practice would be to download the files from the CF/SD card using a reliable card reader, this would be more efficient/faster and reliable. (use the camera to take photographs, rather than have it attached to the computer.)
A LR generated preview will only be rendered after the import of the NEF.

My Bridge update 5.2.0.4 has wrecked previews for all DNG files. They appear only sideways and small and I can't open Camera Raw in Bridge. Anyone else have the same problem?

I updated Bridge yesterday. CS6 5.2.0.4. Mac OS 10.9.5
Now all previews (DNG files) in Bridge appear sideways and only small thumbnail size.
Also Camera Raw has been disabled.
I have tried purging cache for the folders as well as purging entire cache.
I have also spent over an hour on the phone to tech support which mainly involved being switched between departments and trying to understand anyone on the phone.
Can anyone help?

Your Performance preferences screen capture reveals you have a single hard drive with little available space to accommodate both the Photoshop scratch file and the swap files of the OS.
It's obvious that Bridge finds itself at times with insufficient space to build its cache.
However, it's unclear why that should affect only DNG files and not other type of image files. Puzzling, unless the DNG files are the only large image files you have.
Parts of the following may illustrate what happens when the scratch file is on your boot drive:
The rule of thumb I follow to figure out scratch space says to figure on 50 to 100 times the size of your largest file ever multiplied by the number of files you have open. I have seen the scratch file exceed 800 GB once, an admittedly rare occurrence, but it often exceeds 200 GB when stitching large panoramas and the like.
As an example—and stressing that I'm aware that others have even more scratch space than I do—I keep two dedicated, physically separate hard drives as my primary and secondary Photoshop scratch disks and a lot of GB free on my boot drive for the OS. I also have 16 GB of RAM installed.
Additionally, if you only have a single HD, i.e. your boot drive, you'd need it to be large enough to accommodate both the swap files of the OS as well as Photoshop's scratch.

Lightroom and Samsung GX-10 DNG files

Hi
i've got a problem with LR and the samsung GX-10 DNG file format.
It semmes that LR does not read correctly this Raw file
at the begin of the rendering, the image has good colors but they change at the end of the rendering. Colors are more dark and finally the photo is not nice.
I've done the same test with raw therapee and the rendering is better.
Have you got informations about.
It's such a pity because LR is great. i like it !
regards

yeah,, I know about raw data , and yes, wrong or not, the rendition of gx-10 pictures are very "bad" compared with other softwares and with my eyes, and I think that you can understand when i said "bad" no?, there aren't a wrong or correct in raw color but the people speaks about the wrong o correct colors all the time, i think that you understand when speak about bad colors, a bad WB , etc.
I know that i can make my own profile but is not easy, to generate a good profile I need a Macbeth ColorChecker or something like that for example and precise sources of light (like a tungsten) and taking account about that samsung cameras are "clones" of the pentax ones and that samsung shoots in DNG format (and not a propietary raw format) seems easy solve the problem about color interpretation of GX-10. With time I will buy a color-checker and try, but would be great a correct interpretaion of the own samsung colors
PD2: When i know about samsung "adobe-DNG" capacity, i didn't expect have problems with adobe soft and color intrepretation or something like that.
PD: Sorry , I don't speak english well, and so I can't express me very well , only basics

EXIF Data Lost for Edited DNG Files

I'm having an issue where my photo's EXIF data is lost when I export the picture from iPhoto. This only happens after I edit a RAW (DNG) file and export it. If I export the RAW file before editing the EXIF data is fine. Is this a bug?
System Info:
iPhoto v.7.1.3
RAW format type is Adobe DNG.
Camera is Pentax K10D
Mac OS X v.10.5.2.

I've been having the same trouble for a few months now. All EXIF is lost, including GPS and focal info. It only occurs when you edit a RAW/DNG file and have the "save edits as 16-bit tiffs" selected in the preferences. Please, Apple, help! This is a significant issue when exporting photos! That info is essential.
thanks,
Brett

Sidecar .xmp for a DNG file ...

Photoshop CS6 Reference says that "When a DNG file is processed in Camera Raw, the settings are stored in the DNG file itself, but they can be stored in a sidecar XMP file instead." How can I store the changes made to a DNG file in a sidecar file? Thanks.

Complete paragraph: "When a camera raw image file is processed with Camera Raw, the image settings are stored in one of two places: the Camera Raw database file or a sidecar XMP file. When a DNG file is processed in Camera Raw, the settings are stored in the DNG file itself, but they can be stored in a sidecar XMP file instead. Settings for TIFF and JPEG files are always stored in the file itself."
And it adds at the end of the same page: "If you want to store all adjustments to DNG files in the DNG files themselves, select Ignore Sidecar “.XMP” Files in the DNG File Handling section of the Camera Raw Preferences dialog box."

Using DNG SDK for 10bit DNG files

Is there any simple way one can use DNG SDK to write 10bit DNG files?
From what I have seen, DNG SDK can only validate/read/write 8 or 16bit files. I have quite a lot of 10bit raw data to be saved and performing a 16 bit conversion would be both time and space consuming.
If there is no simple workaround to achieve this, is there any chance for future SDK versions to support nonpower of 2 pixel bit depth?
Thank you for your time.

> See these specifications for more information on TIFF and TIFF-EP
I do know that specification. However, DNG deviates from the normal TIFF in enough points to warrant explicite specifications, particularly because several cameras' raw data is compressed in like but not identical ways.
> I'm curious if CR will open 10bit DNG....
The Pentax K10D creates 12bit, uncompressed DNG in this packed format and that will be processed by ACR correctly, so I guess you won't have any problem.
On the other hand, it is interesting, that the DNG converter stores 12 and 14bit data in 16bit form, thereby avoiding the issue; a huge waste of space.

Problem diplaying dng files converted in Lightroom

When I import my RAW files into Lightroom, I convert them to .dng files. They display just fine in Lightroom. However, when I try to open them in Irfanview or Thumbsplus, the image is broken up into broad hoizontal bands with some of the image missing betweeen the bands. I suspect that this is a windows problem since it happens with two different windows applications. Here is an example.
Anybody have an idea where this error comes from?
Nat

Thanks for your help. I did some searching on the ifanview forums. According to somone there, this problem can be avoided by disableing "fast load embedding" when importing RAW files. I have not been able to confirm this as I have not yet figured out how to import them without "fast load embedding". However, it seems like a nice feature that I don't want to disable. I guess, for now, I will just import my RAW files and not convert to .dng.
Nat

Lightroom not finding DNG files in the folder

I am using Lightroom 2.5. My library includes a folder with approximately 5000 images which is located on an external hard drive as is my Lightroom catalog. I use the external dive because it is part of a RAID 1 array to backup my images.
My problem began when I used Lightroom to convert the 600 RAW files in the folder to DNG files. Prior to the conversion, the library tab showed that there were 5000 files in the folder. After the conversion, the library tab shows that there are only 4400 files. The DNG files are actually there but Lightroom will not recognize them. I can use windows explorer to see them and that there are 5000 files in the directory.
I have tried to synchronize the folder, but it did not help. I have also tried to write metadata to the files to make sure that was not the problem and it was no help. As a test, I also copied the directory to my local hard drive and imported that into Lightroom. That folder has the correct 5000 images, but of course non of the ratings that I had applied to the 5000 files to organize them so the local folder is useless.
Can anyone suggest a means of convincing Lightroom that it should recognize the missing DNG files that are actually there?
Thank you.

John,
Thank you for your suggestions. I do have filters off.
I started up Lightroom today and again, the Folders tab only showed that the folder had 600 files which corresponds to the missing 600 DNG files. Furthermore, in the grid view, only the 600 DNG files were appearing. But, after a minute and without my input, Lightroom loaded up the 4400 JPEG images into the grid and the DNG files disappeared both from the file count and the grid view.
When I look at the All Photographs folder in grid view, I can find the missing DNG files so they are in the All Photographs folder.
I did as you suggested and I optimized the catalogue. Now when I launch Lightroom, I see the missing 600 DNG files in the grid view and the file count for the folder. But that only lasts a few seconds before the 4400 JPEGS appear and the DNG files disappear. So the optimization made the loading faster as it should, but did not help Lightroom to find the DNG files.
Now when I try to synchronize the folder, It does show that there are 600 files to be added. However, synchronization does not help and DNG files are still missing.
I can see the DNG files in a folder called “Already in Catalog” from when I tried to synchronize the original folder. After optimizing the catalog, I told Lightroom to write metadata for the DNG files. Once I did that, some of the missing DNG files did appear in the grid view of the original folder (but not all of the 600 missing files). However, the library still only shows 4400 files in the folder.
One last oddity. When I change the sort to “user order” from “capture time”, I see only the 600 missing DNG files in the grid view. The 4400 JPEG files are gone. But when I change the sort back to capture time, the JPEG files and the few DNG files are there again and most of the DNG files are gone.
This bugginess is only occurring on the external drive. The same files saved to the local hard drive all appear in the file count and the grid view.
Thank you.

Dng. files from LR to PS CC ok Can't open in Camera Raw?

I have LR 5.7 and can edit my dng. files in PS CC but I can only get Camera Filter not full camera raw w/ all the tools. I am a PC user, BTW.
How do I open full Camera raw for a dng. file?
Thanks, very frustrated.
Chris

Because it was edited in lightroom first, photoshop knows enough to bypass camera raw since the controls are identical. If you open the dng file using the normal way like any other format, then it would open in camera raw first.
Keep in mind if you already did any editing in lightroom, those edits needs to be saved to that dng file before you can do the above otherwise camera raw and photoshop will not see the edits you did.
To save a file in lightroom select the file in the library and use ctrl-s to save.
If you do the above, lightroom will not automatically see the changes done in camera raw or photoshop. In library view there will be an icon in the thumbnails corner. This appears when changes to the metadata do not match that of lightroom's database. Clicking the icon should provide a dialog box asking if you want to update lightroom or leave it unchanged.
If you do a folder full, you can sync that folder to update all of them. Keep in mind syncing overwrites your changes in lightroom so make sure that is what you want to do.
I personally try to make it a habit to save all the images from lightroom, just so I don't get any surprises when syncing. There is an icon in the corner of those that need saving.

I'm considering buying CC LR/PS package. My camera is Sony a7 - raw ARW. I've been editing using PSE10 and ver 8.7 of the external Adobe DNG converter. Will I be able to open the DNG files in LR with the edits preserved? Will I be able to open the PSD fil

I'm considering buying CC LR/PS package. My camera is Sony a7 - raw ARW. I've been editing using PSE10 and ver 8.7 of the external Adobe DNG converter. Will I be able to open the DNG files in LR with the edits preserved? Will I be able to open the PSD files in LR with the edits preserved? Any import/catalog etc issues between PSE10 and LR?

Lightroom has no problem reading DNG files. Whether the edits you have done to the DNGs you have originally edited in Photoshop Elements 10 I'm not sure. ACR edits made to DNGs are saved in the DNG file itself, as apposed to a XMP sidecar file, so LR should see those edits. At the worst you will get an exclamation mark in the upper right hand corner of the imported DNGs and clicking on that exclamation mark you will get a dialog box asking you to either import settings from disk or overwrite settings. you would select import settings from disk.

Develop settings lost after re-importing folder of DNG files

I've been using LR for several months, and - after getting accustomed to its peculiararities - love the program.
This evening I re-imported a folder of DNG files that I had previously removed from LR - using the "add" import option. When going to the Develop module, I noticed that my original develop settings were no longer applied.
Aren't these settings incorporated into the DNG files? How could they get lost? Are they over-written when re-importing the files?
I always backup my catalog before closing. Does the catalog backup contain the original develop settings for these DNG files?
I know I must have done something wrong! Please advise & explain. Thanks.

Seven_D wrote:
Thanks. I do have autowrite to XMP checked. - I learned that lesson a few months ago!
I will see if I can use an older backup to recover the settings. I have never done that before, but I know where my catalog backups are located. If you can give some advice on that, I would appreciate it. I don't want to lose other DNG edits in the process.
Correct me if I'm wrong - but it appears that if I ever do want to remove a previously imported folder from LR for whatever reason - I should just edit the RAW files without converting to DNG. I know DNGs are more compact, but at least the sidecar files associated with the RAW files will always be there! This is more important to me than conserving disk space!
just try it on one or tow files to test. Also look at "Read Metadata from file" in the current catalog first with ine file to see if that helps. Did you have a Prest applied when importing like Zeroed?...... None is the best for importing files with dev settings already applied.
I use DNG exclusively and haven't experienced your issue so review your import settings as mentioned.

Photoshop CS5 photomerge with dng files crashes

hello and greetings from Finland,
I have constant problems with photomerge tool when using dng files converted from Nikon´s nef files. Photomerge loads all pictures, normally 4-6, starts to align them etc. process seemst to be running just fine. Just before finished panorama picture should appear to screen, photoshop returns to default state. With original nef files, everything works just fine. This happens only with dng files. I´m using iMac (i5 processor with 12 GB RAM, cache for Photoshop in separate HD etc.)
So far I have tried following tricks for this problem; several resets for Photoshop settings file and reboot after that. Uninstalled and reinstalled whole Ps twice. Used two different, formatted memory cards in camera (Nikon D700).
After those, no help. Maybe second reinstall gave some relief for this, dng files worked fine couple of times, but now I have that same error again and I´m running out of ideas what to do next. And once again, I have this problem only with dng´s.
Any similar experiences? Did you managed to get things work again? How?

I don't mean to break your rocks, Chris, but try to keep some perspective... A component of Photoshop exiting abnormally (and delivering no results) is a crash to any user who doesn't have a deep insight as to how it's implemented. Maybe it's not as serious as a "whole Photoshop crash with loss of data", but it's not an unreasonable interpretation.
"Not finishing" could be your internal definition of it, and I might even agree with your terminology if it just popped up a message saying "The price of tea in China has risen too high - Photomerge must exit", but just quitting without any message is a crash by any reasonable definition.
Regardless of what Adobe may say, rillumarei, I personally have come to believe Camera Raw leaves some corruption of memory somewhere as I've found any editing session after a Camera Raw run seems a little more likely to fail than one where a PSD or other "normal" image format is opened (without Camera Raw).
-Noel

Lightroom 32bit mode for 32bit DNG files

Similar Messages

Maybe you are looking for