madvr measures always fail

[phi-alek]

first of all a big thank you for this great script. whenever i want to use dovi maker workflow 3-1 or 3-2 the madvr measure always fails. im using mkv but i always get an error that for some reason madvr could not measure at the end of the measuring process. when using workflow 6-2 i have noticed when i crop avs creates a file for madvr which finishes the measuring, but then batch measuring is not working. my favourite workflow would be 3-2 as its fast and i dont care for accuracy for hdr10 to dv conversion. but i can not use it as it always fails to measure, i need to encode everything to prores for it to work. i think the best way so solve it, would be an option to always encode in prores for measuring. in workflow 3-1 we have that workaround, but it always tries to measure without prores first which takes time. so if we could force always prores encoding, that would be wonderful. also if we could downscale 4k to 1080p for the measuring, which would make everything faster. i know its not accurate, but that might be fine for some users. thank you again!

[R3S3t9999]

i think the best way so solve it, would be an option to always encode in prores for measuring. in workflow 3-1 we have that workaround, but it always tries to measure without prores first which takes time.

line 222
::workaround for movies that wont work in madvr scene cut generation in 3-1 (default= NO)
set madvr_workaround=NO

when using workflow 6-2 i have noticed when i crop avs creates a file for madvr which finishes the measuring, but then batch measuring is not working.

Yes possible, the batch mode is not meant for cropping.

also if we could downscale 4k to 1080p for the measuring, which would make everything faster

Measurements are slightly less accurate when I do that.

[phi-alek]

Thank you for the reply :). yes I know about the workaround, but it only encodes to prores, if madvr failured, and it does it with every video, so the time for the whole process raises. i think just an option where 3-1 and 3-2 would always use prores would be so much better. also for 3-1 we have to encode to prores anyway for cm_analyzer, so why not encode to prores from the start. it would not take longer and madvr will not fail.

but anyhow im really happy that we have this script. its a lifesafer.

[R3S3t9999]

if you enable that setting, the script will first convert to prores and generate the scene cuts from it.
if you don't enable this setting, then yes the script will first try with madvr and then encode to prores.

[phi-alek]

thanks it worked!!! thats very good!!! i know now why the measure always fails. the stream within the container is messed up with weird frametiming. its a 24 fps container with 24fps stream, though ffmpeg recognzies it at 23.976 frames, so meta data and video dont match. i could fix it with hybrid, forcing it to render only with conastant framerate at 23.976, and now madvr doesnt fail anymore. still that workaround with prores is overall much faster, since i have set it to 1080p too.

in the dovi script gui beta, is a feature to duplicate frames. how can i use that? some of my videos got messed up and hdr10+ metadata and video are not in sync because of the wrong frame timing. i miss about 85 frames in a 60 minute video.

[R3S3t9999]

Yes, if i remember correctly, the GUI can resync HDR10plus but I'm not 100% sure... The cli version certainly can.