[FFmpeg-trac] #10565(undetermined:new): Error submitting a packet to the muxer: Broken pipe, Error muxing a packet

[FFmpeg]

#10565: Error submitting a packet to the muxer: Broken pipe, Error muxing a packet
-------------------------------------+-------------------------------------
             Reporter:  Rob          |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:  Error        |               Blocked By:
  submitting a packet to the muxer:  |
  Broken pipe, Error muxing a        |
  packet                             |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by winlin):

 This is caused by timecode of FFmpeg, SRS RTMP server fixed by
 https://github.com/ossrs/srs/issues/3803

 FFmpeg sends AMF0 data, but it doesn't begin with the AMF0 string:


 {{{

 Packet #72:
 04 00 00 64 00 00 04 12 01 00 00 00

 Packet #74:
 00 01 a5 e0

 (lldb) p *msg
 (SrsCommonMessage) $0 = {
   header = {
     timestamp_delta = 100
     payload_length = 4
     message_type = '\x12' 18 '\x12'
     stream_id = 1
     timestamp = 100
     perfer_cid = 4
   }
   size = 4
   payload = 0x0000602000003570 ""
 }
 (lldb) x/4xb msg->payload
 0x602000003570: 0x00 0x01 0xa5 0xe0
 }}}


 RTMP server should be able to handle this message by simply ignoring it:


 {{{
 [2023-09-18 11:38:45.099][WARN][91322][148t53jz][35] Ignore FFmpeg
 timecode, data=[00 01 a5 e0]
 }}}


 However, there is a workaround for this issue, to remove the `-map 0` then
 it works well:


 {{{
 ffmpeg -stream_loop -1 -re -i low2.mp4 -c copy -f flv
 rtmp://127.0.0.1:1935/<stream key>
 }}}
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/10565#comment:9>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker