24.01.2025, 21:54
Hi,
I use the QTGMC deinterlacer as part of my workflow where I am also making multiple passes through Topaz Video AI where I am using the lossless FFV1 codec with an RGB 444 16 bit colour space. The reason is that since I am doing multiple input and output passes through Topaz I am remaining in the "internal" format that Topaz uses (RGB48) and obviously remaining totally lossless during the workflow (apart obviously from the effects of the filters I am using). From Topaz at a certain point in the workflow it then goes to Hybrid for temporal smoothing (source material is badly deinterlaced 25p - originally derived from 50i but unfortunately that is the best source that I have). The Hybrid output then goes back to Topaz for one final pass of yet another filter (AION AI) taking it to 50p.
With the Hybrid step, there does not seem to be any possible way to avoid an RGB to YUV conversion - whilst I can choose 16 bit and i444, I cannot choose RGB like I see in the dropdown box for the FFVHuff codec for example. The FFVhuff RGB option, however only processes material in RGB 16 bit (at least in all my testing) with the Avisynth option selected under the filtering tab. This reduces processing speed drastically compared to the Vapoursynth option (the latter is about twice as fast) and in the end still outputs in YUV format regardless (and my input media is absolutely in RGB 444 16 bit format as per my Topaz parameters and this is verifiable with MediaInfo).
So my question is - is there any way at the "user" end I can tell FFV1 to remain within RGB 444 16 bit as per the input format? I did try to edit the associated json file for FFV1 but Hybrid appears to ignore it so I imagine the colour space options are hard coded elsewhere and I cannot change them.
I expect the answer is no but thought it worth asking just in case I have missed something.
Thank you.
I use the QTGMC deinterlacer as part of my workflow where I am also making multiple passes through Topaz Video AI where I am using the lossless FFV1 codec with an RGB 444 16 bit colour space. The reason is that since I am doing multiple input and output passes through Topaz I am remaining in the "internal" format that Topaz uses (RGB48) and obviously remaining totally lossless during the workflow (apart obviously from the effects of the filters I am using). From Topaz at a certain point in the workflow it then goes to Hybrid for temporal smoothing (source material is badly deinterlaced 25p - originally derived from 50i but unfortunately that is the best source that I have). The Hybrid output then goes back to Topaz for one final pass of yet another filter (AION AI) taking it to 50p.
With the Hybrid step, there does not seem to be any possible way to avoid an RGB to YUV conversion - whilst I can choose 16 bit and i444, I cannot choose RGB like I see in the dropdown box for the FFVHuff codec for example. The FFVhuff RGB option, however only processes material in RGB 16 bit (at least in all my testing) with the Avisynth option selected under the filtering tab. This reduces processing speed drastically compared to the Vapoursynth option (the latter is about twice as fast) and in the end still outputs in YUV format regardless (and my input media is absolutely in RGB 444 16 bit format as per my Topaz parameters and this is verifiable with MediaInfo).
So my question is - is there any way at the "user" end I can tell FFV1 to remain within RGB 444 16 bit as per the input format? I did try to edit the associated json file for FFV1 but Hybrid appears to ignore it so I imagine the colour space options are hard coded elsewhere and I cannot change them.
I expect the answer is no but thought it worth asking just in case I have missed something.
Thank you.