Here you go. Please bear in mind that these images are not in a calibrated colour space. That is, I just use the RAW RGB values. EG The problem with over-saturation of the blues would still probably happen with normal colour management.
@Iain and i have been working heavy on a darktable implementation of his ideas, many things had to be implemented in a slightly different way or required new stuff in dt. It’s already usable with good performance (on my 8core E-2288G the algo takes <100msec on the selected image), some issues remaining but we both are confident we find a good solution.
Here is a screenshot, no filmic applied so no interference from there, slightly dark for better view of the highlights, just default color management.
I’m telling you this is the best darktable news I’ve heard in a long time. So looking forward! Handling of blown out highlights has (for me) long been the achilles heel of dt. “reconstruct in LCh” often does too little and “reconstruct color” has a very high chance of really nasty artifacts (such as pink striping/patterns). How common are strange artifacts like those with @Iain 's color propagation method?
Lastly, is there any chance whatsoever of this ending up in the 3.8 release?
There’s no chance of those weird pattern artefacts. Other kinds of artefacts, well, that’s different.
But seriously, all highlight reconstruction is guesswork. The approach we are taking, splits clipped areas into patches and tries to guess the correct colour for that patch. The most obvious artefact is when the guessed colour is completely wrong.
A large patch of the wrong colour should be more easily corrected with other tools than weird patterns and smudged colour.