The following warnings occurred:
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/printthread.php(287) : eval()'d code 2 errorHandler->error_callback
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



Selur's Little Message Board
[BUG] Interlace Store Method Changing Upon Conversion - Printable Version

+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html)
+--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html)
+--- Thread: [BUG] Interlace Store Method Changing Upon Conversion (/thread-2847.html)

Pages: 1 2 3

RE: Interlace Store Method Changing Upon Conversion - Analog - 31.08.2022

Hi Selur,

Thanks for the information and for making the update.

You are correct that Vapoursynth R60RC1 appears to have fixed the "washed out" video output! Wonderful! It looks like FFV1 10bit direct to FFV1 8bit works OK now. This is a great update so thank you so much for spending the time to assist me!

One last thing... When converting from my FFV1 master file to any other format (including just passing through), it appears to be losing it's metadata even though I have no advanced metadata selections set in Hybrid, etc. When converting to FFV1 8-bit, however, everything seems to be preserved.

I've attached an image of the metadata of four files. ".mkv" is the source file (FFV1 interlaced 10-bit), "_new.mkv" is processed QTGMC/progressive ProRes, "_copy.mkv" is simply with video & audio "passthru" selected in the "Base">"Processing" section of Hybrid, and "_FFV1.mkv" is the output converted to FFV1 8-bit with no other processing.

This can be replicated simply by passing thru a video with metadata (like the video I have given you in my previous link to you which should still be good). Let me know if you need more info like a debug log file.

Is this a bug? I feel like at least the color range and compression attributes (i.e. "coder_type" field) should be written to the output file if possible...

Thanks!

RE: Interlace Store Method Changing Upon Conversion - Selur - 31.08.2022

Unless you tell Hybrid sprecifically through "Config->MKV tagging" such container only vui data is ignored.
No this is not a bug. VUI data belongs inside the video stream not inside the container, especially HDR data.
Adding that data to the container is a workaround of mkv for formats which normally do not support such tagging.

Cu Selur

RE: Interlace Store Method Changing Upon Conversion - Analog - 02.09.2022

Got it! Makes sense. 

Big thanks once more!