[FFmpeg-trac] #8944(undetermined:reopened): 2 output fifos are not enough (4.1.6)

[FFmpeg]

#8944: 2 output fifos are not enough (4.1.6)
-------------------------------------+-------------------------------------
             Reporter:               |                    Owner:
  SteveNewcomb                       |
                 Type:  defect       |                   Status:  reopened
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  4.1.4        |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by jdlh):

 I agree that the FFmpeg documentation should include a reference like your
 paragraph, which says that more than just pipes 0, 1, and 2 are supported,
 and under what conditions.

 This ticket is a poor place to put that message, however, because the
 ticket's description is already centred around the observations about
 ffmpeg functionality: "ffmpeg can only write streams to 2 fifos" and "2
 output fifos are not enough". Those observations are based on a
 misunderstanding of the functionality. That means this ticket will likely
 get closed and ignored.

 It would be better to have a separate ticket which is centred on the
 documentation omission.

 Just to set your expectations, however, this project does not seem to
 value improving its documentation. Don't be surprised if that ticket
 languishes. You could also learn how to edit the documentation, and submit
 a patch with the documentation fix.  That patch might well also languish,
 because it may not get the sign-off required for it to be applied.

 As evidence of this attitude, see [comment:3 Cigaes]:
 > FFmpeg's documentation is not a a beginner's course to Unix. Learn to
 use your operating system.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/8944#comment:4>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker