Originally posted by ogunturkay Hmm... I think your information might be a little out of date.
About LR. With the K-1 at least, importing a RAW dng shot from the K-1 will offer you 5 camera matching profiles, Portrait, Landscape, Bright, Natural and Vibrant (I think). The other Custom Image profiles on the camera (such as mono and Film Reversal) are not accessible. The default for RAW files is for LR to apply Adobe Colour as the colour profile, and its actually quite nice, far from muted anyway, but you can change that anyway as I mention above.
Can you check your imported RAW files with another "viewer" after importing to LR. I am not talking about opening the file again in LR. I point that LR "removes 'embed' color profile". Of course if you open it in LR again you can get/apply those its 5 profile presets.
Fast Picture Viewer (or Faststone Image Viewer) show a Jpg preview of the RAW file, I'm not sure exactly what you're saying here and how this is relevant to SP?
The relation is that checking the "embed color profile". Is it still embed or not after LR; as I mentioned above. Not talking about JPG preview. (It doesn't show that either.) ICC profile. Here you can see the screenshot of "FastPictureViewer" preview: and here is another sc of the same file after LR with the same software:
I thought SP did support pixelshift for motion correction? DCU is not the best option for those files, numerous sites have proven that RawTherapee is better for handling Pixelshifted files, and my own findings confirm that to be true.
No it did not. Did those numerous sites complain about some strange pixelation issue?
DR? You mean Dynamic Range? Are you suggesting you can get even greater shadow and highlight recovery from SP than LR?
Yes I mean Dynamic Range. SP is better.
Thanks.
Cheers Ok, we might have to go back a bit here and start at the beginning as I'm a little confused over certain things.
First thing, why are we talking about FastPictureViewer at all, its totally separate from LR and SP, its simply an Image viewer software, the same as Faststone Image viewer, handy tool to quickly see RAW files usually my showing the Jpg Preview of the RAW files. Either way, why is this at all relevant in a discussion about LR and SP? When we decide to shoot RAW the intention is to edit the file in a proper RAW developer typically, is it not? Otherwise just shoot jpg and have everything embedded in the file properly at the time of the shot with whatever camera features you decide to turn on.
When importing an image (DNG) in LR for the first time, it is using Adobe Colour as its profile, you can use a pull down menu and change that to being a Camera Matching profile such as Natural, Portrait etc. You can synchronise that change across a batch of DNGs if you like. You may even be able to set LR to use a camera matching profile as standard upon all imports, I think that is an option but I don't bother with it.
I did want to know if SP can import the DNG file from the camera and apply more colour profiles from the camera than the typical five that LR can do, such as Mono, Film Reversal etc that the camera has. That would be good to know.
It sounds like your argument is that natively SP applies a better colour profile to the RAW image than what LR applies, however what version of LR are you using? Typically LR changes these things on updates, and seeing as you have about 10-20 different colour profiles to choose from and are synchronisable across a large batch I don't really see this as being a strong win for SP.
As I said before, importing a raw DNG file into RawTherapee and that software will too render the RAW (on default) differently to LR, it is even flatter and duller, but again I believe these things are changeable in RT, I have certainly done a few edits within RT to get something pleasing, it really doesn't overly stress me if the default render of the RAW is dull or lifeless, it is after all a just a canvas.
The issue with pixelshift is long and convoluted. Essentially it comes down to understanding that having the option switched on in the first place is only the beginning of fully taking advantage of the feature, there are additional steps that you should familiarise yourself with to get the best advantage of the tool. Motion Correction is often required, the recommendation is to turn it OFF in camera and let RT do the correction for you, it's typically at this stage the highest praise comes to RT with cleaner tidy ups being performed with fewer artefacts remaining. However even the motion correction in RT is quite advanced allowing a great deal of control over how its applied by the user. Lastly, a major advantage of Pixelshift is taking the Sharpness slider higher than what is normally possible with far less noise and IQ degradation than typically experienced. Usually the recommended flow is;
1) Take picture with pixelshift, motion off.
2) Import RAW file to RT and use its motion correction to achieve a cleaner image with fewer artefacts
3) Stress the file further than what non pixelshift files are deemed acceptable.
There are a lot of examples and articles on the internet showing DCU vs RT for pixelshift treatment, a google search should give you some further reading.
Interesting to hear you think a certain RAW developer handles the DR better than another. I was under the impression the sensor and camera gives the DR, it's not something that software can differ in exploiting.