You need to enter the desired output resolution. For '-resize', as specified in the help again.For '-surfaces', I don't know what that means.Meaning 6 pixels cropped from top, 6 from bottom and none for left and right. For '-crop', it's as specified: '(top)x(bottom)x(left)x(right)'.> without proper documentation I'm not going to even try to implement these changes. what war valid strings for '-gpu' also in what order will ffmpeg apply crop&resize? The order they are specified, always crop first, always resize first. (, 15:46)Selur Wrote: Especially not planning to add these features without knowing more about them, i.e.

At some time I need to actually relax some time. And let the user enable and customize the options they want to use. (, 15:46)Selur Wrote: Quote:Basically provide the options for '-gpu ', '-surfaces ', '-crop ' and '-resize '. I'll send you a video on Drive, so you can understand better. Okay, loading the defaults after loading the source will always cause problems, since most of the setting collected will be lost. Hybrid should always decide the decoder based on the input and never the user. This is why I think defaults should not retain the decoder, but only the deinterlacer. (, 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. 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.īasically provide the options for '-gpu ', '-surfaces ', '-crop ' and '-resize '. same-rate (this will do -deint 2 -drop_second_frame) (, 15:28)Selur Wrote: Okay, I probalby will change teh cuvid support to only offer:Ī.

(, 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.

Ffmpeg crop and resize