-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support FFmpeg timecode, fix AMF0 parsing failed. #3803
Labels
EnglishNative
This issue is conveyed exclusively in English.
Comments
Examine the pcap file, where FFmpeg sends AMF0 data, but it doesn't begin with the AMF0 string:
SRS should be able to handle this message by simply ignoring it:
|
winlinvip
added a commit
that referenced
this issue
Sep 18, 2023
…3804) Please see #3803 for detail: 1. When using FFmpeg with the `-map 0` option, there may be a 4-byte timecode in the AMF0 Data. 2. SRS should be able to handle this packet without causing a parsing error, as it's generally expected to be an AMF0 string, not a 4-byte timecode. 3. Disregard the timecode since SRS doesn't utilize it. See [Error submitting a packet to the muxer: Broken pipe, Error muxing a packet](https://trac.ffmpeg.org/ticket/10565) --------- Co-authored-by: john <hondaxiao@tencent.com>
winlinvip
added a commit
that referenced
this issue
Sep 18, 2023
Please see #3803 for detail: 1. When using FFmpeg with the `-map 0` option, there may be a 4-byte timecode in the AMF0 Data. 2. SRS should be able to handle this packet without causing a parsing error, as it's generally expected to be an AMF0 string, not a 4-byte timecode. 3. Disregard the timecode since SRS doesn't utilize it. See [Error submitting a packet to the muxer: Broken pipe, Error muxing a packet](https://trac.ffmpeg.org/ticket/10565) --------- Co-authored-by: john <hondaxiao@tencent.com>
duiniuluantanqin
pushed a commit
to duiniuluantanqin/srs
that referenced
this issue
Oct 11, 2023
Please see ossrs#3803 for detail: 1. When using FFmpeg with the `-map 0` option, there may be a 4-byte timecode in the AMF0 Data. 2. SRS should be able to handle this packet without causing a parsing error, as it's generally expected to be an AMF0 string, not a 4-byte timecode. 3. Disregard the timecode since SRS doesn't utilize it. See [Error submitting a packet to the muxer: Broken pipe, Error muxing a packet](https://trac.ffmpeg.org/ticket/10565) --------- Co-authored-by: john <hondaxiao@tencent.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See Error submitting a packet to the muxer: Broken pipe, Error muxing a packet
Test using the file timecode.mp4.zip or below:
timecode.mp4
Use this FFmpeg command:
SRS will fail with this error:
Here's the pcap file:
rtmp-amf0-invalid.pcapng.zip
The text was updated successfully, but these errors were encountered: