On Tue, 29 Sep 2009 05:49:30 -0400, Stephan Assmus <[email protected]>
wrote:
I've tried to find a way to search this list, but could not find one from
the link at the bottom of every mail to this list.
Google:
site:http://lists.mplayerhq.hu/pipermail/libav-user/ multithread
;-)
In any case, I've looked into the code, so far it seems the "lockmgr"
callback is indeed only used when opening or closing codecs. What other
calls are not thread-safe?
[...]
I do make sure that av_register_all() is only
called once. What other potential pitfalls should I be aware of?
I haven't kept up with changes to the codebase, so LockManager looks like
a new and welcome addition to eliminate the voodoo from this problem. The
post I was thinking of is
http://lists.mplayerhq.hu/pipermail/libav-user/2009-March/002556.html
"
Here's a list of other functions that also need locking:
- avcodec_find_encoder()
- avcodec_find_decoder()
- av_find_stream_info()
- avcodec_close()
"
You can probably search the libav-devel list to see the dev's discussions
on the problem.
--
Michael Conrad
IntelliTree Solutions llc.
513-552-6362
[email protected]
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
