LR 3.6RC vs. LR 3.6 /w D700 Camera Profiles v4

I used the LR 3.6RC on Mac to develop a whole session using the Camera Profiles v4 that came with 3.6RC. The behaviour was a bit strange as the images got "lighter" the more you move the "Wiederherstellungs-Regler" (is that recovery control in the english version?) to the right. Anyhow, I developed some hundred images using LR3.6RC /w Camera Profiles v4 and after I installed the regular 3.6 now all images that have been done with 3.6RC are now too dark (and much too dark!). That means I have to go through all images to re-develop them?
You can see an example here: left is how it looks in (also devel here) 3.6RC1, right is how it looks now in 3.6

I'll have to add new findings to the above issue. When I switch to the library mode the image will be shown in the original development status as it has been done in LR3.6RC. You'll see it in the screendumps.
On the left side is the screendump from the library module. The right photo of the two is the one I'm talking about. The left one is a tiff version with all controls set to zero.
The screendump on the right site shows the same image in the development module of LR3.6. Same behaviour as in my first mail.
Any idea, help?

Similar Messages

Canon S100 RAW color issues

Hello, all. I created a thread with this similar issue a few months ago but never really got it resolved. Instead of reviving an old thread, I decided to just recreate it with updated information.
I have the new Canon S100 and I am having an issue with how the RAW files appear in Lightroom.
I import the photos into a Lightroom catalog and they all look fine within the importer window (which shows essentially what a JPEG would look like), but when I click on the photo in Library or Develop, once the photo finishes loading, the red saturation goes through the roof.
Any photo that already had a little bit of warmth to it exploded with red.
Whereas any photo taken in normal light gains a little more warmth and exposure.
Here are a couple examples of the JPEG preview (also how it looks in-camera) compared with what the RAW looks like once it's been loaded in Lightroom. (The above or left photo is the “normal” version, the bottom/2nd image is the RAW)
It’s sort of difficult to tell with some of the photos by looking at them side-by-side. I also have the individual photos if you want to A/B them to see the changes that are actually occurring.
There are no presets being applied upon import.
The only solution I've found is to convert them all into JPEGs using Canon's software (which does not alter the images as seen above), and edit them in Lightroom as JPEGs, but that completely eliminates the point of buying a camera that is capable of shooting in RAW.
I’ve been having this issue since the S100 first came out (when I purchased it) with Lightroom 3.6RC and was told that it would be fixed in Lightroom 3.6… which it wasn’t… nor was it fixed in Lightroom 4.
I decided to just go ahead and convert all my photos to JPEGs until I found a fix to this so I could at least have my photos (I had photos from my anniversary with my girlfriend in November that I couldn’t do anything with so I was sick of waiting).
I figured I’d wait till more people had the camera, expecting this issue to be more widespread… but now that a lot of people have the S100, I’ve looked around and found no other instances of this happening… so I’m worried it’s something on my end.
I have a 2008 13” MacBook Pro running OSX 10.7.3 and I have the latest version of Lightroom (4.0) and Camera Raw (7.0) installed. I’ve tried the photos in Photoshop CS5 and it does the same thing. When this first happened back in December I tried the photos in Aperture as well and it did the same thing.
The only software that seems to recognize the true color of the photos is Canon’s horrible “professional editing” software.
Thanks in advance.
-Patrick

I recently bought an S100 and encountered the same problem. With Camera Standard in Lightroom, Reds are too bright, greens are shifted towards yellow, and some yellows are shifted towards orange.
I have been using Lightroom since the beta, with different cameras from different manufacturers. The camera profiles for the S100 are the worst I have experienced by far. The profiles, particularly all of the profiles that start with "Camera," do not fit this camera. I believe somebody made a mistake. It could have been someone at Canon, it could have been someone at Adobe. I don't expect this mistake to be fixed, or even acknowledged.
Moving on, here is my workaround:
Start with the Powershot S110 Camera Standard profile.
Use dcpTool to decompile the profile.
Open the decompiled profile in a text editor.
At the top, change the name to S110 Standard.
At the bottom, set the baseline exposure offset to zero.
At the bottom, change the model restriction from S110 to S100
Use dcpTool to compile the modified profile. Give the resulting .dcp file a different name than the original.
Put the new .dcp file in the appropriate directory, open Lightroom and apply the S110 Standard profile to your S100 images.
dcpTool is here:
http://dcptool.sourceforge.net/Introduction.html
This hacked S110 profile gets rid of the blazing reds. It does have some problems with yellows and greens. I solve this in Lightroom by using +20 in Camera Calibration: Green Primary: Hue. I haven't had my camera very long, and I may end up making other adjustments in Lightroom. But using the Powershot S110 Camera Standard profile seems like the best place to start.
I tried using Adobe's DNG Profile Editor app on the S110 "Camera" profiles, but did not get good results. From what others have posted on Adobe's forums, this is to be expected. A lot of the "Camera" profiles are too complicated for DNG Profile Editor to work well on. Both the S100 and S110 Camera Standard profiles have over 23,000 lines of code when decompiled!
I also tried dcpTool (and DNG Profile Editor) with some of the other S series and G series profiles, without finding anything that works better than the S110 Camera Standard profile.

Camera RAW 5.6RC update

Is the Camera RAW 5.6 update suitable for PSE 7.0?

No problem. This happens all the time. First, Photoshop and Photoshop Elements get confused, and then there is Premiere, which has three main flavors: the old Premiere, Premiere Pro and Premiere Elements.
Also, there seem to be a number of "rabbit holes" in the forum, where one seems to be in one forum, but when they post, they find that they are actually in another forum. This happens a lot in the Forum Comments forum, as it seems that many of these rabbit holes silently lead there. It's filled with posts on Acrobat, Illustrator and InDesign - each with there own set of fora.
Good luck with the ACR update info,
Hunt

File handling in LightR 2.6RC importing from Leica M9

Please help - there is something going on here I don´t understand;
1. I shoot compressed DNG in my Leica - get lovely images!
2. I import to Lightroom 2.6 RC as DNGs via USB cable from the camera/device - usb port set in PTP protocol mode (have not tried "mass storage" yet)..
3. The dng file sizes in Lightroom as viewed in Library is only 8-10 MB (dimension 5212x3468). The file sizes on the SD card is 17,89 MB if I look at the files via a card reader (this is according to spec.). Do Lightroom compress the files?
4. I ask Ligtroom to back up the image files into a separate catalogue. However - here the files are in TIF, size 17,89 MB BUT dimension only 320x216???? Not possible to use.
Can anyone explain??
Thanks
/Anders
BTW - thanks for an excellent form with a lot of help!!

In LR terminology, a "catalog" is a LR database of settings and locations of photos. It is not a subfolder of My Pictures that contains photos, but I think I know what you were trying to say.
Everything seems normal about what is happening except the files in the backup folder are TIFs instead of DNGs. If your camera is producing DNGs then the files that get backed up should be DNGs. Can a Leica produce either DNGs or TIFs? Some of the higher-end Canon's create their RAWs with a TIF extension, but they are still just RAW-type files.
I think something may be interfering with the import when you do Import from Device directly from the camera.
In an effort to isolate the source of the strange behavior, as others have suggested, if possible, take the card out of the camera, put it in a card-reader and use Import from Device on that.
Also look at the folder of files on the card when it's in the card-reader and see if those files are TIFs or DNGs.
You might just rename one of the TIFs in the backup folder to .DNG and see if things can open it normally. Maybe Win7 or some other application is doing something to the files because they are under My Pictures and it is a watched folder? You might try moving the backup folder somewhere else out from under My Pictures.
Did this behavior occur with LR 2.5 and earlier, or is this the first version of LR that you've tried with the camera?
What happens when you use the released version of LR 2.6 not the release candidate, or is that was you are using, despite the subject of the thread?

Upgrading from XP to W7 - will I loose my LightR/M9 licence?

I plan to upgrade from XP to Win 7. In doing so I expect that I have to reinstall all software including Lightroom 2.6RC for my Leica M9. My questions;
- how do I transfer all historical data etc related to my images in Lightroom? I will of course take care of my DNG files - but will the Lightroom back-up take of everything else?
- can I reinstall Lightroom "within" my current license on the new platform without problems?
Thanks
/Anders

Your license is valid on any platform..windows, mac whatever version.
Ensure you have everything backed up to disks that do not contain the OS before you start the new instillation.
Make sure you copy your Lightroom catalog folder and all your image files in the same folder structure as they presently are in order to not have to relocate once upgraded. Install LR on your new system (use a downloaded copy, do not install from disk..you want the latest version, enter your license code and open the catalog..you should be good to go.

Can't open .DNG files in Preview and others

I am using Adobe DNG converter OR Lightroom to convert .RW2 from a Panasonic Lumix 3 to .DNG
This works:
1. Working with files in LR
2. Use PanoMaker to create panoramas
3. Create HDR with Photomagix
This does not work
4. Open files with MAC OS X 10.4.11 Preview (Vorscha) even though thumbnails look ok.
It says (in German) that it can not open the file
5. View files in Houdahgeo - Adding GPS info works
5. Use Photomagico to creat slide shows - only see thumbnails at the bottom
I also played with the settings in Adobe DNG Converter and LR (Raw 2.4, 4.1, 4.6, 5.4, User...Linear...Not compresse) but it did not help.
I searched multiple forums, found the problem twice mentioned on the side but never resolved. One hinted that its a problem since 10.4.11
Message was edited by: schillab

Hi,
(1) I'd think that if Adobe makes a XYZ to DNG converter for MAC OS X the goal would would that the following can open such a DNG file
        (a) All Adobe Apps ..... it works ....... mission accomplished
         (b) The native DNG viewer in OS X which is "Preview" .... it does not work!!!
         Note: the above works if XYZ is Canons RAW. If it is coming from a Panasonic LX3 one is out of luck
(2) I just tried the above with LR 2.6RC and DNG Converter 5.6. Nothing has changed.
Anybody having an idea? work around?
Christian

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!

Need Help installing "Backtrace" SOLVED

Hi
I need to install backtrace so that i can report Kde bugs with the debug output.... I have reported about 9 kde bugs in 4.6RC but
I have been asked to install backtrace. It is not in the official repos, but it is in AUR but I get the following error when trying to build it
(I don't know why kde just doesn't include backtrace by default since the automatic bug report tool pops up to report bugs but fails because you don't have backtrace)
[kaddy@archbox libbacktrace]$ yaourt -S libbacktrace
==> Downloading libbacktrace PKGBUILD from AUR...
x PKGBUILD
First Submitted: Mon, 02 Mar 2009 12:58:02 +0000
libbacktrace 3.0.0-1 : A C library replicating the bt functionality from gdb, allowing function stack tracing
( Unsupported package: Potentially dangerous ! )
==> Edit PKGBUILD ? [Y/n] ("A" to abort)
==> ------------------------------------
==> n
==> libbacktrace dependencies:
- liblogfile>=3 (building from AUR)
==> Continue building libbacktrace ? [Y/n]
==> --------------------------------------
==>
==> Building and installing package
==> Install or build missing dependencies for libbacktrace:
==> Downloading liblogfile PKGBUILD from AUR...
x PKGBUILD
First Submitted: Mon, 02 Mar 2009 12:29:07 +0000
liblogfile 3.0.0-1 : A C library providing a basic logging function
( Unsupported package: Potentially dangerous ! )
==> Edit PKGBUILD ? [Y/n] ("A" to abort)
==> ------------------------------------
==> n
==> liblogfile dependencies:
- glibc (already installed)
==> Continue building liblogfile ? [Y/n]
==> ------------------------------------
==>
==> Building and installing package
==> Making package: liblogfile 3.0.0-1 (Thu Dec 30 12:31:08 WST 2010)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Downloading liblogfile-latest.tbz2...
--2010-12-30 12:31:08-- http://www.wolf-software.net/Libraries/ … atest.tbz2
Resolving www.wolf-software.net... 82.165.15.30
Connecting to www.wolf-software.net|82.165.15.30|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 248307 (242K) [text/plain]
Saving to: "liblogfile-latest.tbz2.part"
100%[=========================================================>] 248,307 65.1K/s in 3.7s
2010-12-30 12:31:13 (65.1 KB/s) - "liblogfile-latest.tbz2.part" saved [248307/248307]
==> Validating source files with md5sums...
liblogfile-latest.tbz2 ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build liblogfile.
==> Restart building liblogfile ? [y/N]
==> -----------------------------------
==>
Last edited by kaddy (2010-12-30 14:52:15)

all done. Sweeeeeeeeet
For those that don't know how to fix it...
All I did was download the package that had the error from the main website..... (there was no checksum mentioned)
and then do a md5sum check on that package and edit the PKGBUILD with the correct sum and version and rebuild
Last edited by kaddy (2011-01-01 12:01:58)

Develop view stretching

Suddenly in 2.6rc, in the Develop module, all my vertical shots are stretched into landscape. I cannot find a setting anywhere that will fix this. Help!
* Edited *
(i originally said "loupe view" which was incorrect)

Is this really some freaky thing that no one has ever seen before? It's truly driving me bats. It's like there's suddenly a "zoom to fill" setting on somewhere (in Develop only) but i can find no such thing anyplace. I've deleted all previews and rebuilt them at 1:1 but same thing... Develop after "loading" will stretch what should be a vertical (or "portrait") orientation into a "landscape" orientation... and of course distorting the entire shot. Arrrghhhhhh.....

5.6 raw converter turns pure white into purple

i bought a canon 7D in early october and i still can't use PS cs4 to convert my raw files -- even the newest version (5.6) turns the highlights *purple*
has anyone else noticed this? is there a workaround? will adobe fix it soon? i hope so -- that's why i'm posting this in "feature requests."
please help -- i really need to get my workflow back!!!

Is this an sRAW or mRAW? The beta 7D support in ACR 5.5 had an issue with regular RAW format, and ACR 5.6RC still has a problem with at least sRAWs.
Eric (MadManChan) at Adobe is aware of sRAWs still not working right:
http://forums.adobe.com/message/2412132#2412132

I have just updated to LR5. I also have a new Camera. Nikon D800. Trying to import directly (from camera) into LR. But unsuccessful. Getting the following message. "The files are from a camera which is not recognised by the raw format support in Ligh

I have just updated to LR5. I also have a new Camera. Nikon D800. Trying to import directly (from camera) into LR. But unsuccessful. Getting the following message. "The files are from a camera which is not recognised by the raw format support in Lightroom." How can I import please?

Hi,
I assume you mean the Nikon D810 because D800/800E support has been there since Lightroom 4.1
Currently, because it is a new camera (D810) the only support is in a RC of ACR 8.6 for Photoshop CS6 and CC, as the RC runs out on 31 August it is expected support will be there in the next dot release of Lightroom.
Current limitations are that only full sized NEF is supported.
If you wish to import to Lightroom 5.5. you will need to download the DNG Converter v8.6RC and convert the NEF files (full size RAW ony) to DNG then import into Lightroom 5.5

Re: Newest Camera Raw Update

I downloaded and installed the most recent update for Camera Raw yesterday, which works fine. However, since then the Photo Downloader freezes when I click the select folder button. I have to force quit the downloader. Bridge and all the other apps on the computer work fine when this happens. Anyone else having this problem and what can I do about it?

Keli Douglas wrote:
…@ riswest and Ingram that is two people in 24 hours, I how big of a problem this will become?
Actually, riswets's post is already two months old.
That sounds like a well known Photo Downloader bug in the Mac version of ACR 6.5. Should be fixed in the ACR 6.6RC version available from Adobe Labs.
http://labs.adobe.com/technologies/cameraraw6-6/
Keli Douglas wrote:
Hi Grant,
Camera Raw is a plug in for CS5…
LOL ! You misread Grant's post. He was asking the original poster to indicate the model of his camera, whether he was using a card reader, etc.
FYI, the bug has been discussed at length in the Bridge Macintosh forum, which is where all questions regarding the Photo Downloader belong, as it is a Bridge Feature:
http://forums.adobe.com/community/bridge/bridge_macintosh?view=discussions&start=0#
There's also a dedicated, platform-agnostic Adobe Camera Raw forum:
http://forums.adobe.com/community/cameraraw
Wo Tai Lao Le
我太老了

LR 5.5 and acr 8.6

I have downloaded acr 8.6 RC so that I can process D810 RAW files. However, LR is not reading ACR 8.6.What am I doing wrong?
Thanks for any help.

ACR 8.6RC is only for Photoshop, Lightroom does not use the Photoshop plugin. As SausalitoDog said the support should come soon and probably in a LR 5.6 release.

ACR 8.6 RC and the D810 - have the controls changed? And is there a guide to using those new controls?

I just changed from CS5 to CC to support the Nikon D810.
When I open a RAW file from the D810, I am confronted by different sliders - things like Highlights and Shadows. White Balance and Exposure haven't changed, but the ones under that are different, or in different places.
I opened a D800e file in ACR 8.6RC, and the controls look the same as they did in CS5; it's only on D810 files I see the new controls.
I know how to drive the controls for the old ACR. This new set of controls, not so much
Is there a guide somewhere explaining the impact of the changed controls? I remember a really useful guide when "Clarity" was introduced, which explained (amongst other things) why I should be using Clarity instead of Contrast, and where to set a level of sharpening - that sort of stuff. I'm kinda hoping to find a similar guide for this.

This is new territory for us!
Can you clarify that both devices could sync with the Vista machine, or did they both fail? Was it 64bit Vista?
Did you try the Aceeca drivers as mentioned in the sticky post at the top of this section? (64bit Windows USB drivers).
I'm going to assume the same drivers might work with Win8. If you find this to be true, please let us know!
I have no present needs for a new computer, so we're relying on users to report back to us...
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

Nikon tethering working OK?

All,
I have to shoot tomorrow with a Nikon D200 or D300 tethered to either my Lenovo running Lightroom or a friend's MacBookPro also running LR (don't know which version.) Need to tether for teaching a bunch of students about lighting.
I tether back at home with my Canon dSLRs, so I am pretty used to the general process but of course have never done it in the Nikon orbit. With Canons we have the EOS Utility which works reliably. I don't tether directly into LR with the Canon bodies as the process has a flaky reputation. Anyone with recent experience with this body and LR? If we use my computer it will be LR 3.5.
I assume it's a "watched folder" process, even in v3 LR....
All suggestions greatfully received.
jonathan7007

Although LR3.5 was an improvement, some people still had tethering issues. LR3.6RC appears to have solved the problems, so you might want to use it instead of LR3.5.
For a discussion that is more Nikon-centric, see this one:
Lightroom: Tethering Bug: OSX 10.6.8 + LR 3.4.1 [Nikon]
Also, the process is not like a watched folder or auto-import. Tethered capture imports files directly into a folder that you specify when you start tethered capture.

LR 3.6RC vs. LR 3.6 /w D700 Camera Profiles v4

Similar Messages

Maybe you are looking for