TS_PACKET_INSERT(1)

πŸ’– NAME πŸ’–

ts_packet_insert β€” bestie, this one inserts TS packets into a Transport Stream. That's the whole vibe. No cap.


✨ SYNOPSIS ✨

ts_packet_insert [-err stdout] [-err stderr] [-p positions]
                 [-pid pid_no] [-s -string] [-o out_file] in_file

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so real talk: ts_packet_insert drops TS packets into a Transport Stream, and it puts them exactly wherever you tell it to. You're the main character, you pick the spots. πŸ’…

🌸 Input 🌸

  • in_file β€” an H.222 Transport Stream file. That's your source, your starting point, your origin story. Hand it over. 🫢

πŸŽ€ Switches πŸŽ€

  • -err stdout β€” sends error messages to standard output. This is literally the default, so if you do nothing, this is what you get. ✨
  • -err stderr β€” sends error messages to standard error instead. This is the Unix traditional way, iykyk. πŸ‘‘
  • -p positions β€” this is a colon (:) delimited string of numbers, and every number sits between 0 and 1. Each one says how far through the file to put a TS packet. So like, -p 0.1:0.4:0.7:0.9 will insert 4 packets at 10%, 40%, 70% and 90% through the file. Four positions, four packets, math is mathing. πŸ”₯
  • -pid pid_no β€” the inserted packets get the PID you specify. [default = 0x68] πŸ“
  • -s string β€” the inserted packets carry string as their payload. [default = 'Inserted packet'] 🌈
  • -o out_file β€” the brand new TS file gets written out under the name you give it. [default = out.ts] πŸ’–

⭐ EXAMPLES ⭐

Like, here's the moment you've been waiting for:

ts_packet_insert -p 0.3:0.6 -o out.ts -pid 89 -s "AD=start" in.ts

πŸ‘‘ SEE ALSO πŸ‘‘

esdots(1)


πŸ’€ quick vibe check: that SYNOPSIS line says -s -string, not -s string. Not me trying to fix it, I'm just saying β€” type it exactly like it's written, bestie. πŸ™ˆ

Okay that's the whole page, mwah πŸ’‹ β€” this one's from the Debian crew, dated October 28, 2015, and it lives in the General Commands Manual section. Slay. πŸŽ€βœ¨