[Libav-user] Suggested alternative for av_oformat_next and av_codec_next?

Hi, My application (SimpleScreenRecorder) uses the functions av_oformat_next and av_codec_next in order to obtain a list of format and codec names to display in a drop-down menu for the user. Incompatible formats and codecs are filtered out to the extent that this is possible with the current

[Libav-user] decode_video.c can not decode 8192 * 4096 media file.

Hi every one, I had used decode_video.c to decode my media file. I found it can decode some media files such as h264 media file. but it can not decode h265 media file at 8192 * 4096. it shows some error message at av_parser_parse2 function called. my version is ffmpeg 4.0 how can i

[Libav-user] prores encoding

Hi Folks, I'm having trouble with both prores codecs -- prores, and proes_ks. I've tried both and even though both support FF_THREAD_FRAME I'm getting significant frame tearing given the more threads I use. I'm setting: vctx_->profile = 3; vctx_->thread_type = FF_THREAD_FRAME;

Re: [Libav-user] decode_video.c can not decode 8192 * 4096 media file.

2018-05-21 12:34 GMT+02:00, 刘粤桂 : > I had used decode_video.c to decode my media file. I found it can > decode some media files such as h264 media file. but it can not > decode h265 media file at 8192 * 4096. it shows some error > message at av_parser_parse2 function called. Does

Re: [Libav-user] prores encoding

2018-05-21 22:24 GMT+02:00, David Ibbitson : > Hi Folks, > > I'm having trouble with both prores codecs -- prores, and proes_ks. > > I've tried both and even though both support FF_THREAD_FRAME > I'm getting significant frame tearing given the more threads I use. > > I'm

Re: [Libav-user] prores encoding

> On May 21, 2018, at 4:10 PM, Carl Eugen Hoyos wrote: > > 2018-05-21 22:24 GMT+02:00, David Ibbitson >: >> Hi Folks, >> >> I'm having trouble with both prores codecs -- prores, and proes_ks. >> >> I've tried