25.01.2025, 00:09
I just changed the filtering on the top right drop down box on the Filtering tab from Vapoursynth (default on my setup) to Avisynth and ran it again - with rgb selected under the FFV1 tab but nothing else changed (and the same short test file as before). This time it worked and the output with MediaInfo correctly shows it as RGB 16 bit. So I am not sure what is happening here and for that matter I am not sure of the implication behind changing that drop down box setting or even if it matters - I will have to do some research and also check how it effects the processing speed.
I did read the sticky and changed the settings to produce a bug report but for some reason it does not produce one. I mentioned this in my previous post and acknowledged that the reports only might not be of any help and if that is the case that is fine - at least I tried.
As for QTGMC, I did thoroughly read up about it and have actually spent about 9 months refining my workflow which includes QTGMC (different settings for interlaced versus progressive input). The QTGMC documentation explicitly states that it can also be used on progressive input for temporal smoothing caused by poor deinterlacing (which is the problem I am dealing with in the source material) and I did very extensive testing to prove (or disprove) that to myself - carefully checking the final results on my LG OLED TV and making sure that the QTGMC step did actually madke an obvious and positive improvement. And it certainly did, though only with the settings I am using - applying source matching or enabling lossless for example produced a clearly inferior result to doing nothing at all but that is consistent with the QTGMC documentation on the topic in any case. I was just being thorough since the documentation was worded in such a way that it seemed to me that it was worth trying all the options regardless.
http://avisynth.nl/index.php/QTGMC#Progressive_Input
So although you say the settings make no sense, they do work. At least in my situation and with the particular source material I am dealing with. If I were to use good quality progressive input and QTGMC it would be pointless and destructive to the final quality of the output but I am dealing with a special case here where the material was poorly mastered but it is the only source material in existence.
And my last post on the subject (bed time for me too). I just researched the differences between selecting the avisynth and vapoursynth options and it changes quite drastically what QTGMC filtering does - and avisynth is apparently an old 32 bit processing pipeline, no multithreading and does not support more than 8 bits in any case (and it explains why the test I did ran at less than half the speed of vapoursynth).
I also did a test where I just ran the input through Hybrid without any QTGMC filtering but with RGB selected and the resulting output was perfectly fine RGB 16 bit FFV1 according to MediaInfo.
So the changes you made to the development version for the RGB option work fine with the testing I have done and the problem I am having seems to be specifically related to QTGMC itself when RGB is selected.
I will happily stick with the workflow I was using before. Thank you for your quick responses and adding the RGB option.
(25.01.2025, 00:04)Selur Wrote: Not a debug output -> useless to me. (read the sticky)
You might also, if your source is of good quality, those QTGMC settings make no sense. You might want to read up on QTGMCs settings.
I did read the sticky and changed the settings to produce a bug report but for some reason it does not produce one. I mentioned this in my previous post and acknowledged that the reports only might not be of any help and if that is the case that is fine - at least I tried.
As for QTGMC, I did thoroughly read up about it and have actually spent about 9 months refining my workflow which includes QTGMC (different settings for interlaced versus progressive input). The QTGMC documentation explicitly states that it can also be used on progressive input for temporal smoothing caused by poor deinterlacing (which is the problem I am dealing with in the source material) and I did very extensive testing to prove (or disprove) that to myself - carefully checking the final results on my LG OLED TV and making sure that the QTGMC step did actually madke an obvious and positive improvement. And it certainly did, though only with the settings I am using - applying source matching or enabling lossless for example produced a clearly inferior result to doing nothing at all but that is consistent with the QTGMC documentation on the topic in any case. I was just being thorough since the documentation was worded in such a way that it seemed to me that it was worth trying all the options regardless.
http://avisynth.nl/index.php/QTGMC#Progressive_Input
So although you say the settings make no sense, they do work. At least in my situation and with the particular source material I am dealing with. If I were to use good quality progressive input and QTGMC it would be pointless and destructive to the final quality of the output but I am dealing with a special case here where the material was poorly mastered but it is the only source material in existence.
And my last post on the subject (bed time for me too). I just researched the differences between selecting the avisynth and vapoursynth options and it changes quite drastically what QTGMC filtering does - and avisynth is apparently an old 32 bit processing pipeline, no multithreading and does not support more than 8 bits in any case (and it explains why the test I did ran at less than half the speed of vapoursynth).
I also did a test where I just ran the input through Hybrid without any QTGMC filtering but with RGB selected and the resulting output was perfectly fine RGB 16 bit FFV1 according to MediaInfo.
So the changes you made to the development version for the RGB option work fine with the testing I have done and the problem I am having seems to be specifically related to QTGMC itself when RGB is selected.
I will happily stick with the workflow I was using before. Thank you for your quick responses and adding the RGB option.