Inexplicable Auto-Adjustments on Import

I've looked through my settings and Google, and it appears that my LR installation is set up as it should be, however, when I import an image, it applies some kind of auto-mix to the images. The images will show up for a split second as they should while loading, then when the standard size preview has been generated, it will shift to some kind of default adjustments.
I don't have any preferences that I'm aware of set to do this, so I'm not sure what's going on. Here's an example. This is how it's supposed to look:
Then when it's done loading, this is how it looks:
I know, we don't all have the same calibration, but you should be able to see some differences. The contrast is higher on the second image, the blue is a little less teal, and there even appears to be some added vignetting.
Sometimes it's not a problem, since almost everything gets some minor adjustments anyway. But in some situations, it will affect things dramatically, for example, sometimes a properly exposed image will all of a sudden become very under-exposed, presumably because it's detecting that's over-exposed, when it's not.
Can anyone give me a clear answer on why this is happening, and ideally how to fix it?

http://forums.adobe.com/thread/358016?tstart=0

Similar Messages

Auto levels on import preset

I tried a search to see how you can get AP3 to do an "auto levels" adjustment during import, but I am not sure how to do it. If I do an "auto" adjust on an image and then create a preset, does AP3 apply the levels based on that particular file used, or will it actually look at each file individually and make the correct adjustment for each file during the import? Or is there a different way to correctly apply auto levels during import?
Thanks in advance.

this is fairly easy. the only thing you have to do is create an adjustment preset to do just that.
steps:
1-click on an image and go to the Adjustments tab
2-apply auto-levels on that image (and nothing else)
3-in the Presets drop box, choose Save as Preset (Aperture is intelligent enough to remember you've applied the Auto-levels)
4-in the preset management box, give it some name
5-on following imports, just apply this preset to your images on import and voilà.
j

Camera Raw 3.7 no longer supports per slider auto adjustments

Nobody else resent this "improvement"?
Now the only way to have the image properly scaled (while not affecting everyting else by the automatic guesswork) is to have the settings in custom non-automatic default and then one has to use the Exposure slider manually with the aid of the Highlights Clipping Warning, for each and every image.
Compared to the 3.6 where this is fully automatic and works very very well.

sorry for the confusion, it is indeed shift double click and double click to change from auto to standard.
If you use your own created standard setting both automatic and standard on top of the sliders are blue colored and visible. Using auto does gray out the auto setting and using standard does gray out this option which is logical because you have to click on the highlighted option to change.
So this is the way to see in what mode you are.
underneath a copy from the original post that came with the release,
regards
Omke
Topic
Camera Raw 3.7 Now Available
Tom Hogarty - 09:36pm Feb 18, 2007 Pacific
The Photoshop Camera Raw 3.7 plug-in is now available on adobe.com.
http://www.adobe.com/products/photoshop/cameraraw.html
Important Notes Regarding Camera Raw 3.7
There are several significant changes to Camera Raw 3.7 in how it handles auto and default settings:
Applying auto settings by default is no longer controlled on a model by model basis, but instead there is a single global preference checkbox Apply auto tone adjustments that controls this adjustment for all camera models at once.
Camera Raw 3.7 no longer supports per slider auto adjustments. One Auto control at the top of the panel now sets the Exposure, Shadows, Brightness, and Contrast sliders to their auto values. The Default control at the top of the panel sets these same four sliders to their default values. The keyboard shortcut for the Auto control is CMD/CTRL-U.
The keyboard shortcut for the Default control is CMD/CTRL-R.
Double clicking on a slider to set that single slider to its default value.
Shift double clicking on a slider to set that single slider to its auto value.
Previously, default image settings could only be applied per camera model. Camera Raw 3.7 can now:
-Apply default image settings specific to a camera serial number
-Apply default image settings specific to a camera ISO setting
The additional criteria are located in the Camera Raw preferences.
The default settings (including the global auto preference) are now shared with the DNG Converter.
The DNG Converter requires OS X 10.3.9 as a minimum operating system.

LR makes auto adjustments even when prefs are set not to

Using LR 5.5 on a Mac with Mavericks.
I import photos in LR then when I begin to look through them, one by one, in Library Module Loupe view, I can see the photo the way I took it (low contrast and saturation) for a second while it's "loading" then LR seems to make an adjustment. I looks like it adds a lot of contrast. I believe I have all of the auto adjustments turned off in preferences.
I took a video of it below. The change happens quickly.
http://nickdantonio.com/wp-content/uploads/2014/06/IMG_0173.mov
What is happening here and how to do fix it?
Thanks.

After viewing the movie, what I saw is what I would expect to see with LR set to the defaults.
After the image is imported, the initial view will use the JPG preview contained in the raw file, this JPG preview will have all your camera settings baked into it.. After the raw file is processed, all your camera settings are ignored and the default LR profile is applied to it. The default LR profile is the "Adobe Standard" profile, which does up the contrast and saturation.
To prevent similar discrepancies, I created a user preset that applies the "camera neutral" profile and assigned that preset as the "apply during import".

How do I turn off ALL auto adjustments in Camera Raw?

SUMMARY:
I am simply trying to open my images in Camera Raw (version 8.6.0.254) via Bridge CC exactly how they were shot in camera, with no auto adjustments whatsoever. I already have all of the auto boxes unchecked in the Camera Raw Preferences dialogue box under Default Image Settings. I am shooting raw on a Sony A7r.
MORE INFO:
This discussion is not being created without prior research on how to solve it. Hopefully there is a simple solution that I have overlooked and missed when looking for it.
I shoot my raw images flat on purpose. The in-camera saturation is turned down, along with a lot of the other picture profile settings in the camera.
I use Bridge CC to sort though my images and make selects. In Bridge, I have "Prefer Embedded" selected for my thumbnails in order to stop the auto processing to happen to the thumbnails there.
The problem is, as soon as I open my raw images in Camera Raw from Bridge, the auto adjustments kick in and the saturation and exposure are automatically adjusted. I can't figure out how to stop Camera Raw from making adjustments to my raw images. As stated above, all of the auto check boxes are unchecked in the Camera Raw Preferences.
When the "Command U" shortcut is pressed after an image is opened, it applies the auto settings, making it clear the Camera Raw thinks that nothing has been applied yet. Toggling between "Camera Raw Defaults" and "Image Settings" in the side drop down menu does nothing either.
Below are two screen shots. One of how the thumbnail looks in Bridge, desaturated and flat. The other is how the image opens in Camera Raw with no user adjustments what so ever. You can see how the saturation and exposure have been adjusted:
Bridge Preview - this is how the image was shot in camera.
Camera Raw - Straight after opening the file with no user adjustments. You can clearly see the dramatic auto adjustments, but all of the sliders are set to default.
I would love to get some help with this, so I can see and work on my images as they were shot. Im really hoping it is a stupid oversight on my part with an easy fix. Thanks for the help.

As was already said: the camera's interpretation of the raw data is just one interpretation, and not the same as Adobe's. Don't confuse it with "exactly how they were shot", as this doesn't apply when shooting Raw. Granted it IS the manufacturer's interpretation, but you wouldn't be shooting Raw and using Adobe Camera Raw if you thought the manufacturer was always right.
One thing nobody has mentioned is Adobe's "baseline exposure" compensation factor. Camera Raw adjusts the default preview exposure by a factor of EV based on their measurements of the camera sensor. My present camera is boosted by 0.35EV and my last camera by 0.5EV. There is a way of determining this using EXIFTOOL, but I can't remember how to do it offhand. For the last few years, I have adjusted my own Camera Raw defaults by reversing this compensation, so it more closely matches the exposure I was expecting.
EDIT: here's the procedure, if you're interested. Re: Baseline Exposure

BPC Carry foward of auto adjustments (Consol)

Hi,
We are using BPC periodic model for Consolidation. Our carry forward tasks, basically carries forward the closing balance for balance shet items from the prior period to the current period. It does not carry forward any values that have datasource type "A", which is fine. I have read the consolidation configuration notes, and its states that the datasource type "A" will be carried forward when running the consolidation (auto adjustment task), it will adjust carry forward balances for prior period auto adjustments (datasource type "A")
This does not seem to be automatically happened, has anyone got any ideas? Thanks

Dear All:
I have a similar question about this automatical funcion in copying A-Type dadasource. I did see such copying of datasource with A-type in BPC 5.0 MS version, however, I had no idea why BPC does this copy automatically? Can I disable this and just copy datasource with type I and M into next year instead? Or how to explain this in terms of accounting consolidasion? Can anyone share your experience in it?Thanks in advance.
Fred Cheng

Develop Mode Auto Adjustments

Hello,
When I am loading RAW files in to LR, in the Develop mode they start off as a pretty flat image (as I shot them) but then LR slowly adjusts each photos as it loads which looks like it is bumping the saturation and contrast then lowering the exposure.
What are these auto adjustments and how can I turn them off? I would rather edit my images as shot in camera, not after LR makes its own adjustments without my help.

Ryan.Polei wrote:
This doesn't happen in Bridge
The difference: Lightroom is a raw editor, Bridge is not.
So, Bridge shows you what the camera did (if unedited raw file) instead of what it would look like with Lightroom edits. And Lightroom edits have to start somewhere, and that somewhere CAN'T be the same as the jpeg, or the same as another raw editing software (they use different settings, different software, different starting point..).
Don't get me wrong: I think Adobe should have better support for displaying embedded preview / sidecar jpegs (which is what Bridge does), and have an option to detect in camera profile setting and select a "nearest fit" Lightroom profile, but none of that will change the basic "deal" - different software, different settings, different starting point...
Note: this may seem odd to you now, but it's how all proprietary raw editors work, i.e. all those except the camera manufacturer's own (or those using the camera manufacturer's raw-rendering toolkit under the hood, instead of it's own), which emulates in-camera settings pretty-much exactly - no others can interpret a custom picture style, granted some may try to start with a somewhat closer look.
To review: all proprietary raw software does the same thing: interpret raw data according to invented algorithms and settings. That's what Lightroom software does, and that's what Capture NX2 does (and that's what your camera firmware does to come up with the jpegs), but they are different software, with different algorithms, which use different settings.
So your choices are:
* shoot jpeg
* use the camera manufacturer's software to process, or
* wean yourself from custom camera styles and learn to setup Lightroom processing instead.
PS - I recommend the later. Actually, you can use a plugin to somewhat translate camera settings to Lightroom settings, but I don't recommend doing it, because it tends to prolong your dependency on camera settings, rather than wean.
My advice? - Learn to use Lightroom (and get it set up optimally for your druthers) for post-production, and forget about camera settings whilst shooting (except for exposure and focusing etc., of course). Then, delete all the custom profiles you created in your camera, for therapeutic purposes .
Rob

Cannot disable Auto Tone on import of PSD files - ruins edits !!

Hi - I am a LR 5 expert and we have an issue with the latest release that I need to overcome or it is unusable.    Please direct this to an expert level support person as I have already networked around and have not been able to resolve this issue.    The issue is consistent with other users as well - we have tried this on several computers and the result is the same.     It is possible that is pilot error but I doubt it - we have disabled apply auto tone everywhere we could find it...
I believe this is a serious bug in the way LR handles files on import - and I am also hoping there is an immediate work-around as the issue has TRIPLED our workflow time.
Example #1   -   Edit DNG - Export as PSD with "add to catalog" checked - LR exports the file and then imports the PSD,   but in doing so applies auto tone and destroys all the edits. The re-imported images are too bright and too contrasty.       Auto tone on import IS disabled.
We tried to work around the issue by trying to edit outside LR and re-importing but that does not work either -SAME RESULT !
Example #2 -   Edit DNG files, export to PSD, do not check "add to catalog" - make the edits needed in Photoshop, then import using "add" and LR applies Auto Tone once again destroying all edits.      You can actually watch the auto tone being applied to the thumbs as it imports them. - they get brighter.
In all cases the edited images end up too bright and too contrasty and are otherwise unusable.        Our workaround is to export to PSD, edit in photoshop, then use Photoshop's   scripts to produce the final images and leave the PSD files out of the catalog - this has added a TON of time to our workflow and has corrupted our file management - UNACCEPTABLE !!
We have also tried reading the external meta data option - same result - bright files.
Please let us know how we completely disable auto tone on import and fix this issue it is a deal breaker for using this version.   We are using LR 5.6
Thanks, Mark
Head Janitor, 6IXGUN.COM

Looks like we solved our own problem -   either edit or delete the preferences files and restart lightroom. If you delete it, it will of course wipe our your template settings, etc but that was far less of a hassle than not being able to use LR with PSD / exporting. We were able to make a simple edit and it was fixed.   Also make sure you have unchecked "apply auto tone" in the >preferences>presets   dialog box - we did not have it checked but it WAS enabled in the plist file.       I would definitely consider this a bug - the issue was not present in the last version of LR, it was introduced upon installing 5.6.

US Eliminations vs Auto Adjustments

Hello Folks,
I have two set of questions relating Eliminations and Please share your valuble inputs in this regards.
Q1> How to decide whether to go for US Eliminations or Auto Adjustments Business Rules? I
My thoughts:
was under impression that US Eliminations need a seperate Elimination Entites. And also it can be done only for Entities having common parent (nothing but with in a Group) But for Auto Adjustments Elimination Entires will be captured under seperate Data Sources. And it can support Inter Group Eliminations also.
Your inputs here:
Q2>How Eliminated/Adjusted amounts of an Account will be distributed into entities much lower than Company Code when we do eliminations at Company Code level? How to capture Eliminations at lower level than Company Code(Ex, Profit center, Cost center, WBS element, Internal Order)
My thoughts:
Eliminated Values when we performed Auto Adjustments gets captured in seperate Data Source and seperate Elimination Accounts we create exclusively in BPC.(Ex IC_DIFF, IC_REC, IC_SAL, IC_REV..)
Eliminated Amounts by Account, by Company Code cannot be distributed to further lower level entities like Cost Center, WBS Element, Internal Order. Eliminated Ammount will remain in Elimination Account in that Co Code as an aggregated value with all other Loew Enties as None_LLEntity)
Ex: In an Entity ABC, there is an account 123 is holding an amount of $ 1000. This value is coming out of combnations of Account, Company Code, Cost Center. After we performed US eliminations or Auto Adjustments $ 100 got Adjusted/Eliminated and resulted with $ 900 as Consolidated Value.
If we report it by Account, Company Code,Cost Center I guess we see Eliminated value something like this.
Account, Co Code, Co Ctr, Data Src, Amount
123, ABC, CC1, INPUT_DS = 1000
IC_DIFF, ABC, CC_None, ELIM_DS = (100)
Your Inputs:??
Please correct me if Iam wrong. Highly appreciates your inputs of these 2 set of questions.
Thanks,
BIBPC

Q1: US Elimination only works when entity hierarchy is static ( which means the hierarchy does not change as time goes by), and the share of parent entity over child entity is also static (100% always). Auto Adjustment is much more powerful (supposed) to do legal consolidation.
Q2: Do you mean the Cost Center is a 'Inter Company'? Btw, It's more clear to get the answer by hands on

How to initiate auto search and import

When I first started iTunes, it initiated a auto search and import of files to my library, but it got interrupted by a software update and thus terminated the import process. How do I re-initiate that auto import?
Thank you.

Choose File > Library > Consolidate Library.

LR5 and Photoshop CC-weird auto adjustments on return to LR

This pertains to the use of LR5 and Photoshop CC.
. This problem that’s plagued me since LR4 has been when I’m working with plug-ins via Photoshop (now in PSCC). The transfer from LR to PS is no problem. It’s when I save the file and bring it back into LR that things change and the image barely resembles what the image looked like when saved in PS. Back in LR the exposure gets a wild increase in exposure as well as adjustments in contrast, highlight/shadow and clipping. The Basic adjustment panel is the only panel effected. So, like Nasim, I have to go back and change everything. A funny thing about this is that the history panel does not reflect these changes, so I can’t just step back in history. Drives me absolutely NUTS!

photowhiz wrote:
I would rather not chang the auto-tone adjustment pref as it IS usable on new (original from camera) imported files. And secondly, there isn't (IMHO) any reason why I should expect such wild swings in exposure executed by the auto-adjustment, especially when this does not occur when files are originally imported - it only happens when the PS edited file is returned to LR. The plug-in I use via PS is Niks Color Efex Pro 4. While I can just as easily go directly from LR5 to my plug-in I go through PS so I can flatten the image and thereby reduce file size. This is especially important when the original file is 35+MB.
I agree that it would be better if LR did not apply auto-tone when re-importing images from Ps editing - even if configured to do so at original import time - in fact, I am surprised that this is happening.
One workaround which would give you control over when auto-tone happens and when it does not, would be to remove it from your overall LR prefs, but include it into a Develop preset which you can then call at import time (as part of your Import settings). Perhaps you are already using such a preset, and can add this option to that. Then the only situation where auto-tone will happen, is where you explicitly ask for it to happen - the selection of this preset at import time, along with the remainder of the import options, can be automated by including it in a named import preset. Perhaps have differing import presets, for different import scenarios, e.g. as to whether you want autotone or not. There's some flexibility there.
regards, RP

Auto-organization of import statements broken

Anyone else having this problem?
it happens pretty regularly, when I use auto-complete on a new object type, then flexbuilder goes and totally screws up all my imports, causing me to have to go through and ctrl-space (alt+"/" ) each one.
Also, it seems to never put in the correct import statement for an MXML component that I refer to in my AS block. I finally just used the fully qualified name because I was sick of FlashBuilder removint the import after I added it 5 times.

Known bug http://bugs.adobe.com/jira/browse/FB-23179 or one of the related bugs.
Jason San Jose
Quality Engineer, Flash Builder

Originals auto modified on import from camera

I discovered that iPhoto has modified a lot of my pictures when importing from camera. Not only vertical photos (bacause of auto rotate I believe) but also landscape. Mostly photos with high contrast or too dark/too light photos are modified and enhanced. This makes me angry! I usually export photos to modify in PS and this way I do not work with the original! I suppose the modified version is not lossless.
I can't find out how to turn off this auto modifying.
Any suggestions?

hansik:
Are you aware that you can have iPhoto use PS as the default editor? The edited version is saved in the Modified folder and the originals never get touched. The only caveat is that you do not change the extension or file name. If you need to do either then you do a Save As to the desktop and then import as a new file.
Are you concerned about the thumbnail size increase due to HD space issues? There is a way to have your source files on an external HD and only have aliases, thumbnails and the modified files on your PB. My 27G (15,600+ files) of image files on my second HD are represented by a 1.75 G iPhoto library on my boot drive. When the external drive is not connected the library is still operational on a limited basis: you can view thumbnails, create, delete and move album folders, add comments and, with some hassle but doable, add keywords. You can't edit, work with books, slideshow, etc. or anything that requires moving thumbnails. Once the HD is remounted the library is fully functional again. Great for laptops with limited space.

Color Adjustments while importing from Epson P5000

Hello, I recently upgraded to Aperture 1.5.2. Since doing so, when I import my images from my Epson P5000 portable external hard drive I am having a problem. As soon as all the images are imported in Aperture, one by one each image undergoes automatic adjustments. They become over saturated, develope a color cast (or perhaps a temperature adjustment). This is not a setting in my camera nor do the images look this way on the display on my Epson. Can anyone explain how to turn these adjustments off? Thanks, Phil

WALTER-MILANO-ITALY wrote:
May I ask you your help ?
I use RAW+Jpg in different cameras and I import Both Raw as Master, leaving the originals on an external HD, that is referenced system.
I am missing something ?? For instance if I take a BW with my EP2 I get a RAW colored and a BW jpeg into Aperture only if I import separate masters.
If you use your normal 'Both RAW as Master' option, can you Control+Click (right-click)and use the set JPEG to Master option to switch to the Black & White version displayed?
Probably I am only wasting time shoting BW in camera because you can do it later from RAW with aperture...
If the JPEG captured what you wanted to see and will work for your purpose, then it is not a waste of time - IMHO.
I shoot RAW+JPEG also and import 'Both JPEG as Master' because most of the time the JPEG works for what I want.
Note - RWBoyer has a great site with a lot of information about Aperture here:
http://photo.rwboyer.com/

Picture auto-rotation on import into LR3 ?

Hello !
When importing directly from a card into LR3, vertical pictures are displayed correctly in the library, but JPEGs are not rotated in the file system.
That's not too much of an issue if you edit with CS5, or export the pictures. In those cases they are handled appropriately.
However if you edit with something else (in my case Topaz's filters via Topaz Fusion Express), the pictures aren't rotated appropriately.
Context: W7x64, LR3, Cameras (EOS5D, G10) set to Auto-rotate "on"
Any idea about how to fix this?
Many thanks!
Jean-Paul

Ok - bear with me...
Workflow1: import pictures from camera, with Canon EOS Utility or Canon CameraWindow. Both of them activate ZoomBrowser.
Result: jpegs and raws stored in the file system.
View with Windows explorer, all thumbnails have correct orientation.
Edit with CS5 orientation is correct.
Workflow2: import pictures from card, with Adobe LR3.
Result: jpegs and raws stored in file system.
View with Windows explorer, vertical photos are not displayed correctly (not rotated).
View in LR3 library, orientation is correct.
Edit in CS5 (called from LR3) orientation is correct.
Edit in Topaz Fusion Express (called from LR3) orientation is not correct.
I moved from 1 to 2 because of Canon's inability to provide a driver for W7x64, and, more importantly, because of the workflow improvement with LR3. The incorrect orientation is of course not a showstopper, but an annoyance...
Thanks
Jean-Paul

Inexplicable Auto-Adjustments on Import

Similar Messages

Maybe you are looking for