>
>
> Your first attempt - iiuc - was not to use the skip_frame option for h264
> and
> vc1 input but to re-implement it in your code (which is technically
> difficult or
> impossible because only while decoding can you decide what to drop).
> I suggest you use the option instead of
Am So., 19. Apr. 2020 um 23:56 Uhr schrieb Simon Brown
:
>> libavcodec's skip_frame option works fine for h264 and vc1, I strongly
>> suggest
>> that you don't try to reimplement it after testing with "ffmpeg" that it does
>> exactly what you need.
>>
> I'm confused with your negatives in that
>
>
>
> You can do --enable-decoder=aac,h264,vc1 to make the configure line more
> readable.
>
> Thanks - it's good to learn even basic things like this!
> libavcodec's skip_frame option works fine for h264 and vc1, I strongly
> suggest
> that you don't try to reimplement it after testing with
Am So., 19. Apr. 2020 um 22:57 Uhr schrieb Simon Brown
:
>>
>> But the question was how you compiled FFmpeg.
>>
>> > I tried skipping frames, but then it had too many errors
>>
>> Can you reproduce these errors with ffmpeg (the command line interface)?
>> (Assuming you tested the skip_frame
>
>
> But the question was how you compiled FFmpeg.
>
> > I tried skipping frames, but then it had too many errors
>
> Can you reproduce these errors with ffmpeg (the command line interface)?
> (Assuming you tested the skip_frame option)
>
> Carl Eugen
>
> Thank you Carl, and apologies for
Am Sa., 18. Apr. 2020 um 00:35 Uhr schrieb Simon Brown
:
>
> On Fri, 17 Apr 2020 at 22:50, Carl Eugen Hoyos wrote:
>>
>> Am Fr., 17. Apr. 2020 um 20:38 Uhr schrieb Simon Brown
>> :
>>
>> > Thanks Devin, found the right place, but finding frames to skip seems to
>> > be taking more CPU time.
>> >
On Fri, 17 Apr 2020 at 22:50, Carl Eugen Hoyos wrote:
> Am Fr., 17. Apr. 2020 um 20:38 Uhr schrieb Simon Brown
> :
>
> > Thanks Devin, found the right place, but finding frames to skip seems to
> be taking more CPU time.
> >
> > Is there any way of building ffmpeg libraries to a) minimize any
Am Fr., 17. Apr. 2020 um 20:38 Uhr schrieb Simon Brown
:
> Thanks Devin, found the right place, but finding frames to skip seems to be
> taking more CPU time.
>
> Is there any way of building ffmpeg libraries to a) minimize any other stuff
> that isn't being used
Yes but even showing us how
On Fri, Apr 17, 2020 at 2:38 PM Simon Brown wrote:
> Thanks Devin, found the right place, but finding frames to skip seems to be
> taking more CPU time.
You probably need to understand where within libavformat/libavcodec
the time is being spent. Such an exercise in profiling can be
On Fri, 17 Apr 2020 at 13:53, Devin Heitmueller
wrote:
> Not through the standard APIs, as implementations of FIFOs within
> input modules vary depending on the input. In my case (which is the
> UDP source), I added instrumentation to libavformat/udp.c which once a
> second calls
> My problem is that from time to time my decode or frame copying gets behind
> and if it gets too far behind I end up with a "circular buffer overrun" error
> and it bombs out. What I want to be able to do is determine WHEN I'm getting
> behind in decoding and so take the option of dropping
I am trying to decode a live stream using the libav libraries from ffmpeg.
I open a udp input using avformat_open_input.
I get the stream information and open_codec_contexts for the video and
audio streams.
Then when everything is setup I go through a loop of
av_read_frame
decode_packet
12 matches
Mail list logo
