It's really nice that Hybrid has custom filters so the user can apply settings that aren't in Hybrid, for example a custom QTGMC like this:
(This is a "tweaked" setting someone shared for noisy, interlaced VHS & DVD sources. I've tried it out and it looks great!)
But that's just an example.
The problem, is that in a custom deinterlace script, Hybrid doesn't (nor shouldn't) attempt to evaluate the script for a new frame rate, so, any filters that the user selects not via custom, after the custom deinterlace script, and that need the current frame rate as a variable will have that variable incorrect.
The same thing is true for any changes made to the color matrix. If a custom script changes or converts it to 601 for example, if the input was 709, any filters or converts that Hybrid inserts after the custom filter will put it back to 709.
So I thought it might be nice (and hopefully wouldn't be too hard to implement) some settings for the custom filters along the lines of "assume new" for after the custom script is run. This will allow the user to tell hybrid what their custom script did to the frame rate or the color matrix. It will of course be up to the user to put correct info in... which is currently the case for a custom script!
In this way, Hybrid will better work with custom scripts that change the frame rate and/or color info.
Maybe something like this:
![[Image: ErbWfcg.png]](https://i.imgur.com/ErbWfcg.png)
So each custom filter could have these check boxes... if unchecked, it does nothing (like it is currently), if checked, Hybrid then assumes the custom filter has changed the frame rate and/or color matrix to whatever the user has entered or selected from the options. In the above example, the frame rate should change to 59.94. (I forgot to delete the "InputType=2").
QTGMC(Preset="Placebo", NoisePreset="Slower", ChromaMotion=True, TrueMotion=True, TR0=2, TR1=2, TR2=3, Rep0=3, Rep2=3, NNSize=3, NNeurons=4, EdiQual=2, Precise=True, NoiseProcess=2, GrainRestore=0.3, NoiseRestore=0.01, Sigma=2.0, Denoiser="dfttest", DenoiseMC=True, NoiseTR=2, NoiseDeint="Generate", StabilizeNoise=True, EdiMode="NNEDI3", EdiMaxD=16, Sharpness=0.3, Smode=2, SLMode=0, SLRad=3, Sbb=3, MatchPreset="Placebo", MatchPreset2="Placebo", SourceMatch=3, MatchTR2=1, MatchEnhance=0.85, Lossless=2)(This is a "tweaked" setting someone shared for noisy, interlaced VHS & DVD sources. I've tried it out and it looks great!)
But that's just an example.
The problem, is that in a custom deinterlace script, Hybrid doesn't (nor shouldn't) attempt to evaluate the script for a new frame rate, so, any filters that the user selects not via custom, after the custom deinterlace script, and that need the current frame rate as a variable will have that variable incorrect.
The same thing is true for any changes made to the color matrix. If a custom script changes or converts it to 601 for example, if the input was 709, any filters or converts that Hybrid inserts after the custom filter will put it back to 709.
So I thought it might be nice (and hopefully wouldn't be too hard to implement) some settings for the custom filters along the lines of "assume new" for after the custom script is run. This will allow the user to tell hybrid what their custom script did to the frame rate or the color matrix. It will of course be up to the user to put correct info in... which is currently the case for a custom script!
In this way, Hybrid will better work with custom scripts that change the frame rate and/or color info.Maybe something like this:
So each custom filter could have these check boxes... if unchecked, it does nothing (like it is currently), if checked, Hybrid then assumes the custom filter has changed the frame rate and/or color matrix to whatever the user has entered or selected from the options. In the above example, the frame rate should change to 59.94. (I forgot to delete the "InputType=2").