I have been following this thread because I have had issues with
thread synchronization in the past, secifically my problems have
stemmed from the need to use custom interrupt callbacks. Is there some
new inbuilt functionality that can avoid the use of these as timeouts
for ffmpeg functions?
Thanks,
Mark.
On 12 Jun 2010, at 21:52, Mike Scheutzow <[email protected]> wrote:
Jean-Daniel Dupas wrote:
Le 12 juin 2010 à 16:07, Mike Scheutzow a écrit :
Walter P. Mondale wrote:
I am trying to open multiple files simultaneously and noticed
that I
started getting errors such as "insufficient thread locking around
avcodec_open/close"
If you upgrade to a more recent version of the FFmpeg library,
thread locking should not be necessary.
I use a version from January 2010, and have no thread locks around
the FFmpeg library calls.
If you don't have error, it's just because you are lucky or you
don't access avcodec_open/close concurrently.
avcodec_open/close require locking in the svn trunk HEAD (the most
update to date version) but as I said, providing a lock manager
function is enough to prevent race conditions
I was not aware this was a problem, but I see the warning in
avcodec.h now that I look for it.
Thanks for the information,
--
Mike Scheutzow
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
