![]() ![]() Yeah, the first part usually is the one a converter engine like Libraw/DCraw should take care of otherwise I will be designing my own raw converter if I jump too much in the details here except of course for adjusting some few parameters such as (gamma, WB, image end-format.etc.) more saturated color, much of compression, less time consumption) Oh by the way, relaying on the default parameters of Libraw/DCraw, in my opinion, I don't think they are the optimal in term of accuracy but rather usually they are optimized based on pleasing and time criteria (i.e. Well, satisfactory.hmm this the point, I am not really trying to just make a pleasant good-looking photos but rather I am more into color accuracy and authenticity so I would appreciate any advice/idea in that direction for what to follow in specific or just to hear what is the common practice among professionals Here's various outputs from RawDigger (uses LibRaw) based on a Foveon X3F input:Thanks a lot for your efforts, though I quite didn't understand the difference between the photos you've posted, I mean what were the conversion paramters in each, could you maybe tell? Raw is using the image data unchanged unless gamma or different white balance or saturation is selected, see below. It could be satisfactory to your good self but unlikely to be better than what LibRaw does, IMHO. I am sure there should be a way cuz, to my understanding and my speculation - as Libraw/DCraw is part of RawTherapee studio- are in RawTherapee the two steps processing just like what I am trying to achieve in my workflow are happening the same, like there must be a step where RawTherapee is using DCraw first to decode the raw data and then the second step where it tries to assign to the decoded data an ICC profile using? (I am not quite sure what). Is it the best practice to go to a wide color space gamut as output of conversion and then re-map that gamut to my custom ICC profile's gamut (something like ProPhoto maybe)? How am I supposed to deal with Libraw/DCraw so that I can de-mosaic a raw image in order to assign to it my custom ICC profile later on as it doesn't support internally profile passing argument other than the hard-coded ones? So basically I see the problem of correcting an already-corrected image. Well, as a CS engineer it is needed for some software development actually. Now coming to your question, how much of difference I see between the "color corrected" images my workflow produces and reality, so far it is really too much just judging by the naked eye (I follow also the DetalE metric by the way) However, unfortunately with my current workflow using two separate software ( Libraw/DCraw + LittleCMS) I am not even close to that. ![]() In the workflow I am trying to establish I don't think I need to go beyond that in part 1.įor part 2, this is actually my main focus and what I am trying to achieve is really an accurate color rendition as much as possible to reality and yeah I would make the efforts to make the last 5% jump even it would take much time. I guess I don't understand why you are jumping through all these hoops.yeah, the first part usually is the one a converter engine like Libraw/DCraw should take care of otherwise I will be designing my own raw converter if I jump too much in the details here except of course for adjusting some few parameters such as (gamma, WB, image end-format.etc.) Part 2 - make sure that the image is as true to the original as it can be. Part 1 - take the data that the camera has recorded and turn it into an image file and Let's break this discussion into the two significant components: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |