No. ‘The girl in red’ only works for women. 
2 Likes
I have errors too!
Hello everyone, thank you for everything
There is actually a bug in this alpha where you lose frames and the video kinda stutter, when you export in ffv1 (I export in 10bit yuv420), when i export the same video in x265 there is no missing frame.
When I pass the ffv1 output in mkvtoolnix it shows me the real fps, for example a video in 24fps output in 23,500fps.
Also this is not my hardware fault, all others ffv1 video that I have worked, and my setup is powerful enough to read ffv1 in 4k (ryzen 7 7700x, 48gb ddr5, rtx 3080, samsung ssd 980 pro).
Thanks, have a good day!
It would be nice you extend the metadatas relative to Hyperion
“Enhanced using hyp-1; and exposure at 0” is now outdated, and to do comparison is somehow useless because so lacky
This didnt produce any HDR10 output for me, just 4:2:2 YUV (saved to .mov, though).
This part of patch is to only introduce color_range instead of leaving it blank.
You need to patch the output into MKVToolnix also filling empty fields (see screenshot)
1 Like
Ah. That makes sense. Thanks.
1 Like
Brilliant stuff, mate! Just what the Doctor ordered. 
I am a little confused on how you retrieve --max-cll, though. Feels a but like the chicken-and-the egg situation, where I don’t have the max-cll values yet for the to be created, new HDR movie; and in order to write the movie to disk, I will first need the max-cll data!
1 Like
At the moment, it is impossible without an external application.
I know DaVinci Resolve can do it, but I don’t have it. I am working (hard) on a way to recover it.
I found one, with brute force management, but to be fast, it needs a RAM drive (maybe huge), so I can provide a temporary solution until I find a more reasonable one, or expect Topaz to provide it.
For me, I think we can’t ask Topaz to focus on it, there are so many things to make perfectly executable before that.
What’s more, these values are not interpreted or even used in the same way depending on the codec, significantly complicating the task for Topaz
Personally, I only focus on AV1, because well exploited it literally buries all competition and it is really not well exploited in TVAI, something half normal given the need to contextualize all the parameters.
Yes, you’re right, to create a compatible BR-Disk it is necessary to get it, but you may use the Disk as a simple storage to get a MKV+AV1 ?
You may also try to set values assessed at random and do (many) tries
Then I suggest 400 to MaxFALL and 100 to MaxCLL as a starting point.
1 Like
One could maybe write a VapourSynth script to get --max-cll data per frame, and then for all frames, to get the min/max values? I’m looking into finding such filter right now (so I can do a preliminary pass to collect all --master-display and --max-cll data first.
Dammit, wrong thread…
