[FFmpeg-devel] Allow interrupt callback for AVCodecContext

Don Moir donmoir at comcast.net
Mon Jan 6 09:17:38 CET 2014

Le sextidi 26 frimaire, an CCXXII, Don Moir a écrit :
>> So you have to ask what the real hack is. Keeping an opened cached
>> context or having an interrupt callback. An interrupt callback does
>> not use any additional resources but then it has to be implemented
>> for every decoder.

>What do you mean, it "does not use additional resources"? A callback needs
>to be called. That means the decoder has to frequently interrupt its work
>and call some foreign function, consuming time and letting the caches get
>cold in the process, precisely during the most speed-critical phase of a
>video framework. And that just in the possible case someone would have the
>same very specific needs as you.

Yeah callback needs to be called but that is negligible. It does not need additional memory resources that matter and no additional 
threads. The default is a noop and always a very quick return (up to user but common sense dictates return immediately otherwise 
user is at fault for slowness). It does not seem to matter to you though, that av_log is called very often..

>And, by the way, can you please fix the time and date on your computer?

Clock battery dead or dying and not a simple change out right now because busy, but reset clock for this email.


  Nicolas George 

More information about the ffmpeg-devel mailing list