Apologies, I didn't mean to say that the encoder existed. I was just pointing out that ffmpeg didn't complain about the wrong argument. And when I say ffmpeg, I actually mean ffmpeg-python which is what we use to interact with ffmpeg. I also realize that ffmpeg-python may not fall in your purview at all. Just making an observation.
Best, - Nishant. On Wed, Mar 10, 2021 at 4:34 PM Moritz Barsnick <barsn...@gmx.net> wrote: > On Wed, Mar 10, 2021 at 15:54:28 -0500, FFmpeg user discussions wrote: > > Oh duh! Thanks @Moritz! > > You're welcome. > > > As a side note, I just wanted to mention that we mostly deal with RTMP > > streams and we have been starting the ffmpeg process the way I described > > for over a year and half now and it never complained. > > Hmm, I don't think an "h264_cuvid" encoder has ever existed - only a > decoder. (There was some cleanup recently in those aliases, but I > cannot identify such an encoder having being removed.) Perhaps you are > confusing the two? > > > would be interesting to note the behaviour here. Thanks again! > > No problem, as long as your encoding works again now. > > Cheers, > Moritz > _______________________________________________ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
