On date Tuesday 2009-04-14 13:13:13 -0400, AliReza Khoshgoftar Monfared encoded: > On Tue, Apr 14, 2009 at 11:12 AM, Stefano Sabatini < > [email protected]> wrote: > > > On date Saturday 2009-04-11 20:45:20 -0400, AliReza Khoshgoftar Monfared > > encoded: [...] > I have the locks now, but it still seems that my version of ffmpeg.c is not > completely threadsafe, as it fails in some of the tests. > Right now, I have locks around the functions mentioned in the previous post. > Do I still need to put locks around all avcodec_find_*()'s and allocation > functions?(I saw in an old post somebody told they are also non-safe)And if > yes, do they need to be the same mutex as the previous one?
Ugh, reading again the post I finally realized what you did, no doesn't look like a good idea to wrap ffmpeg.c into a function, this may cause problems especially if you try to find things which hasn't still been allocated, or worse many threads trying to register all the components at the same times. You can still do that introducing locks but it sound ugly and a maintainability hell. system(ffmpeg_command); should work just fine for what you want to do. Regards. _______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
