#1663: Multiple named pipes don't work
-------------------------------------+-------------------------------------
Reporter: burek | Owner:
Type: defect | Status: new
Priority: normal | Component:
Version: unspecified | undetermined
Keywords: | Resolution:
Blocking: | Blocked By:
Analyzed by developer: 0 | Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by burek):
Well if I'm wrong (and I've used named pipes a lot in the past and never
had such issues like this one mentioned in this ticket) then the faq item
might be wrong as well. Since it does exactly what I described here.
Btw, such an example of a dead lock, that you offered, simply shouldn't
happen in this scenario, since 2 outputs are completely independent (raw
audio vs raw video) and if I'm not wrong, ffmpeg does that in separate
threads, so that situation should never happen.
Also, 1 process is using both pipes for write only and 2nd process uses it
as read only. So that's also the indicator that such deadlock should never
occur in theory, for this scenario.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1663#comment:6>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
