Skip to content

Latest commit

 

History

History
44 lines (24 loc) · 1.02 KB

ffrewrite.md

File metadata and controls

44 lines (24 loc) · 1.02 KB

Ffmpeg rewriting SCTE-35 packets.

As of 2.4.55, threefive can parse the packet either way.

I love you msnbc, (please don't get mad at me for using your SCTE-35)


Let me preface this by saying this is not a criticism of ffmpeg.
In my experience, ffmpeg tends to do things the correct way,
and I have no problem adapting to them.

My goal is to keep threefive as flexible and compatible as possible.

This is what I usually get for SCTE-35 packets.

  • four byte header
  • \x00
  • SCTE-35 Cue
  • padding to 188 bytes

image

ffmpeg -copyts -i msnbc-latest.ts -map 0 -c copy msnbc-latest-ffmpeg.ts

Now ffmpeg changes that packet to look like this.

  • four byte header + AFC
  • padding to 188 bytes
  • PES header
  • SCTE-35 Cue

image

As of 2.4.55, threefive can parse the packet either way.