POB-3119(1)

💖 POB-3119 💖

okay bestie, so this is pob-3119 from the User Command section of the manual (section 1, the classics ✨) — and no, the name isn't a typo, it's literally named after the RFC it implements. iykyk. 🎀

✨ NAME ✨

pob-3119 — receive RTP RFC 3119 MP3 streams 🎧

🌸 SYNOPSIS 🌸

pob-3119 [ -s address ] [ -p port ] [ -b size ] [ -q ]

🦋 DESCRIPTION 🦋

so what this lil icon does 👑 — pob-3119 receives an RTP MP3 stream using the protocol described in RFC 3119. fr fr, that's the whole vibe.

the incoming stream gets buffered 🧺 and then written out to standard out, specifically so you can pipe it straight into an MP3 decoder. it's giving glue code, but make it cute. 💅

💜 OPTIONS 💜

• -s address — tell it which address to listen to, bestie. default is 224.0.1.23. and here's the slay part: if that address is a multicast address, group membership gets requested automatically, no extra work from you 🫶
• -p port — pick the port to listen to. that's it. that's the option. 🌸
• -b size — sets the maximal number of packets held in the ring buffer. default is 128. like, how many lil packets are chillin' in the buffer at once, you know? 🎀
• -q — quiet mode 🍓. don't output any information on standard error. it's giving silent but deadly (to your logs). 🤫

🌈 EXAMPLES 🌈

pob-3119 -s 224.0.1.24 -p 8989 | mpg123 -

what this is doing 👇 — receiving the MP3 RTP stream sent to 224.0.1.24 on port 8989 and feeding it right into the MP3 decoder mpg123. chef's kiss, no notes. 😭🔥

👑 AUTHORS 👑

• Manuel Odendahl <manuel@bl0rg.net>
• Florian Wesch <dividuum@bl0rg.net>

absolute legends, we stan. 🫶✨

💀 heads up bestie: this page is from February 2005, so it's giving vintage. still iconic tho.

and that's the whole page!! POB-3119(1) with source/version POB-3119(1), dated February 2005 — periodt. 💅🎀💖