This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[BUG] QTGMC - "Lossless" should be disabled for progressive input
#1
This applies to both Avisynth and Vapoursynth.

If you want to use QTGMC on progressive input for temporal smoothing, you select the "Custom" preset and set the "Input Type" to 1.

[Image: NiTs3Ox.png]

There is a setting in the above image called "Lossless." This seems to be tied to the deinterlacing functions of QTGMC. So if you enable it with the input type set to 1, it will cause a crash when the video is processed. You can test this by previewing a progressive video, setting the Input Type to 1, and selecting a Lossless setting. In Avisynth preview you will get all kind of garbled text and rendering errors (or even a Hybrid crash). In Vaporsynth preview there's no crash but it makes QTGMC stop working; try to advance frames and you won't be able to.

When Input Type is 1 (progressive) and Lossless is off, Vaporsynth preview seems to behave very stable, while Avisynth preview seems to occasionally get an error and jump back to the first frame when adjusting other settings, such as Sharpness. Not sure if this is due to anything in Hybrid or not.

Anyways, Hybrid should grey out "Lossless" and set it to "off" if "Input Type" is anything other than 0.
Reply
#2
I'll adjust Hybrid accordingly.

Cu Selur

ps.: LOL, just looked at the source code, I already wrote code for it but it didn't get executed due to a typo -> will be fixed in the next release.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)