You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I generated an opus stream in gstreamer and muxed it into ts: gst-launch-1.0 audiotestsrc ! opusenc ! mpegtsmux ! filesink location=out.ts.
The opus stream in this file has 160 byte packets, but when I decode it with ts-demuxer, it returns 163 byte packets, where the first 3 bytes are always the same: [127, 224, 160]. If I remove the first 3 bytes manually, the decoder can decode the stream again.
I don't have a good understanding of the ts format, so I don't why this happens. For now, I can work around this by slicing off the first three bytes, but it would be nice to have this fixed here.
The text was updated successfully, but these errors were encountered:
ebekebe
changed the title
Decoded opus packet is corrupt
Demuxed opus packet is corrupt
Mar 15, 2022
Odd. If it were two bytes, I would suspect self-delimited Opus packet headers, but I don't know why there would be three.
Do you see similar issues with any other encodings?
I generated an opus stream in gstreamer and muxed it into ts:
gst-launch-1.0 audiotestsrc ! opusenc ! mpegtsmux ! filesink location=out.ts
.The opus stream in this file has 160 byte packets, but when I decode it with ts-demuxer, it returns 163 byte packets, where the first 3 bytes are always the same:
[127, 224, 160]
. If I remove the first 3 bytes manually, the decoder can decode the stream again.I don't have a good understanding of the ts format, so I don't why this happens. For now, I can work around this by slicing off the first three bytes, but it would be nice to have this fixed here.
The text was updated successfully, but these errors were encountered: