UHD BD to BD?

[Beber]

Well, to be fair, RipBot does use a comma for the decimal. No typo. I just reproduced the way it appears in it, except that I didn't include the hue part 'cause I didn't touch it.

[Chewtobacca]

^ I see. Well, I'll know in future.

---

Just so you guys know, I made a script based on the one that I posted in post#126, and successfully opened it outside of RipBot264 in VirtualDub2 (64-bit version).  There were no problems, and I didn't need to make any additions to the script beyond the usual functional stuff (e.g. pointing calls to LoadPlugin() to the precise locations of the plugins on my HDD, adding "return video", etc).  I did take out the call to Sharpen().

Technically, the highlights are occasionally slightly blown out after the conversion.

Top: video after HDR-to-SDR conversion
Bottom: Levels(0, 1, 255, 0, 242, coring=false, dither=true)



Most of the time, the luma stays very tightly within the TV range, but there were numerous moments of overshoot scattered throught the film (Gladiator). It's worth noting that the TV levels were conceived with a little overshoot in mind, so you might not consider this worth fixing. Still, now you know...

N.B. The levels adjustment given above is specific to this instance and shouldn't be seen as a generic adjustment.

N.B.  Installing RipBot264 is a pretty good way of giving yourself everything you need for the conversion  – in other words, if you don't fancy playing "hunt the plugin".

[X5gb]

Well, I give up with Grease, 4 times tried to convert and everytime it freezes on a still picture at different points in the film and stays that way for the rest of the movie. Will try something else instead.

[Chewtobacca]

Try getting it to work outside of RipBot264, which should have given you all the components already. All you need to do is write the script and open it
in VirtualDub2.

[X5gb]

I'll try Ripbot with standard settings on another film first, got a feeling it doesn't like something about my custom settings or in the Grease UHD rip.

[X5gb]

You can get rid of the sharpen 0.2 in ripbot too by going into the ini settings and changing it to 0.0.
Is it recommended to do that Chewtobacca or should I leave it at 0.2.

[Chewtobacca]

Is it recommended to do that Chewtobacca or should I leave it at 0.2.

It's not a matter of recommendations.  I prefer to select a sharpening filter myself on a case-by-case basis – or not sharpen at all.

[X5gb]

I'll leave it at 0.2 then.

[Chewtobacca]

^ Cool!

Going back to Gladiator, I used a vectorscope to check the saturation post-conversion.  The video seems fairly nicely saturated to me, rarely going beyond what is broadcast safe, even in scenes with intense reds.



This transfer's rich in oranges and yellows.  They often push the limit.



And occasionally they go beyond it.



But I've seen this happen from time to time on official releases, and it might not be worth doing anything about it. Overall, saturation doesn't seem to be much of a problem from a technical standpoint (though you might tweak it, of course, for personal preference).

Obviously, this is only one data point, and conversions of other films might fare differently, but I'm very pleased with what I've seen so far of DGTonemap. With the exception of the minor (and possibly not even necessary) levels adjustment that I mentioned above, it seems to do a great job.  I'm off to encode a test BD to see how it looks on a TV...

[X5gb]

Doing Mamma Mia at the moment, see if that one goes correctly on my main htpc and Grease yet again on another laptop to see if that one goes ok on a different machine, both CRF 20 rather than 2 pass with the perfect bd compliant settings, but the encode time on both is insane, close to 60 hrs each. (Have a q6600 on htpc and i5 on laptop). If they go to plan, Die Hard next at a high bitrate unlike the other ones floating around.