[FFmpeg-trac] #7328(avformat:closed): Bug: FFmpeg's tee muxer treats a named pipe output as a regular output file instead of 'writing' into it as expected.

[FFmpeg]

#7328: Bug: FFmpeg's tee muxer treats a named pipe output as a regular output file
instead of 'writing' into it as expected.
------------------------------------+------------------------------------
             Reporter:  Brainiarc7  |                    Owner:
                 Type:  defect      |                   Status:  closed
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:  invalid
             Keywords:  tee muxer   |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+------------------------------------
Changes (by Brainiarc7):

 * keywords:   => tee muxer
 * component:  undetermined => avformat


Comment:

 And related,

 When I remove the {{{>}}} from the command line, the same behavior as
 above is repeated.

 Passing the full path of the named pipe as the input only results in the
 error:


 {{{
 [tee @ 0x560bb7272100] Slave muxer #1 failed, aborting.
 av_interleaved_write_frame(): No such file or directory
 No more output streams to write to, finishing.
 [AVIOContext @ 0x7fb800045c00] Statistics: 0 seeks, 1 writeouts

 }}}


 Yet the file and path exists:


 {{{
 file /home/brainiarc7/test_channel
 /home/brainiarc7/test_channel: fifo (named pipe)
 }}}



 For whatever reason, FFmpeg's tee muxer cannot recognize the named pipe as
 a valid output and instead of writing into it as expected, FFmeg simply
 creates a file on the filesystem with a name matching the output name :


 {{{
 ' pipe: test_channel'
 }}}


 Is that intended behavior? And if so, why then does FFmpeg fail to treat
 it as a regular file that can be written to, as an output, when the tee
 muxer is called up?

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