On 10/25/2015 11:44 AM, Michael Niedermayer wrote: >> One could argue this is not a representative sample. It's a single small >> file, >> which must always init (as opposed to a longer running process such as >> Chrome. >> Whereas if you have a longer sample, it wouldn't even be within the margin of >> error, I bet. > > If the usecase is to probe many files, then file duration would not > help hideing the init time. (to fill a GUI list or whatever)
I reject this notion. You are completely discounting that people use libavcodec *as a library*, and not via CLI. > Also startup time for normal playback itself does matter, as its > part of user vissible responsiveness, the user clicks play in his > players playlist and if that isnt instantaneaously starting playback > the user notices. So IMO startup time is not irrelevant I agree, but neither is thread-safety. Perhaps there is a middle ground. - Derek _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
