Bug in Camera Raw's tone curve?

Phil Harvey has released ExifTool 8.04 yesterday, and in the release notes he says, 'WARNING: Some Adobe utilities (Camera Raw 5.6, DNG Converter 5.6, Lightroom 2.6) have a bug which causes the tone curve to be incorrect for edited ARW images from some Sony cameras (A500, A550, A700, A850, A900, and maybe others)'.
Can any Sony Alpha users confirm this? And will there be an intermediate bug fix, or will we have to wait for the next ACR version? Does anyone know when the bug was introduced, i. e. does it make sense to revert back to ACR 5.5?
UPDATE: I have tried editing an A900 ARW raw file with ACR 5.6. I have changed the tone curve, saved the file, inspected the XMP file, loaded and edited the raw file again, saved it again, inspected the XMP file again. As far as I can tell, no problems with the tone curve. So I am wondering if Phil's allegation holds any water in the first place, and if so then under which circumstances the bug will emerge.

This means, that offsets within a tag are wrongly assumed to be fixed; my comment above related to the offsets to the tags themselves.
Sorry for the confusion.
Gabor

Similar Messages

Camera Raw Default Tone Curve Function / Coordinates

Hi,
I would like to know where I can find the function / coordinates for the Lightroom / ACR default tone curve that is applied to any image.
I think it's the red one in that image, or it's very very close:
I want to generate a lookup table to match it's effect. For now I plotted something that is very very close but I lack precision at the bottom of my curve.
Cheers,
Thomas

I'm confused - I thought the default was linear. I mean, this is probably not what you want, but here is a curve which makes PV2012's linear tone curve equivalent to PV2010 linear, or at least that's how I call it:
<dngclr:ToneCurve rdf:parseType="Resource">
<dngclr:Edit0 rdf:parseType="Resource">
   <dngclr:X>0</dngclr:X>
   <dngclr:Y>0</dngclr:Y>
</dngclr:Edit0>
<dngclr:Edit1 rdf:parseType="Resource">
   <dngclr:X>17</dngclr:X>
   <dngclr:Y>26</dngclr:Y>
</dngclr:Edit1>
<dngclr:Edit2 rdf:parseType="Resource">
   <dngclr:X>34</dngclr:X>
   <dngclr:Y>44</dngclr:Y>
</dngclr:Edit2>
<dngclr:Edit3 rdf:parseType="Resource">
   <dngclr:X>51</dngclr:X>
   <dngclr:Y>60</dngclr:Y>
</dngclr:Edit3>
<dngclr:Edit4 rdf:parseType="Resource">
   <dngclr:X>68</dngclr:X>
   <dngclr:Y>74</dngclr:Y>
</dngclr:Edit4>
<dngclr:Edit5 rdf:parseType="Resource">
   <dngclr:X>85</dngclr:X>
   <dngclr:Y>89</dngclr:Y>
</dngclr:Edit5>
<dngclr:Edit6 rdf:parseType="Resource">
   <dngclr:X>102</dngclr:X>
   <dngclr:Y>105</dngclr:Y>
</dngclr:Edit6>
<dngclr:Edit7 rdf:parseType="Resource">
   <dngclr:X>119</dngclr:X>
   <dngclr:Y>120</dngclr:Y>
</dngclr:Edit7>
<dngclr:Edit8 rdf:parseType="Resource">
   <dngclr:X>136</dngclr:X>
   <dngclr:Y>135</dngclr:Y>
</dngclr:Edit8>
<dngclr:Edit9 rdf:parseType="Resource">
   <dngclr:X>153</dngclr:X>
   <dngclr:Y>151</dngclr:Y>
</dngclr:Edit9>
<dngclr:Edit10 rdf:parseType="Resource">
   <dngclr:X>170</dngclr:X>
   <dngclr:Y>167</dngclr:Y>
</dngclr:Edit10>
<dngclr:Edit11 rdf:parseType="Resource">
   <dngclr:X>187</dngclr:X>
   <dngclr:Y>183</dngclr:Y>
</dngclr:Edit11>
<dngclr:Edit12 rdf:parseType="Resource">
   <dngclr:X>204</dngclr:X>
   <dngclr:Y>200</dngclr:Y>
</dngclr:Edit12>
<dngclr:Edit13 rdf:parseType="Resource">
   <dngclr:X>221</dngclr:X>
   <dngclr:Y>218</dngclr:Y>
</dngclr:Edit13>
<dngclr:Edit14 rdf:parseType="Resource">
   <dngclr:X>238</dngclr:X>
   <dngclr:Y>236</dngclr:Y>
</dngclr:Edit14>
<dngclr:Edit15 rdf:parseType="Resource">
   <dngclr:X>255</dngclr:X>
   <dngclr:Y>255</dngclr:Y>
</dngclr:Edit15>
</dngclr:ToneCurve>

LR 1.1 - Bug with Camera Raw resolutions?

I don't know that this is necessary, but in case this is a bug, I am posting it here, as well as in the help forum. Is it my imagination or am I missing some obscure Lightroom Preferences setting?
When selecting Edit in Photoshop, Lightroom 1.1 seeems to ignore the Camera Raw resolution settings for Nikon .nef files. While I have Nikon's recommended D1x natve resolution set for Photoshop's Camera Raw Plug-in (5.9MP - 3008x1960 @300ppi at 8-bits per pixel), when a selected .nef file is opened through Lightroom, it comes into Photoshop using all the D1x pixels (10.5MP - 4011x2613 @240ppi at 16-bits per pixel).
Is this yet another Lightroom resolution bug?
Did the same problem occur with the beta and 1.0 versions of Lightroom?
Why are all these Preference Settings hidden away in so many different places, and then not communicating with one another? If they must be set up in different dialog boxes for each application, you should be able to get to all related Preferences for Lightroom, Camera Raw and Photoshop in one place -- ideally the Photoshop Preferences dialog boxes.

No need to double post one forum section is enough.
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.10 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

Bug? Camera Raw Smart Object Can't Be Edited

I have a problem where a raw file placed as a smart object can't be re-edited in CS3. Here's how to replicate the problem:
1. Open a JPEG or TIFF as a Smart Object (may happen with other file types).
2. Go to Layer > Smart Objects > New Smart Object via Copy.
3. Double-click the top smart object and make changes in Adobe Camera Raw.
You should now be able to hide/show the top layer (the final)
to see the bottom layer (the original.)
4. Double-click the top smart object layer to see that it properly opens Camera Raw allowing you to make edits (this works for now but will stop working when we encounter the bug in a moment).
5. Save the file and close it.
6. Re-open the file and double-click either of the smart object layers to edit them. Instead of Camera Raw dialog opening, the image in the window changes to the original unedited version. This is a bug and doesn't happen on every image, but it always happens on at least some of my images.
There have been times when it works, but the next time I open the file it stops working. Some of my files allow editing later without problems. Truly weird. Has anyone else had this problem? Is there a workaround?
I have applied all updaters, so that means I am using Photoshop CS3 10.0.1 with Camera 4.4.1 on Mac OS 10.5.2. I have also trashed preferences for Photoshop and Adobe Bridge. I've also Purged the Adobe Camera Raw Cache in the Bridge. This happens on both my Mac Pro (3GB RAM) and MacBook Pro (4GB RAM) so it's not just one machine.
Thanks in advance,
Dan

Hi Daniel,
Stumbled on your post while searching on a similar issue. I'm not sure if I precisely understand yuour problem, but here's my experience when dealing with TIFFs and JPEGs embedded as Smart Objects in CS3...
If the Smart Object layer contains a TIFF or JPEG that has already been edited and saved in Camera Raw (i.e., the embedded file has Camera Raw XMP metadata in its header), then Photoshop will open the Smart Object's contents in Camera Raw... with one provision. You have to make sure that in your Camera Raw preferences, under "JPEG and TIFF Handling", that both boxes are checked for "Always open JPEG/TIFF files with settings using Camera Raw".
If those boxes aren't checked, when you try to edit the contents of a Smart Object layer containing a TIFF or JPEG with Camera Raw settings in its header, instead of opening the embedded file for editing, Photoshop seems to simply revert to displaying the layer without the settings applied. I'm unsure whether this is a bug or intended behavior, but it seems to be one of the symptoms you describe.
On the other hand, if you make a Smart Object layer from a JPEG or TIFF that does not already have Camera Raw settings in its header, Photoshop CS3 will never open that layer's contents in Camera Raw, regardless of what preferences you have checked. Instead, the contents are opened in a separate window as a temporary .psb file. The only way I've found to do Camera Raw editing in these cases is to export the layer, edit the exported file in Raw, and then re-import it via Replace Contents.

Bug in Camera Raw

I think this was introduced with ACR 6.6 RC ... but I'm not entirely sure, as the bug seems to be transient.
The problem basically is, when adjusting an image in Camera Raw and hitting Ctrl+Z while the preview is zoomed in to 100 % view or larger then the enlargement will snap back to "Fit in View". However this will happen only sometimes, not always. I have not yet found out which preconditions must be met in order for the bug to happen. The last thing I tried was a DNG 1.0 file from a Leica M9 camera, portrait orientation, cropped to 4:3 aspect ratio, some capture sharpening added (including Mask), preview enlarged to 400 % view. Upon trying to decide whether I want Colour Noise Reduction 10 or 20, I wanted to toggle between the two settings via Ctrl+Z but the preview kept switching back to "Fit in View" every time I hit Ctrl+Z.
The behaviour can sometimes be reproduced with other images from the same camera, and sometimes not. I wasn't able to reproduce it with images from other cameras ... not yet.
Operating system: MS Windows XP SP3 (32 bit)
CPU: AMD Athlon 64 X2 Dual Core 6000+
RAM: 4 GB installed, 3 GB used
Graphics card: ATI Radeon HD 2600 Pro

johnkwon9 wrote:
Have you been able to reproduce this issue on images before/without applying a crop?
No, I haven't. In fact, currently I am unable to reproduce the issue at all. I deleted the .8bi file of ACR 6.6RC and replaced it with a backup copy of the .8bi file of ACR 6.5, to check if the issue would appear with that version also (it didn't). Then I deleted the .8bi file again, to replace it with a backup copy of the .8bi file of ACR 6.6RC (I did not re-run the ACR setup procedure but just copied the .8bi files manually). Since then, the issue didn't appear anymore. It seems my original .8bi working file somehow was corrupted, and deleting and replacing it with a backup copy apparently solved the issue.
If the issue re-appears then I will report it here immediately.
EDIT: Umm ... I just found out what the "issue" actually is. It's just me. Hitting the Z key (without the Ctrl modifier) will select the Crop tool and zoom to "Fit in View" when a crop has been applied. So the issue appeared whenever I wanted to press Ctrl+Z but actually hit just Z inadventently (pressing the Ctrl key too late or not fully). So the issue is solved. Sorry for the flurry!

Camera RAW auto tone settings applied to jpegs

I posted this in the Windows Bridge forum, but a camera raw preference controls this so I am also posting here.
On jpeg files without any RAW setting applied, Bridge still applies RAW settings to the thumbnails and the preview are thus display incorrectly. Opening the file shows the jpeg as it should be, without RAW settings applied.
I have RAW preferences set to apply auto settings to RAW files without any current settings.
I have my RAW settings to open jpegs in RAW *only* when they already have settings. If I set this to disable jpeg support, then the RAW settings are not automatically applied to jpegs without existing settings. aka, Bridge redoes the thumbnails without the auto setting.
While it is correct to apply auto tone to RAW files without settings, jpeg files are already "developed/printed" and should not get additional auto develop settings automatically applied.
My Bridge is 4.0.4.2
Raw is 6.3
-Norman

I posted this in the Windows Bridge forum, but a camera raw preference controls this so I am also posting here.
On jpeg files without any RAW setting applied, Bridge still applies RAW settings to the thumbnails and the preview are thus display incorrectly. Opening the file shows the jpeg as it should be, without RAW settings applied.
I have RAW preferences set to apply auto settings to RAW files without any current settings.
I have my RAW settings to open jpegs in RAW *only* when they already have settings. If I set this to disable jpeg support, then the RAW settings are not automatically applied to jpegs without existing settings. aka, Bridge redoes the thumbnails without the auto setting.
While it is correct to apply auto tone to RAW files without settings, jpeg files are already "developed/printed" and should not get additional auto develop settings automatically applied.
My Bridge is 4.0.4.2
Raw is 6.3
-Norman

Bug in Camera Raw 8.4?

I have Photoshop Elements 12, and have just updated to get the new version of Camera Raw for opening my files. What I've noticed is that if there are dark bits which are almost black they show up bright blue, as if it's some kind of warning like with highlight blow-out. It is very offputting! Any idea if this is a bug in the new version or is there some setting I can change to make it go away?

You nailed it: the blue spots are an indication that there is severe underexposure. Look at the small squares in the upper left and right part of the histogram : click on them to hide/show those indications (blue for shadows, red for overblown highlights).

Bizarre bug in Camera Raw 7.3 or Adobe Algorithms??? Grayed out areas of the image

When converting raw files from Nikon D600 using CR 7.3 parts of the image appear grey and save that way. Converting to TIFF using Adobe DNG Converter didn't help but viewing and saving to TIFF in Preview showed none of the artifacts. Very bizarre and I am really looking forward to an explanation and hopefully a fix! Tried it on two machines now - same problem!!

The example photo had Defringe values were set too extreme for the picture content. Here is a lynda.com video that shows how to back things off based on what you see on screen:
http://www.youtube.com/watch?v=cMfoLcfn8W8
Images should initially be opening with zero Amount values for Defringing. This is how my defaults are:
If not, then reset your camera raw defaults to the factory defaults:
After doing this, then if you really want something different than the factory defaults, open a new image, set those values and use the Save New Camera Raw Defaults item just above.

Bug on Camera Raw?

Hi Everyone,
I've seen this on Camera Raw:
Contrast bar in one photo appears bellow Brightness, an on another one appears bellow exposure.
On Photoshop CS5 it worked perfectly. It just started to happen now with cs6.
Any solution?

I have issues with this new process.
1. The old interface seems much more intuitive to me. I would like the option to keep it. Seems like once you swith versions, you are forced to switch interfaces and processes. Perhaps I will try and fathom what the new measures are relative to the old ones. Perhaps I will wait for a more stable version with more help to decide whether I want to go this route.
2. The old and new processes do not record the same thing. Below is an image edited in Camera Raw 6 then pulled into Camera Raw 7, before and after converting to the 2012 process. Clarity was set to 37 and the new process changes that to 18. I don't really understand these "processes" but my guess is that Clarity is a different process in the newer version. I trust PS will know forever how to interpret these processes in rendering images. Or is this a mistake?

Bugs in camera raw 7.1 plugin?

Found some graphics bug in ACR 7.1. Known issue?
Look at the linked image. In the boxes where the numerical values are you can see some artifacts.
PS CS6 Ext, Macbook Pro 15'' mid 2009 with fresh Mountain Lion install.
http://bildr.no/view/1245661

Why do you assume, after upgrading to a new OS from Apple, that anything will work afterward? It's not like Apple gives a dang about maintaining compatibility with anything you already have.
-Noel

Camera Raw - Enable RGB Tone Curves

In Camera Raw, the Tone Curve Channel selection is disabled. How can I enable it to allow me to adjust specific colors in Camera Raw?
I’m using Photoshop CS5, Camera Raw version 6.7.0.339 on a Windows Vista 64 bit system, and my camera is a Nikon D90.
Thanks,
Jack

I don't think you can...ACR 6.7 was a crossover version tho have compatibility with LR 4 when it was released, as a result it was set to allow processing of certain features that were in LR 4 (and ACR 7). While the RGB curves show up dimmed, I don't think ACR 6.7 allows actually adjusting the RGB curves. I think the only way to get them is update to CS6 and ACR 7.x.

RGB Channel unavailable in Camera Raw under point in the Tones Curve

How can I use the the RGB channel in Camera Raw under Tone Curve?

Hi yariel83,
Make sure under the Camera Calibration tab that the Process is set to 2012.

LR4: tone curve settings lost after upgrade

I've find an annoying bug in this new version that makes me really crazy.
I've a Nikon D300S and a D7000.
After the importation of the catalog in the new Lightroom 4 all the D7000 .dng files have lost all the tone curve settings (I normally use linear).
The D300S files instead retain the tone curve settings.
It's a very strange behaviour: I've lost more than half of my old photo settings.
It's really frustrating.
Will be resolve soon this problem?
Until that day, for my older works I'll be obliged to continue to use LR3.

I've probably found a sort of workaround!
I've made some "organized" tests and here I report my findings.
Using LR3.5, I prepared a "test catalog" using 4 images from 7 different cameras (28 images total): for each of them, I used both the original nef and the dng converted file (56 files in the catalog), all develop process was set to "2010".
The cameras were Nikon D70, D90, D200, D300s, D700, D5000, D7000.
I applied a strong tone curve to each image in a way that the appearance was heavily characterized.
Before exit LR3.5, I SAVED ALL THE METADATA TO THE FILES.
Opening and converting the catalog using LR4, doesn't show any visual change until I zoom in library or open the develop module: both these operation lead to a flat image with the strong tone curve lost.
Curiously, the history retains the original steps but they are ineffective: histogram and tone curve changes according to the visual change but for some camera the "new" tone curve is "medium contrast", for others (D5000, D90) is "linear", for D300s is "custom" (linear with blacks cut at 9.8%, and this explain my initial impression that D300s's curves were untouched, sorry). This last behavior may depend on the fact that I've different default develop settings depending on the camera serial number.
Finally, the update to the 2012 process only minimally changes the visual appearance and surely doesn't restore the lost tone curves.
And here is the UNEXPECTED WORKAROUND: doing a READ METADATA FROM FILES IT RESTORES THE TONE CURVES (and the 2010 process)! Upgrading the process to 2012 minimally changes the visual appearance again but now the strong tone curve is present and evident.

Does anyone know any detailed tutorials about Tone Curve of Camera Raw on the Internet?

Does anyone know any detailed tutorials about Tone Curve of Camera Raw on the Internet?
I need deeper more detailed instructions and tutorials than the official Photoshop Help.
If anyone had a useful link, please let me know. THANK YOU

A Google serach brings up a bunch, such as
http://photoshop.digitalmedianet.com/articles/viewarticle.jsp?id=354032 (with QT video)
http://www.luminous-landscape.com/videos/CR_1.shtml
http://www.google.com/search?hl=en&q=tutorials+about+Tone+Curve+of+Camera+Raw&btnG=Google+ Search&aq=f&oq=

Lightroom 2.6 trial version camera raw tone curve questions + 4 more

1- How do you reduce the 100% point on the curve (upper right) and raise the 0% point black portion as can been executed in CS4 photoshop bridge camera raw? Example I want a photo adjusted to have a 5% dot value in the white area and a 95% dot value in the black area. Note: CS4 bridge camera raw can lower the white point and raise the black point by pulling the points up or down.
2- After cataloging three internal drives how does one do a search across the three(3) drives simultaneously to find a file name to look for redundancy or whatever without launching each catalog separately?
3- How can an initially created catalog name be changed after the catalog is created?
4- How can a file or several files be added to a catalog after the catalog is created - is there a way to immediately refresh to show newly added files?
5- Is there a way to show Illustrator CS4 files in lightroom 2.6 or a utility to convert them to acceptable LR formats to be visible?

vic,
1. You can do this natively in the LR3 beta 2, but not easily in LR2. You can edit the curve in Camera Raw and save it as a preset, then import that into LR. I don't know the details, but I've seen posts here that talk about it.
2. You can't. That's why it's lots better to have only one catalogue. The images can be spread across as many drives as you want, and that one catalogue can keep track of them all.
3. Use your operating system to rename the catalogue file and its associated top-level folder of previews.
4. You can Import or Synchronize.
5. LR will just deal with JPG, TIFF, DNG, PSD, and various raw files. I don't know of a utility that will convert Illustrator files to one of those formats. If I were you, I'd search in Google.
Hal

Bug in Camera Raw's tone curve?

Similar Messages

Maybe you are looking for