Odd Camera Profile / Undo Bug in 2.3 RC

I downloaded the LR 2.3RC tonight and although it seems to be running faster, I've noticed a strange bug that I've never noticed before (or that wasn't there before.
When using develop presets that change the camera profile (for example Matt Kloskowski's 300 Look) the preset will be applied and then after that the camera profile is changed as a separate step in the History palette (however I have only clicked on the preset and haven't changed the camera profile).
When clicking undo the overlay that tells me what step I am undoing says that it is "Undo Camera Profile: ACR 4.4" - however this step either (1) gets undone and immediately re-applied, or (2) never gets undone. This problem makes it impossible (without using the History palette) to revert to the step before - and it kind of makes it difficult to apply several presets to see which works best as I have to scroll to the History palette to undo it and apply another.
This bug only exhibits itself when using presets which change the camera profile.
Anyone else seeing this?
Any work arounds (other than reverting to 2.2)?
Thanks,
Chris

Hey Chris,
Yes I can reproduce this same exact problem on my Macbook Pro (Feb. 2008) with 4GB RAM and 10.5.6 with Lightroom 2.3RC
I tried this on Lightroom 2.2 and I can say that this problem does not happen. This is a Lightroom 2.3RC bug.
Is there a place where we are suppose to report RC bugs or is this post enough? Thoughts Adobe?

Similar Messages

D810 RAW conversion in LR 5.6 shows posterization at certain camera profiles: Camera Standard, vivid, monochrome that it does not show with identical photos from a D800. Is this bug already known?

Never had this problem seen before in all my years of LR use. I use a test-chart with a continuous gray bar (from dark to light). Normally use Camera Standard profile to develop all my D800 RAW files with no problem so far. Got a D810 to test this week and did some tests using the same target. Suddenly there are some ugly posterization effects in the gray bar to be seen that can only be eliminated with heavy color-noise reduction or by switching to any other profile but Camera standard, Camera Vivid, Camera monochome.
The following 100% crop shows the effect from a D810:
And this is the same crop from a D800-shot:

OK, after posting there was the right suggestion of other forum threads that took care of the issue:
Nikon D810 & Lightroom 5.6 posterization issue with Camera Profiles
So this thread can be closed.

Camera profiles bug

Some camera profiles not appear in the version 4.4., and ACR 7.4
folder of camera profiles
I see this in LR 4.4 and ACR 7.4
And this whith LR5
I had made me with ColorChecker Passport. Anyone know where it is due. You can fix-it?
If I open one camer profile made in 4.4 with "texedit" I see this:
IIRC ∆
b!∆
and if I open all the camera profile made with 4.3 i look this:
IIRC ∆ b!∆
What has changed in the plugin developer?

There was a change to the behavior of LR4.4 and ACR 7.4 to look for camera profiles only in the user level location not the root level. What OS are you on?

New camera profile not "appearing" in ACR, but does in Lightroom

I recently created a camera profile for a Nikon D200, using an X-Rite Colorchecker chart photo and the Chart feature in the DNG Editor. I exported the camera profile. When I go to the Calibration tab in ACR 5.5, the new profile does not appear in the drop down list with the other camera profiles. However, when I go to the Develop module in Lightroom 2.5, the new profile does appear in the drop down list there.
I am running Windows 7. Snooping around my root drive I find that if I look within the Users\User Name\AppData\Roaming\Adobe\CameraRaw\CameraProfiles directory (referenced in the Fraser and Schewe CS4 Camera Raw book as the Vista location for the profiles) I can find no camera profiles and when I place the new profile there it still does not appear in ACR. When I look in ProgramData\Adobe\CameraRaw\CameraProfiles\Camera\Nikon D200 directory I can see the regular set of camera profiles for the camera, as well as the one I created, but as I previously stated, the newly created profile does not appear in the ACR list.
A side note - I did some experimentation with camera profile names. I added "XX" to the end of the Nikon Vivid profile name (not the extension), and then that profile no longer appears in the ACR list of profiles. I removed the extra letters and then the profile reappears in the ACR list of profiles. Seemed odd behavior to me. I also noticed that the profile I created with DNG Editor is noticeably smaller than the others provided by Adobe (28K compared to 110k).
Hope someone has a suggestion for me.

Your reminder about both Photoshop (main) and Bridge needing to be shut down for changes to take effect reminded me that I had Bridge set to "auto-start at log-in". So I checked and it was still running (shown with the other hidden icons). When I "shut it down" from the UI I had thought it was fully terminated. So I completely shut Bridge down, restarted, and the new profile now appears.
Thanks for the reminder/pointer in the right direction.

ACR 5.7 can see camera profiles in Bridge CS4 but not in Lightroom 2.7

When utilizing ACR5.7 through Bridge CS4 - the cameral profiles are easily applied for my .NEF files (Nikon D300) but when I am in Lightroom 2.7 the camera profiles are not available unless I convert the nef to DNG. I have tried to search the web and these forums but I am unable to locate the answer to my problem:
Why can't I see the camera profiles in Lightroom for my nef files when I can see them through Bridge.. (both running ACR 5.7)
Windows XP xp3
Lightroom 2.7
Bridge CS4
ACR 5.7
Nikon D300 profiles
Thanks for the help.
NGG

For those who might be reading this and having "odd" problems .. my solution was to delete my preferences file.
http://lightroomers.com/replacing-the-lightroom-preference-file/745/
This solved several odd issues I was seeing in my lightroom including the camera profiles..

Lightroom 4.3 Update and Camera Profiles.

Hello there!
First let me start by mentioning that im running Lightroom on a Mac OS X (10.8.2).
I was running v4.2 for a while until the v4.3 update came out about a week and a half ago.
I updated to v4.3 and everything was working fine until I noticed something today.
Im having problems with Camera Profiles. I do run the latest 2012 process.
The problem to be exact is when I open catalogs that were made with v4.2
I scroll down to Camera Profiles and here is what i get.
I have presets that automatically correspond to the "film" profiles below.
But ever since the upgrade it automatically goes to ACR 4.6 instead of the "film" profile.
I know for a fact that with v4.2 I only had these profiles:
Adobe Standard
Camera Landscape
Camera Neutral
Camera Portrait
Camera Standard
Camera Vivid
with the addition of the "film" profiles.
After updating, thats what I get when opening v4.2 catalogs.
Heres the weird part.
When i create a v4.3 catalog, all of those Camera Profiles disappear.
leaving only these:
Adobe Standard
Camera Landscape
Camera Neutral
Camera Portrait
Camera Standard
Camera Vivid
and nothing else.
When I looked at the Camera Profile folder, the ones I added are there but doesnt show up in Lightroom.
Mac HD > Library > Application Support > Adobe > CameraRaw > CameraProfiles
Is this a bug or is there a fix for this? Does v4.3 read Camera Profiles from another location?
If so please help!

I would suggest a two-step process:
1) The problem could be due to a corrupt Preference File. This file can go "funny" and is then responsible for all kinds of strange behavior of Lr. The remedy is replacing the Preference File.
Re-installing Lr, or upgrading Lr does not replace the Preference File since it is designed to stay intact during upgrades.
See here for where to find the Preference file for your OS: http://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroo m-4.html
See here for how to go about Replacing the Preference File: http://lightroomers.com/replacing-the-lightroom-preference-file/745/
2) If that does not help: Un-install Lr and delete the downloaded Lr 4.3 file. The file might have become damaged during download.
Then download it again and install.

Current Lightroom / Camera Raw Camera Profile for Sony ILCE-6000 inaccurate: green cast in shadows! Capture one better! Please fix it!

Hi folks from Adobe!
Please take note that the current Lightroom / Adobe Camera Raw Camera Profile for the Sony ILCE-6000 is very inaccurate: There is a serious green cast in the shadows!
Capture One Express for Sony (which is free by the way) renders a lot more correctly!
Please correct this, since I'd rather buy the coming LR6 because of keeping my established workflow instead of going the Capture One route.
A good example can be found in the dpreview forum "LR5 A6K shadow pulling, a mess! Adobe LR is broken? "
Or search for Philp Reeves 3 weeks with the Sony A6000 review "3 Wochen mit der a6000", where he compares it to the Sony A7, using both times Lightroom to push the shadows.
The Sony A7 is fine where earth looks like brown earth, the A6000 picture looks like grass instead.
Please fix this! This is a high volume camera frequently bought by enthusiast or as second body for FF photographers. That would be really great!

I am talking about the two raw files linked in the very last post of page 6 of the Reeves comparison thread, not JPGs or screenshots of unknown manipulation. In LR they both say f/11 and ISO 100 and have a similar tone, but one is shot at twice the shutter speed as the other. This side-by-side is using Adobe Factory Defaults for each image where the profile is Adobe Standard, the toning sliders are all 0, tone-curve linear, and the Sharpening and Color NR are 25:
However, when I look at the camera-embedded JPGs, side-by-side, the 1/80th image on the left is darker than the 1/40th image on the right, as expected given the reported shutter-speed difference:
And it is indeed the darker image that has more shadow problems, also as expected.
When I do manipulate the darker (a6000) raw file in LR, I do see that the shadows are greenish when brightened unlike most other cameras which usually show magenta, which is the combination of the blue and red sensors showing more noise because there are half-as-many photosites as compared to the green, so I am seeing what people are complaining about and would expect shadow noise to be purple not green, I'm more concerned that these two example raws aren't actually comparable due to apparent differences in exposure. It is also odd that the lens listed in LR is different than the lens listed in the filename, so either someone has mistakenly or deliberately renamed the file wrong or someone or something has changed the EXIF parameters that LR is reporting to be the same when they're really not.

DNG Converter 5.2 and Camera Profiles

Hi!
I tried to search for an answer but did not find any.
Question - how and when DNG Converter will use Camera Profiles?
How do I specify which profile to use?
I assume it can use them - version 5.2 comes bundled with them...
Тhanks for the help!
P.S. Since new version has installer, I'd suggest to create uninstaller too.

>This somehow implies that DNG Converter reads settings from installed Lightroom. I'm not sure that this is the case - DNG Converter seems to be completely independent product.
Yes, it does...for the camera model, if you have modified the Camera Raw Default in either Lightroom or Camera Raw then DNG Converter will use the user specified default. If there is no user set default, then of course will use the regular Camera Raw Defaultwhich in the case of 5.2 is now Adobe Standard. (I can't remember what version of DNG Converter started reading the CR prefs).
>If I give DNG file to someone, who uses DNG-compatible program (other than Adobe's), do I have to give him all profiles as well?
If you are using a "custom" profile other than Adobe Standard, the behavior is to embed that profile in the DNG so it is self describing. The only complicating factor is what version of Camera Raw/Lightroom the recipient is using. If they are using a version prior to Lightroom 2 or Camera Raw 4.5, then those older versions ignore the embedded profiles and will use the earlier simple profiles that have been used since DNG/ACR was introduced.
As for checking on updating the DNG Profiles in the future, DNG Converter, as it's rev'ed, will include any new profiles that come out and will update them for any already installed and add any new profiles available for a given camera. The odds of updating existing DNG Profiles is not largethat's what the 2 beta rounds was for, to shake them out. But it's possible. It's more likely that profiles for new cameras will be added.

Camera profiles and Highlight Recovery: color shifts

I often see significant hue shifts and loss of saturation when using the Recovery slider in conjunction with the new dng camera profiles. I don't remember to ever have this 'problem' with legacy ACR profiles. In the sample below, you can see just that:
Sample: http://farm4.static.flickr.com/3224/2918603614_7a562db832_o.png
This becomes a bit of a problem, as recovering highlights now brings color shifts as a side-effect and you have to go fiddling with color controls.
Often, the new, 'shifted' colors are even more pleasing than the 'unshifted' (i.e. recovery set to zero), but this is a psychological and a workflow problem too. It is just not nice to know that controls are interdependent and have side-effects.
Is it a bug or a fact of life? What's so different about the old a new profiles, that cause this difference in recovery effect?
The DNG to play: http://www.yousendit.com/download/bVlBblFOR0Y3N0JFQlE9PQ

Eric, thanks a lot for the explanation and technical details.
Knowing this helps me a bit, as it confirms my observations. What is not clear, is how these shifts will/should (or would they?) be addressed?
I mean Recovery was a perfect control until now. it just did what is should, reliably and consistently. Now we have the side-effect of color shifts.
a) Will Adobe adjust the algorithm to fit the new profile system? A bad thing, because it will not assure backward compatibility.
b) Will Adobe add a new control? Worse, because it adds unnecessary complexity.
c) Will/could the profiles be modified in a way as these color shift don't happen. As I understand from your previous post, this doesn't seem possible.
d) Will it just be left as is and I'll have to live with the color shifts? Now it seems it's the most likely option. Sad, because Recovery used to be so powerful, and now its power is somewhat compromised.

Strong colour shift when reselecting Adobe Standard camera profile

I'm having this curious problem with Nikon V1 NEFs (raw files) in Lightroom 4 beta.
In the develop module, Adobe Standard is selected as the default camera profile. If I switch to one of the other profiles (for the V1, the options are Camera Landscape, Neutral, Portrait, Standard, and Vivid) and then switch back to Adobe Standard, I get a strong color shift in the blues, which move towards teal. It looks like a white balance shift, but the white balance settings themselves don't change.
I've attached three screenshots, the first showing an untouched file with Adobe Standard selected as the default profile in the develop module, then with the Camera Vivid profile selected, and then with Adobe Standard reselected. Besides changing the profile, there are no edits on this file: all I've done is import it, put it in a collection, switch to the develop module, select the Camera Vivid profile and then reselect Adobe Standard.
The color shift happens regardless of which camera profile I pick before reslecting Adobe Standard. Interestingly, while the colors are off in the develop module, they're correct in the library module. Switching back and forth between library and develop doesn't fix the problem -- as long as Adobe Standard has been reselected in develop, the colors are off in that module but correct in library. The only way I've found to clear the color shift is to click reset in develop. Select another camera profile, though, and then reselect Adobe Standard and the problem comes right back.

Yes. This is a bug that has been reported/fixed after the public beta build was made ready. Somehow it did not make it to the final public beta release note. The current workaround is to relaunch LR4 or
a) Copy Settings (check all except Calibration),
b) Reset,
c) Paste Settings.
This will invalidate some internal memory cache that went stale.
-Simon

Thinking behind 'beta' as in Camera Profiles

It would be interesting to hear some guidance on the Beta part of the new Camera Profiles title. Particularly as there is now word of a Beta 2.
It is hardly a scientific survey, but from what I have seen on this and the ACR forum, I would have said that since their introduction there has been nary a word said against them. And certainly little in the way of suggested improvements. The response from users appears to be wholly positive. But then again there has never been a forum dedicated to feedback.
Are there folk in the background providing constructive feedback which will be implemented into improvements to those that already exist? And will those improvements be in Beta 2? Or will this retain the existing profiles and only add additional ones for newly introduced cameras? And if the former, will there be further improvements added to further Beta numbers; or is the plan at some stage to finalise the existing profiles as a firm release?
There are after all, I would surmise, many thousands of images already treated to the existing excellent profiles. It would be great to know a little of what the future holds.

Hi everyone,
Our basic plan at this time is to release a "beta 2" set of profiles which will include support for new cameras well as fix some known issues with the existing ones. There will also be a "beta 2" of the DNG Profile Editor, which is essentially a bug fix update.
As with the beta 1 profiles, there will be an installer so you don't have to worry about where to stick the new profiles. The installer won't delete or replace the existing beta 1 profiles, nor will it overwrite any custom profiles you may have built using DNG Profile Editor. So you don't have to worry about the color rendering for existing images (which use the 'beta 1' profiles) changing their appearance behind your back.
Both are free and will be released to the public very soon. See Thomas's notes in his description of Camera Raw updates in a recent thread in the Camera Raw forum if you want a closer guess on what "soon" means.
There are more details, but I think this is enough for now. Ultimately I will attempt to update the DNG Profiles FAQ with more info, but I haven't yet figured out how to squeeze 25 hours into a day!
Eric

Two hours of futility...where are the camera profiles???

I'm recently upgraded to LR 4.3 RC1 and Photoshop CS6 on my Mac OS10.6. I've read quite a few posts in this forum from people with the same problem. Only Adobe Standard shows up in the camera calibration panel. My Nikon camera is supported, so that's not the issue. I've got CR 7.3, so that's not the issue. Right clicking on the Lightroom appliaction and drilling down through "Show package contents" I see that in Camera Profiles my camera is NOT listed. That seems odd. I tried reloading LR, no help. Reloaded Camera Raw, no help. This seems to be a common problem. It sure would be nice if Adobe would post a relevant help page!

Hi,
I am not sure about Nikon as I only use Canon but for me I have access to the following Camera Profiles in the drop- down list for the 2012 Process:
Adobe Standard;
Camera Faithful
Camera Landscape
Camera Neutral
Camera Protrait, and
Camera Standard
These are available for both the 5D Mk II and the 7D.
I find that for JPG's (e.g I had a 450D) it usually shows the profile as "Embedded"
If you are using Windows 7 the Camera Raw profiles are in C:\ProgramData\Adobe\CameraRaw\CameraProfiles\Camera
and for Lightroom C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3 RC\Resources\CameraProfiles (Adobe Standard and Camera subfolders)
Cheers, Don

FURIOUS! Warning: Undo Bug and Auto-Save Bug

So I'm pretty ticked off right now. I generally liked FCPX and its changes contrary to many others' opinions, but I just came across a bug that ultimately was worse than I thought.
During my editing process, at some point I was unable to undo changes. It was greyed out in the toolbar, and Command+Z wasn't working. It was annoying, but I didn't think much of it or bother to restart FCPX because I was in the zone and didn't want to stop. Eventually, I decided to restart FCPX to see if I could fix the bug with a lull in my edits. It closed out as normal.
When I re-opened FCPX, I found out that my project was at an EARLIER state. From what I can guess, when the undo bug happened. So, during that period of time, NOTHING was being saved. Since you CANNOT auto-save (I know you can duplicate a project, but Im not interested in that, I just want to save a copy manually), there is no way I can recover my edits. I lost about an hour or so worth of edits. Since FCPX doesn't support "versions" yet either, there is no way I can retrieve it.
I do not know if this is a bug due to 10.7, nor do I really care. I sent a bug report because this needs to get fixed. I consider you do the same but AT THE VERY LEAST, be mindful of this bug. If you suddenly can't start undoing, either STOP IMMEDIATELY or duplicate your project (maybe that would work). I'd hate to have someone else go through this problem too.
Sorry if this message is written poorly, like I said, I'm pretty ****** that this key function (Apple's ONLY way to save) failed.

Thanks guys for the tips. Unfortunately though stuck, I don't know if the finder trick will work. Remember, I never really had the file LOST, the changes were simply not writing to the actual .fcp file. So if I copied it in Finder, I think it would just copy the .fcp file which is currently not getting saved to anyway. Maybe duplicating the project in FCPX would work, but again I think that just takes the .fcp file and duplicates it. If it's not writing to it, then its a moot point. Oh well.
As with anything that frustrates anyone, I've cooled off haha, and doing the re-edits actually seemed to turn out easier and better then second time (you know, as theu naturally are I suppose haha). Obviously all sorts of problems happen with technology, its just a shame that its a bug that revolves around the ONLY save feature haha.
HOWEVER. I think I have replicated the problem, and MIGHT know the source of it. Or at least one. If someone wants to try this and confirm this? I'm running OSX 10.7 and FCPX 10.0 (obviously), however I encourage someone with 10.6 to try it too.
I noticed the "undo bug" (and thus the auto-save bug) happens when I took one of the "fader handles" (I don't know the actual name, but its the little marker-like icon found at the start and end of audio tracks, which when dragged, let you easily make a fade in or out. If you take a fader-handle, an drag it ALL the way BEYOND the length of the clip, it should get stuck. Youll notice you cant easily make a change to it again, and you can't undo it. I think this is what causes the problem, as I think this happened twice to me.
If this is it, I hope I can find a way to flag this for Apple so it can get fixed! At the very least we can be concious of it.

Custom DNG camera profiles only available for DNG files?

I developed a custom camera profile for my Sigma DP-1, using a colorchecker chart and the DNG profile editor.
I exported the DNG profile in the default location.
When I open Lightroom or ACR, the new profile is not available for X3F files, only DNG files. Is this normal???

Well, I've imported the original X3F file as well as the converted DNG file in Lightroom.
When I develop the DNG file, my custom profile appears in the list. When I click on the X3F file, embedded* is the only option.
It may have to do with an incomplete support of the X3F format. I have just repeated the exercise for my D300, and in this case the custom profile is available for NEF files.
Too bad since I'm happy with some of the Adobe camera profiles for the D300, but less so with the default look for Sigma DP-1 files.
I guess I should file a bug report...
* or "matrix" or whatever is the term in the english version, I have the french version which says "incorporé"

Custom camera profiles have stopped appearing in LR4.3/ACR 7.3

Really odd... I've been using custom profiles that I created using a ColourChecker Passport for sometime now. I just updated LR and ACR to the latest versions, and I've noticed that they are no longer selectable under the Camera Calibration tab - I just get the standard list of profiles for my camera (Nikon D7000).
I checked in the the relevant folder for LR and they weren't there, but they are in the ACR folder. I copied them across to the LR folder as well, but this has had no effect. In both cases, they're in the root-level folder for all profiles, so in LR's case, they're in C:Program Files/Adobe/Adobe Photoshop Lightroom 4.3/resources/CameraProfiles. This is where both the CCP and Adobe DNG Profile Editor have previoulsy placed them by default - I've never needed to place them in the actual camera model folder itself. Both applications have always found them there without issue.
Anyone else had this problem since upgrading, or have a solution?
M

OK- I am being a total dummy and need some help, please. I have put the KM7D and Sony A700 camera profiles in the above mentioned places
C:\Users\<yourusername>\AppData\Roaming\Adobe\CameraRaw\CameraProfiles
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3\Resources\CameraProfiles\Camera
AND am still not seeing them in either PSE11 or in LR4.3
I also installed CR 7.3 and DNG 4.3 per the Adobe forum.
So, I guess either it is not working or I am looking in the wrong place in PSE11 and LR to find them.
I assume in LR I should be in Develop and I look on the right side under Camera Calibration and try to pick it there somehow. If not- where? Where would I find this in PSE11?
I also tried a little experiment. I have my profiles in
C:\Users\SRose\AppData\Roaming\Adobe\CameraRaw\CameraProfiles\Sony DSLR-A700
and I renamed "Faithful" to Faithfula700" and then opened Lightroom and went to Camera Calibration and only Faithful was there- no Faithfula700. So, either LR truncates the file name or there is some internal name in the dcp files that LR uses or these profiles are not being recognized.
Sorry to be such a noob- everything else I know how to find and LR help was none at all.
Thanks
Steve

Odd Camera Profile / Undo Bug in 2.3 RC

Similar Messages

Maybe you are looking for