24.08.2021, 15:39
(24.08.2021, 15:28)Selur Wrote: About the frame rate adjustment: That would only be needed in case the encoder is also ffmpeg based when piping the output to an encoder, the frame rate ist written by the encoder.
Yes, that's what it seems.
(24.08.2021, 15:28)Selur Wrote: Okay, I probalby will change teh cuvid support to only offer:
a. bob (this will do -deint 2)
a. same-rate (this will do -deint 2 -drop_second_frame)
Why not just redact it as "CUVID (FFmpeg)" and let the user choose whether, which and how to use the options CUVID provides? Similar to what you did with YadifMod.
Basically provide the options for "-gpu <string>", "-surfaces <int>", "-crop <string>" and "-resize <string>". And let the user enable and customize the options they want to use.
(24.08.2021, 15:28)Selur Wrote:Quote:Sorry, forgot to mention that after the h264 input was loaded and the defaults were set, I restored the defaults. This is why I think defaults should not retain the decoder, but only the deinterlacer. Hybrid should always decide the decoder based on the input and never the user.Okay, loading the defaults after loading the source will always cause problems, since most of the setting collected will be lost,...
-> probably not going to changing that.
I'll send you a video on Drive, so you can understand better. But that will be later.