I’m reading something else. Edit in 16 bit, export in 8 bit for most output devices are in 8 bit. There’re some filters that doesn’t work with 16 bit so you’re forced to work with 8 bit in editing. Typical filters that only work with jpg.
But do the editing in 16 bit.
Truth is for philosophers and clergy… Just go along with what works for you and enjoy that it does.
Please see the PL6 upgrades which may be of interest to the discussion here.
They will only be of interest if someone can tell us what this new wide gamut colour space actually is:
a) Is it ProPhoto or some other widely known, used and respected colour space?
b) Is it some new-fangled thing that DxO have invented and thus is a propriety colour space?
From what I can tell, the answer is b.
I’m afraid so…or does it correspond to Adobe Wide Gamut RGB?
And I sincerely hope that DxO will fix the broken colour rendering related items and the * PL6 DNG export options - DxO PhotoLab - DxO Forums
In which case I think I’ll save my money and skip this year’s update.
Because without knowing what the colour space actually is, it smells of smoke and mirrors just to appease the clamour from users for PL to use something like ProPhoto.
If it’s not just a marketing ploy then DxO should have no problem publishing details of how their wonder gamut compare to Adobe RGB / ProPhoto / [insert name of your favourite colour space here]. The fact they are not trumpeting these sort of comparisons is significant, in my (far from) humble opinion.
Have you considered downloading the 30-day free trial checking out the results you get before making that decision? Also keep in mind, that you do not have to use the new color space if you prefer the previous one.DxO was using, which is now called Classic.
As PL is able to export files with ProPhoto color space, we could think that the working space is at least covering it…
I found this via a reviewers website…
A buzzword but hardly usable in practice.
I developed a RAW with it and exported it as SRGB to the hard disk. Result SRGB ignored and DxO Wide Gamut exported.
That’s a bug on Mac, which doesn’t occur on Windows as far as I know (Windows user)
That doesn’t help me, cause I’m a Mac user …
I’d be curious to know more about the purported benefits of this wider gamut over Adobe RGB, or why DxO created a custom gamut instead of using something like ProPhoto (in layman’s term if possible ^^).
Their graphic seems to show that their custom gamut covers Pointer’s Gamut (a gamut that is supposed to cover all of reflected light, so you lose stuff like the blue light that a blue sun would shoot directly in your eyeball but that’s maybe acceptable for photos taken on this Earth), and avoids going into non-existing colors (like ProPhoto does). But it would be interesting to have an explanation of why that’s useful.
That said, I don’t share the suspicion that it’s just a marketing gimmick. As a software developer I suspect that doing all the image math in a bigger color space is something that required a lot of work, and I don’t see DxO engineers taking on that work just to please the marketing boss. Usually you try to come to an agreement between the engineering team and the marketing team so that everyone is happy , especially for a long and costly effort.
Maybe staying on Adobe RGB is a better trade-off, or maybe using ProPhoto RGB is a better trade-off than what DxO made. It’s always possible than an interesting engineering effort doesn’t pan out. I guess we’ll see in practice (on more than one picture and one screen before calling it revolutionary or useless, hopefully ).
If it’s a bug, it will be fixed. That will help you.
What I mean to say is that the wrong color space in meta data (don’t know if the actual color space is wrong as well), is not intended behavior. Writing off the DxO Wide Gamut as a buzzword because of this bug is a bit harsh in my opinion.
Confirmed. With Wide Gamut selected, the choice you make, is ignored. No matter if you select as recorded or e.g. sRGB.
When I release a new feature, I test it thoroughly, at least that’s how it was done in my company at the time.
PS: But the problem is more confusing when use Classic (Legacy) DPL 6 exports in Adobe RGB …
And nothing ever slipped through? Ever? That would be a first one for me, in all my years/decades as a professional software tester as it would mean the company had an unlimited resource of time and money.
But we’re getting off topic