So that means the avcodec_encode_video is a reentrant function? (meaning it 
holds no global data?).
 
Also what if the AVcodec itself which is part of the codeccontext is shared 
between both contexts?> Date: Thu, 25 Dec 2008 12:14:26 +0100> From: 
[email protected]> To: [email protected]> Subject: Re: 
[libav-user] Thread Safety of avcodec_encode_video> > On date Thursday 
2008-12-25 03:03:04 +0000, Ash encoded:> > > > If I am to use two or more 
encoders at the same time (with different> > output buffers and different codec 
contexts, although the same> > codec), is there any rules I need to follow for 
thread safety or> > will it work as is?> > > > For example the following code:> 
> > > avcodec_encode_video(codeccontext1, outbuf, outbuf_size, picture);> > 
avcodec_encode_video(codeccontext2, outbuf1, outbuf_size1, picture1);> > This 
is a perfectly thread-safe usage, as each encoder will use> different context 
and data.> > Regards.> _______________________________________________> 
libav-user mailing list> [email protected]> 
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
_________________________________________________________________
Send e-mail anywhere. No map, no compass.
http://windowslive.com/oneline/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_anywhere_122008
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user

Reply via email to