ACR 6.1RC Presets

Hi,
I tend to use a set of presets as a starting point for capture sharpening in ACR (one for portrait, one for landscape etc). When I saved these only the sharpening box was ticked - so that they only affect the sharpening and do not alter any other ACR parameters. However in ACR6.1 when I apply one of these presets, the sliders on the "basic" tab i.e. exposure; brightness etc all return to their default value instead of remaing unaltered. This is annoying as I tend to work left to right along the tabs.
I have tried recreating one of these presets in ACR6.1 and the effect is just the same.
Am I doing something wrong or is this a bug?
(In case it makes a difference, I am using ACR6.1 in CS5 on a windows Vista 32 bit system).
Dave

Thanks Jeff.
From your answer it sounds like it's already been spotted :-)
If not, do I need to report it anywhere specific for 6.1 or just on this forum?
Dave

Similar Messages

Clear Settings Anomaly in ACR 7.1rc

First, a bug: when you click Clear Settings in ACR 7.1rc (Mac version, at least), the Edit menu highlighting stays on after the operation is complete.
Second, Clear Settings in ACR 7, when applied to DNGs that have had settings made in earlier versions of ACR, are not cleared. Only the additional settings made in ACR 7 are cleared.
This latter may be intended. But, if so, it would be useful to have an additional menu item that Clears All Settings.
Edit: Indeed, I notice that several items leave the menu highlights stuck on. For instance, if one looks at the Camera Raw Preferences, the Adobe Bridge CS6 menu item remains highlighted even after you dismiss the preference pane.
Edit_2: The Clear Settings now seems to be working. I guess, perhaps, it took Bridge some time to update its cache. It certainly wasn't working right after installation.
But the various menu highlights still do not turn off when they should, as reported above.
It seems the menu on/off logic needs a rather general cleaning up.
grampus45

None of the issues reported on this forum have been fixed in Camera Raw 7.1, near as I can see.
The Camera Raw 7.1 software was built on May 15, but Adobe appears to ignore beta feedback unless it's a real show-stopper. I can only imagine the definition of "show-stopper" must include users' systems actually catching fire or something.
Camera Raw 7.1 puts columnar color artifacts like this into images, for example:
Compare the above to the same conversion done with Camera Raw 7.0:
Plus Adobe has removed several color-fringing reduction features without providing suitable substitutes.
I recommend eveyone avoid upgrading to this release.
-Noel

Set whitebalance to a minimum, from inside ACR itself (ie preset)

Hi there
I'm a web/mobile developer but have never scripted in Photoshop much... and I don't want to learn what I don't have to
What I want: when i'm in Bridge -> ACR going through 500 images, I use a preset to set things (ie. get an image style). Now, I find that some of my cameras often have a white balance that is too cool... so, I want a "preset" (or script? or whatever I can click / batch / use from ACR or Bridge easily) that can leave the white balance as it is, UNLESS it is under some minimum I specify (ie. 4400), in which case it is raised to that minimum.
I know it probably sounds weird but it would save me a lotta time..
thanks for any help

I had an even better idea: adjust the minimum according to the time of day. Example: 12noon photo should have minimum white-balance of 4900, a photo taking at 8pm should have a minimum white balance of 5500.
OK just point me in the write direction and i'll start

Bridge CS4 does not see ACR presets in Develop Settings

I think that this is new with CS4. I create a Preset in ACR in the Preset Panel. That Preset works fine on photos in ACR. The Preset is listed in the Camera Raw Settings folder in the Finder.
But, when I try to apply the Preset in Bridge via Edit > Develop Settings, the Preset does not appear. Is this correct? I believe that a preset did appear in CS3 in Bridge Develop Settings.
The preset was created with a Raw file from the 1DS MkIII. Could it be camera-related?
Am I missing something here?
Thanks,
Sonny

Strange. I Quit Bridge. Relaunched Bridge, and the Presets now appear in the Develop Settings list.
I presume that I should not have to Quit and relaunch for the presets to appear?
I created another preset. It only appeared in Develop Settings when I again quit and relaunched Bridge, even though it appears in the Camera Raw Settings folder.
Sonny

D200 white balance presets problem or ACR problem?

Last night I was playing around with my D200 and an SB800. The scene was just a sofa with a Gretag-Macbeth 24 Patch Color Checker. The object was to see what results I got with the SB800 with the D200 set to the various preset White balance values. (I should point out that the lighting was mixed, but that is not relevant to the results I see.)
I set the D200 to each of the preset white balance values and then opened the NEF file in ACR. The preset temperature (from the D200 Manual) and the temperature/tint values reported as "As shot' by ACR are shown in the table below.
D200 ACR 'as shot'
preset temperature/tint
tungsten 3000 2950 / 0
fluorescent 4200 3950 / +31
daylight 5200 4950 / -3
flash 5400 6150 / -9
cloudy 6000 5550 / -7
shade 8000 7100 / +3
First of all I don't care if the temperature reported by ACR agrees with the preset temperature quoted by Nikon. What puzzles me is the discontinuity in the values reported by ACR when going from 'flash' to 'cloudy'. Is this a problem with ACR or with the Nikon preset values for these two settings?

>First of all I don't care if the temperature reported by ACR agrees with the preset temperature quoted by Nikon. What puzzles me is the discontinuity in the values reported by ACR when going from 'flash' to 'cloudy'. Is this a problem with ACR or with the Nikon preset values for these two settings?
Bob,
A full answer to your question would require a response by Thomas Knoll or some other ACR expert with knowledge of how Nikon records the white balance and the algorithm used to apply the white balance. However, I can bring up a few points which may shed some light on the matter.
One should first consider what white balance information Nikon cameras write to the NEF file. The following table refers to the D70 and similar Nikon cameras before encryption of the WB.
http://www.ozhiker.com/electronics/pjmt/jpeg_info/nikon_mn.html
The settings of daylight, flash, tungsten, etc are written as descriptive strings, not actual degrees Kelvin. Nikon considers daylight to be 5200K, but Thom Hogan writes that this value often produces a blue result and 5400K might be better.
The bias value refers to fine tuning between the above descriptive settings, approximately 100 Mired per increment. Finally, the red and blue coefficients are recorded (green would be redundant). Some raw converters such as DCRaw use these coefficients for the "as set" white balance. There is nothing corresponding to the ACR tint, which adjusts in the magenta green axis, whereas the color temperature slider adjusts in the yellow-blue axis. The degrees Kelvin figure specifies the white balance only for a black body radiator.
Thus there several ways to interpret the WB data. Mr. Knoll has written previously that ACR attempts to produce a neutral white balance appearance rather than the WB numbers. An interesting experiment would be to determine which converter (ACR or Nikon Capture) gives a more neutral white balance on your color checker with the above settings.
Bill
http://www.adobeforums.com/cgi-bin/webx/.3bbc87b2/0

New Lightroom & ACR 400D Preset Available

I have a set of presets for Lightroom 1.1 and ACR 4.1 that will IMHO improve on the default color rendering from Adobe.
This is currently a beta, so feedback is appreciated.
To obtain the beta please mail me: [email protected]
I look forward to your comments.

Anyone know how to install these presets in XP Pro?
The website has instructions for OSX and Vista
from http://huelight.com/page3/page3.html :
"To install in ACR, Copy the .xmp to your Photoshop 'Settings' folder and select the Olycoly preset in ACR under the 'Presets' tab.
The settings folder is located as follows:-
Windows Vista - /AppData/Roaming/Adobe/CameraRaw/Settings
OSX - /Library/Application Support/Adobe/CameraRaw/Settings "
I can't find " AppData/Roaming/Adobe/CameraRaw/Settings " anywhere in XP.
Furthermore, when I unzipped the downloaded file there are TWO .xmp files. Which of the 2 do I copy?

New Lightroom & ACR 5D Preset Available

I have a set of presets for Lightroom 1.1 and ACR 4.1 that will IMHO improve on the default color rendering.
This is currently a beta, so feedback is appreciated.
To obtain the beta please mail me: [email protected]
I look forward to your comments.

Anyone know how to install these presets in XP Pro?
The website has instructions for OSX and Vista
from http://huelight.com/page3/page3.html :
"To install in ACR, Copy the .xmp to your Photoshop 'Settings' folder and select the Olycoly preset in ACR under the 'Presets' tab.
The settings folder is located as follows:-
Windows Vista - /AppData/Roaming/Adobe/CameraRaw/Settings
OSX - /Library/Application Support/Adobe/CameraRaw/Settings "
I can't find " AppData/Roaming/Adobe/CameraRaw/Settings " anywhere in XP.
Furthermore, when I unzipped the downloaded file there are TWO .xmp files. Which of the 2 do I copy?

Import Presets from ACR

Hello together
Is there a possibility to import existing presets from ACR into Lightroom? I tried to import, but ACR stores the presets in a different file format than lightroom. Is there a chance to import them?
thanks for your replies
- Daniel -

Hi Victoria
Good idea!! Thanks a lot!
- Daniel -

ACR 7.1 Release Candidate Problem

I just installed ACR 7.1 RC on a Windows 7 Professional 64 bit system and identified an issue relative to how ACR 7.0 works. When I select an image that was initially converted using PV2010 (CS5) and click on the "!" on the image to change it to PV2012, make a few adjustments in the Basic panel and then click on the "3 ---" and select "image settings" it changes back to PV2010 with all the settings, but if I then click on the "3---" again to switch back to PV2012 with the settings I made it's already setting in "Custom Settings" and you can't switch between PV2010 and PV2012 using this approach.
If you have any other panel than "Basic" selected it allows you to switch between PV2010 and PV2012 by selecting "Image Settings" or "Custom Settings". You can also switch between PV2010 and PV2012 in the "Basic" panel using this approach if you don't make any changes to the initial PV2012 slider settings.
ACR 7 does not have this characteristic.
Any comments?

I have returned to ACR 7.0 and it does not have the issue described above for ACR 7.1 RC. I am reprocessing images that were already processed with PV2010 and switch between PV2010 version and PV2012 version using the "Image Settings" and "Custom Settings" . I can do this in ACR 7.0 while in the Basic Panel, but not in ACR 7.1RC. In ACR 7.1RC I have to switch to something other than the Basic Panel before I switch between PV2012 and PV2010 using "Image Settings" and "Custom Settings", but after I do this one time for an image I can then do this in the Basic Panel.
This bug needs fixing before the production release.

ACR 7.1 RC Issue Not Fixed in ACR 7.1

The issue I identified in ACR 7.1RC is not fixed in the production release of ACR 7.1. Maybe I did not explain this in enough detail, it's very easy to miss.
1. Select a RAW file that was previously adjusted using PV2010. When you open the file with ACR 7.1 it will open with PV2010 since the xmp file was saved with that process version.
2. Click on the "!" next to the image and it changes to PV2012 with suggested slider settings. Adjust one of the sliders in the Basic Panel - this is very important becasue if you don't adjust a slider the issue does not show up.
3. With the Basic Panel still selected, click on the three dashes to the right of the Basic Panel to get the pop down menu and select "Image Settings". The image changes back to PV2010 with settings that are saved in the XMP file. Now click on the three dashed again to get the pop down menu and "Custom Settings" is checked, but the image is displaying PV2010, not PV2012 like it should if "Custom Settings" is checked. You just lost your PV2012 settings. ACR 7.0 does not have this issue.
4. If in #3 above you select another panel before you click "Image Setting" the first time you can switch between PV2010 and PV2012 by clicking "Image Settings" for PV2010 and "Custom Settings" for PV2012. After you do this first in a panel other than the Basic Panel for the first time you can then do it in the Basic Panel without the problem occuring.
I discovered this while converting images that were adjusted using PV2010 to PV2012 and like to compare the two Process Versions. I did not have any problems with ACR 7.0, but when I installed ACR 7.1RC the issue occured. I was hoping it would be resolved in the Production Release of ACR 7.1, but it's still there.
I am using Photoshop CS6 on a Windows 7 Professional 64 bit computer, don't know if this same issue exists in Lightroom.

None of the issues reported on this forum have been fixed in Camera Raw 7.1, near as I can see.
The Camera Raw 7.1 software was built on May 15, but Adobe appears to ignore beta feedback unless it's a real show-stopper. I can only imagine the definition of "show-stopper" must include users' systems actually catching fire or something.
Camera Raw 7.1 puts columnar color artifacts like this into images, for example:
Compare the above to the same conversion done with Camera Raw 7.0:
Plus Adobe has removed several color-fringing reduction features without providing suitable substitutes.
I recommend eveyone avoid upgrading to this release.
-Noel

ACR 6.1 Release Candidate causing hangup in CS5

I'm running Windows 7 and Photoshop CS5. I've been using the program with ACR 6.0 for about 2 weeks with no problems. I installed AC 6.1 Release Candidate tonight and opened a Canon raw file from a 7D. I did all of my adjustments in Camera Raw and then opened the file in photoshop. When I try to save the file the program goes into a loop and hangs up, basically locking photoshop up and making me have to shut down the computer to reboot it. After the reboot, I went back into the same file again with the same results.
How do I uninstall 6.1 and go back to 6.0?

I have returned to ACR 7.0 and it does not have the issue described above for ACR 7.1 RC. I am reprocessing images that were already processed with PV2010 and switch between PV2010 version and PV2012 version using the "Image Settings" and "Custom Settings" . I can do this in ACR 7.0 while in the Basic Panel, but not in ACR 7.1RC. In ACR 7.1RC I have to switch to something other than the Basic Panel before I switch between PV2012 and PV2010 using "Image Settings" and "Custom Settings", but after I do this one time for an image I can then do this in the Basic Panel.
This bug needs fixing before the production release.

Default Image settings - handling multiple presets?

Default Image Settings allows for presets based upon camera serial number and ISO.
How is ACR handling overlapping presets? Does the addition of choosing the ISO within prefs simply override the noise reduction and leave the remaining presets untouched?
And, ( should be in feature requests ) would it then be feasible to add a pref in the future to make lens correction presets based upon embedded lens data. I realize that zooms often require multiple CA settings but primes can be relatively stable.
thx
pg103 seems to imply that its either serial number or ISO
>Select the appropriate options in the Default Image Settings section of the Camera Raw preferences to specify whether to associate the defaults with a specific cameras serial number or with an ISO setting.

>Default Image Settings allows for presets based upon camera serial number and ISO.
Uh no...it is wrong to consider the per serial/ISO as "presets"...they are "Defaults"...big difference in implication if not concept. The "Defaults" that are set based on ISO/Serial are hard "all in one" defaults that are captured when you make the current settings the default.
Presets can indeed use overlapping presets because you can save out subsettings as presets. That can't be done with Defaults.
As far as the lens corrections thing, expect interesting developments on that front for the next version.

Camera Raw Loses Saturation, Especially Reds

I'm using PSE 5 and ACR 4.3 on Windows. My camera is a Canon 350D and I shoot RAW+JPG.
The problem I have is that photographs with deep/bright reds don't open properly in Camera Raw, but end up "washed out", so I have to really boost the saturation and play around with the white balance to get the reds back. The JPG file which I shot at the same time is absolutely fine, although sometimes the red channel is clipped.
For example, look at the car in the following JPEG. This was taken with auto white balance, and is a fair representation of the actual colour of the car:
Now look at ACR's attempt to open the corresponding RAW file. You can see how the red of the car is much more muted, and a yellower tone:
Can anybody help, and explain how I can get back to nearer the colours captured in the JPEG?
Thanks
Andrew

The issue of the reds in some raw files was recently discussed here:
http://www.adobeforums.com/webx?128@@.3bb6a869.3c0530a0
It's long thread that boils down to something like this:
First, a caveat: there is no antagonism or criticism of any poster intended in my replies to this question. All my replies to posts on this issue are meant to stress that any differences between an ACR conversion and the conversions performed by the camera manufacturer's software may be normal, expected behavior.
If anybody prefers the camera manufacturer's conversion, that too can be emulated in ACR and saved as your own ACR defaults or preset(s). This has been covered ad nauseam here by others as well as by myself. Please do a forum search. If only my posts show up, it means the others have scrolled off already.
Here's the scoop:
Camera manufacturers, Canon and Nikon in particular, perform in-camera RAW to JPEG conversions designed to generate the over-saturated, over-contrasty and over-sharpened images that appeal to the masses.
Their stand-alone RAW conversion software also performs the same conversion to your RAW images.
Noise is also hidden by compressing the shadows so you don't see much of the noise inherent in the image.
In my experience, even the nominally "natural" default settings in these cameras and in the manufacturer's software perform these adjustments to the images, to a lesser but very real degree.
Adobe Camera Raw, ACR, on the other hand, comes with default settings designed to give you the most detail possible (even if this sometimes means revealing some of the noise hidden by the camera manufacturers in their RAW conversion software), as well as the most natural images.
This is only your starting point in ACR.
You can calibrate your camera to ACR and come up with your own settings to produce exactly what you want, including the JPEG-look of the camera manufacturer, and save that as your profile.
The key is to learn how to use ACR properly and to calibrate your camera to ACR.
CLICK HERE for some essential reading.
The ACR defaults are nothing more than a suggested starting point.
The color temperature won't necessarily match either.
These are not
"changes" to the raw file. All raw files are very, very dark, linear, grayscale image with no colors. There is color information included, from which any and all raw converters must create the colors in the converted image according to the parameters of the design of each converter.

Tip: How to emulate Photoshop-style curves in Lightroom

We all remember the days of Lightroom 1 and the term "Adobe red", when lots of people shouted about how their in-camera color is superior to Adobe's rendering. These days are long forgotten, now that we have the DNG color profiles, introduced with Lightroom 2. So, now, if you use the appropriate profiles, the default rendering almost matches that of camera manufacturers.
However, there's one aspect of color quality that, from time to time, reminds me of legacy ACR color. That is when you start adjusting and make more or less strong adjustments with Curves, Contrast slider or other tonal controls.
See how a contrast boosting S-curve shifted the skin tones towards warmer tones in Photoshop and how they look muddy-yellow-greenish in Lightroom?
Original.
Lightroom (left) and Photoshop (right).
I have noticed that warm colors (orange and everything around it) are more affected. Skin tones and some other objects (e.g. wooden furniture) fall in this category. The difference between other colors (blues, greens) is much smaller between Lightroom and Photoshop.
This happens because, curves in Lightroom have been programmed to be smarter and said to have a hue lock. That is, unlike curves in Photoshop or any other program on Earth, where curves affect the luminance, as well as saturation and hue, curves in Lightroom are mostly luminance-based, have a moderate saturation boos and minimal or almost no hue shift. This is described in more details here, here and also confirmed here. Most experts in the field consider Lightroom's implementation to be superior to Photoshop's, because it better preserves the original color.
However, in my tests (you also can easily check HSL values in Photoshop) I have found that not only the skin tone hues will not shift towards a warmer red like in Photoshop, but they will actually shift in the opposite direction — towards yellow and green. Below you can see the hue values of the marker in the photos.
If you, like me, happen to hate those muddy yellow/green skin tones in the shadows, you now have a way to get rid of them. The trick is to emulate Photoshop-style curves in Lightroom. Now that we have per-channel R, G and B curves in Lightroom 4, we can do this by using them instead of Contrast slider or the old composite point curve.
If you find that this method twists the hues too far (e.g. faces are getting too red in the shadows), you can use something intermediate: a blend between moderate R+G+B curves and some Contrast slider. I personally like something in-between Lightroom and Photoshop.
And finally, you need to adjust the three R, G and B curves so that they match perfectly to avoid losing color balance. It's very hard to do it in Lightroom, since there are no number input boxes for curve points. So, it's better to adjust one channel, and then carefully copy it to other in a text editor. I have prepared a collection of R+G+B contrast-boosting curves of different intensity: form Normal to Ultra Strong. You need to place the in your ACR's Curve preset folder. On Windows, it's \Users\<userprofile>\AppData\Roaming\Adobe\CameraRaw\Curves.
Download RGB curves

Thanks Dorin - I've downloaded but not yet scrutinized. -Rob

Photoshop CS6. Windows and Mac pop-up/drop down menus

Hi guys!
I have a problem with pop-up menus in CS6 (13.0.5) and ACR (white balance) under Mac OS 10.8.5.
I have been working with photoshop on PC under Windows for the years. I recently had to switch to CS6 on Mac.
I can no longer place my cursor in the Photo Filter preset mode (or ACR white balance presets) field and use arrow keys to quickly toggle through different presets/modes to find the ideal mode.
I know that with Shift+ an Shift- one can toggle between blend modes (Layers). But these keyboard combinations do not work for Photo Filter and other pop-up/drop down menus.
I used to be able to preview a lot of filters (or other modes) in seconds to choose the optimal. Now I have to click this button and click again on each photo filter. This is lengthening enormous the process.
On my Mac, I can certainly click in the menu and use the arrow key to go up and down but what that does not do is apply the blend mode, unless I also press Return. But pressing Return kicks you out of the menu so you have to start the click/arrow/Enter cycle again, which is a long way just to try the next blend mode.
It is very annoying. Please help! Thank you very much!

Hi guys!
I have a problem with pop-up menus in CS6 (13.0.5) and ACR (white balance) under Mac OS 10.8.5.
I have been working with photoshop on PC under Windows for the years. I recently had to switch to CS6 on Mac.
I can no longer place my cursor in the Photo Filter preset mode (or ACR white balance presets) field and use arrow keys to quickly toggle through different presets/modes to find the ideal mode.
I know that with Shift+ an Shift- one can toggle between blend modes (Layers). But these keyboard combinations do not work for Photo Filter and other pop-up/drop down menus.
I used to be able to preview a lot of filters (or other modes) in seconds to choose the optimal. Now I have to click this button and click again on each photo filter. This is lengthening enormous the process.
On my Mac, I can certainly click in the menu and use the arrow key to go up and down but what that does not do is apply the blend mode, unless I also press Return. But pressing Return kicks you out of the menu so you have to start the click/arrow/Enter cycle again, which is a long way just to try the next blend mode.
It is very annoying. Please help! Thank you very much!

ACR 6.1RC Presets

Similar Messages

Maybe you are looking for