[FFmpeg-devel] [PATCH 1/2] ffmpeg: allow to set the thread message queue size.

Michael Niedermayer michaelni at gmx.at
Thu Feb 26 23:15:38 CET 2015

On Thu, Feb 26, 2015 at 07:56:06PM +0100, Nicolas George wrote:
> Le septidi 7 ventôse, an CCXXIII, Michael Niedermayer a écrit :
> > i think the case i tested had HAVE_W32THREADS set
> > also theres HAVE_OS2THREADS
> I suspect my question was too vague.
> If I understand correctly,
> Am I right?

i think so

> My main question is: do we have supported case where we do not HAVE_THREADS
> at all?

yes but i doubt multiple live stream inputs ever worked properly in
this case

> The basic reason I ask is that this kind of issue is that any application
> reading from a live stream and doing something else at the same time has
> similar kind of problems. We need some kind of really working non-blocking
> or input-driven API, and if we do not want to rewrite 90% of the demuxers,
> we will need threads.
> Regarding the patch itself, if you consider the series ok, you can pull this
> from my tree:
> a92193f lavd/alsa: set frame_size field.
> 508d6a2 ffmpeg: allow to set the thread message queue size.
> d92c6d8 ffmpeg: notify when the thread message queue blocks.



Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Many things microsoft did are stupid, but not doing something just because
microsoft did it is even more stupid. If everything ms did were stupid they
would be bankrupt already.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20150226/a9f86654/attachment.asc>

More information about the ffmpeg-devel mailing list