DNG 1.7 (JXL lossy) support...?

[golemusu]

Hi. Is there any near term plan to add DNG 1.7 (JXL lossy) support in near term...?

Support seems to exist already in Libraw, although in its compiling Adobe SDK has to be included. Below is a related topic with some instructions from Libraw devs which might be useful if/when implementing it:

LibRaw/LibRaw#786

[gi-man]

You already asked this question in rawspeed. Why the duplicate? darktable-org/rawspeed#516

I don't think it is a good idea to covert raw files to lossy demosaic ones to then import into dt for editing. At that point, just shoot in jpg and edit the jpgs.

[wpferguson]

I don't think adding Adobe SDK as a dependency for darktable would work either

[golemusu]

You already asked this question in rawspeed. Why the duplicate? darktable-org/rawspeed#516

I am still unfamiliar what is difference of darktable and rawspeed Githubs and what should be discussed on which side.

I don't think it is a good idea to covert raw files to lossy demosaic ones to then import into dt for editing. At that point, just shoot in jpg and edit the jpgs.

I don't know much about internal implementation of Darktable. For editing purpose one of most important things (in my opinion) is ability to apply the highest quality noise reduction algorithms. If I have not misunderstood the algorithms require non-demosaiced data to function correctly. So in that perspective I do agree, demosaiced images would not help a lot in editing.

But if that is more complex to implement even seeing the image would help a lot when browsing through images.

Any idea how Adobe Lightroom might have implemented this? You can use high quality noise reduction algorithms. Is it more likely that they have made new versions of the algorithms that is applied to lossy JXL RAW data or is it more likely that the data is first converted similar format RAW data (lossless) which DNG 1.4 files contain, then loaded to memory and used traditional algorithms which have been used for years...?

Ps. the whole point for advocating this feature is that using it you can spare up to 50-70% in storage capacity and cloud storage costs and still maintain ability to apply high quality RAW processing algorithms. IMO it is pretty significant, especially as SSD prices have over doubled during last 6 months.

[kmilos]

You already asked this question in rawspeed. Why the duplicate?

I am still unfamiliar what is difference of darktable and rawspeed Githubs and what should be discussed on which side.

I guess it's a valid general enquiry on this side: dt uses rawspeed for 95% of its raw file loading needs. The other 5% (Canon CR3 only really for historical reasons) is (unfortunately, or for better or worse) served by LibRaw.

So I guess the question here is: would dt enable DNG 1.7 support via LibRaw + Adobe SDK as support for it through rawspeed won't be happening any time soon...?

Is there any near term plan

TBH, the only person who can answer this is someone preparing a PR as we speak and willing to commit to maintaining this (abomination of) integration on all platforms for years to come. Unless this happens to be you, I'm not aware of anyone intending to do that ATM.