Pierrick Philippe

IP-Based Broadcasting As broadcasting continues its shift toward IP and software-defined infrastructures, operational visibility is becoming more complex — and more important. Traditional monitoring approaches that worked well in baseband environments are no longer sufficient for modern broadcast systems. In conventional broadcast facilities, signal paths were largely deterministic. Engineers could trace faults through defined hardware routes, and system behaviour was relatively predictable. IP-based environments introduce a different reality. Video, audio, and data now travel across shared network infrastructure alongside multiple services and protocols. Packet loss, latency variations, timing drift, and software interactions can influence broadcast quality in ways that are not always immediately visible. This is where observability becomes critical. Monitoring typically answers the question: Is the system working? Observability goes further by helping teams understand why something is happening within the system. In IP broadcasting, this means visibility into network performance, packet behaviour, timing synchronization, system logs, and application-level metrics. When these insights are integrated effectively, engineers can detect anomalies early and resolve issues before they affect live transmission. For executives, observability supports operational confidence. Reliable insights enable better decision-making, reduce downtime risk, and strengthen accountability across technical teams. For engineers, it provides the context needed to troubleshoot complex systems where problems may not originate from a single device but from interactions across multiple layers. The transition from monitoring to observability reflects a broader shift in broadcast operations. As infrastructures become more distributed and software-driven, understanding system behaviour becomes just as important as maintaining equipment. IP broadcasting offers remarkable flexibility and scalability. But without strong operational visibility, complexity can easily outpace control. The organisations that succeed in this new environment will be those that invest not only in infrastructure — but also in the tools and practices that make that infrastructure understandable. — Broadcast Technology Executive | Satellite, IP & OB Systems © OWASPACE | Original Content #OWASPACE #OWASPACEBroadcast #OWASPACEInsights #IPBroadcasting #BroadcastMonitoring #Observability #MediaTechnology #BroadcastEngineering

9

🚀 Introducing NMOS Scout We’re happy to launch NMOS Scout — a lightweight engineering tool for discovering, registering, and routing NMOS streams. 🎯 What it is NMOS Scout is designed for engineers, system integrators, operators, and broadcasters who need a simple, practical way to work with NMOS networks — without deploying a full control system. 🔎 What it does Scan — discover NMOS devices, senders, and receivers Register — populate and maintain NMOS registries (IS-04) Mini Routers — build custom logical mini routers (IS-05) Northbound Control — expose mini routers via Ember+, SW-P08, TSL Cross-Platform — runs on Windows, macOS, and even Raspberry Pi via a web browser ✅ Why it matters Bridges the gap before full broadcast control systems Simplifies validation during commissioning Integrates seamlessly with legacy workflows Cost-effective and simple to use — even runs on a Raspberry Pi ⚠️ Important: NMOS Scout is a tool for engineers — not a broadcast control system. 👉 Developed by Teunkey Broadcast Consultants — bridging the gap between NMOS and real-world operations. #NMOS #BroadcastTech #IPBroadcast #EngineeringTools

162

41 commentaires

𝗕𝗶𝗴 𝗡𝗲𝘄𝘀: 𝗣𝗮𝘁𝗰𝗵𝗔𝗺𝗽’𝘀 𝗙𝗿𝗮𝗺𝗲 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝗦𝘆𝘀𝘁𝗲𝗺 (𝗥𝗠𝗦) 𝗶𝘀 𝗻𝗼𝘄 𝗶𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗲𝗱 𝗶𝗻𝘁𝗼 𝗦𝗸𝘆𝗹𝗶𝗻𝗲 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀’ 𝗗𝗮𝘁𝗮𝗠𝗶𝗻𝗲𝗿 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺. What does this mean for broadcasters and engineers? ✅ Real-time visibility across coax & fiber signals ✅ Custom dashboards + SNMP alarms ✅ Faster diagnostics with card-level insights This collaboration makes signal health easier to track, troubleshoot, and automate—without adding complexity. The PatchAmp Frame Monitor connector is live in the DataMiner Catalog today. 👉Read the full press release here: https://lnkd.in/ebPZbVy4 #PatchAmp #DataMiner #Broadcasting #Monitoring #SkylineCommunications

44

1 commentaire

⏱️ 𝗣𝗧𝗣 𝗶𝗻 𝗦𝗠𝗣𝗧𝗘 𝟮𝟭𝟭𝟬: 𝗧𝗵𝗲 𝗖𝗹𝗼𝗰𝗸 𝗧𝗵𝗮𝘁 𝗧𝗶𝗰𝗸𝘀 𝗪𝗶𝘁𝗵 𝗖𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆 🎥 Think black burst was tricky? Welcome to PTP — the deceptively elegant but technically ruthless backbone of ST 2110 synchronization. As we shift from SDI to IP-based production using SMPTE ST 2110, one of the most critical — and complex — foundations is synchronization via Precision Time Protocol (PTP), defined by IEEE 1588-2008 (v2). 𝗕𝘂𝘁 𝗵𝗲𝗿𝗲’𝘀 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹𝗶𝘁𝘆: ✅ PTP enables precise, frame-accurate sync across distributed IP devices. ❌ But implementing it at scale, with reliability, is no small feat. 𝗛𝗲𝗿𝗲’𝘀 𝘄𝗵𝗮𝘁 𝗺𝗮𝗸𝗲𝘀 𝗣𝗧𝗣 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗶𝗻 𝗦𝗧 𝟮𝟭𝟭𝟬 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀 𝗵𝗮𝗿𝗱𝗰𝗼𝗿𝗲: 🔍 𝟭. 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗗𝗲𝘀𝗶𝗴𝗻 ≠ 𝗦𝘄𝗶𝘁𝗰𝗵 𝗦𝗽𝗲𝗰𝘀 It’s not enough to check “PTP support” on a datasheet. Poorly implemented Boundary or Transparent Clocks introduce timing asymmetry, delay variation, and jitter — corrupting every downstream node. 📡 2. 𝗚𝗿𝗮𝗻𝗱𝗺𝗮𝘀𝘁𝗲𝗿 𝗥𝗲𝗱𝘂𝗻𝗱𝗮𝗻𝗰𝘆 𝗖𝗮𝗻 𝗕𝗲 𝗗𝗮𝗻𝗴𝗲𝗿𝗼𝘂𝘀 Failover sounds good on paper — until you see BMCA chaos in live environments. Clock handoffs can introduce phase jumps or holdovers if slave devices don’t re-sync correctly.  Redundancy ≠ Resiliency without tight configuration. 📶 3. 𝗠𝘂𝗹𝘁𝗶𝗰𝗮𝘀𝘁 𝗙𝗹𝗼𝗼𝗱𝘀 & 𝗗𝗼𝗺𝗮𝗶𝗻 𝗕𝗹𝗲𝗲𝗱 PTP uses Layer 2 multicast. One misconfigured switch or overlapping PTP domain, and suddenly your audio breaks up, your video frames stutter, and you’re blind to the root cause — until it’s too late. ⏳ 4. 𝗔𝘀𝘆𝗺𝗺𝗲𝘁𝗿𝘆: 𝗧𝗵𝗲 𝗦𝗶𝗹𝗲𝗻𝘁 𝗞𝗶𝗹𝗹𝗲𝗿 Asymmetric link delays between PTP master and slave? Good luck maintaining precise offsets. In PTP, nanoseconds of asymmetry = misaligned SDI-timed frames in an IP world. 📊 5. 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝗜𝘀 𝗡𝗼𝘁 𝗢𝗽𝘁𝗶𝗼𝗻𝗮𝗹 Tri-level sync was dumb and predictable. PTP is smart — but opaque. Without tools that decode Announce, Sync, Follow_Up, Delay_Req/Resp, and logMessageInterval trends, you’re flying blind. PTP deserves full telemetry. 🎯 𝗟𝗲𝘀𝘀𝗼𝗻 𝗳𝗿𝗼𝗺 𝘁𝗵𝗲 𝗳𝗶𝗲𝗹𝗱: PTP isn’t about time — it’s about control. Without precise time alignment, your entire ST 2110 pipeline — video, audio, ANC — loses coherence. No timing, no transport. PTP in 2110 isn’t “set it and forget it.” It’s a living, breathing timing architecture. And when it breaks, everything breaks — silently and deeply. #BroadcastEngineering #SMPTEST2110 #PTP #NMOS #IS04 #IS05 #MediaOverIP #AVOverIP #NetworkedMedia #IPBroadcast #RemoteProduction #PrecisionTimeProtocol #IEEE1588 #MediaOverIP #IPBroadcast #TimingMatters #LiveProduction #ST2110Sync #BroadcastTech #TimeIsEverything #NMOS #NetworkDesign #AudioVideoSync

219

17 commentaires

ATSC (B2X) Multicast Broadcast Neutral-Host O-RAN System Architecture First paper to be published IBC 2025 https://lnkd.in/eRyCBMza ABSTRACT ATSC 3.0 is the most advanced digital broadcast standard. This paper introduces Broadcast-to-Everything (B2X), a new physical layer Radio Access Network (RAN) standard being developed by ATSC. B2X enables multiple users to share multiple radio frequency (RF) carriers in various IMT and broadcast bands (ranging from 5 MHz to 50 MHz). B2X is optimized for battery-powered devices. B2X builds on ATSC 3.0's Layer 1 (L1) and Layer 2 (L2) protocols where applicable and includes new L1/L2 control signalling. It operates within a Neutral-Host shared Open RAN (O-RAN) system, supporting a variety of services such as wearables, IoT, and Smart City applications with flexible Fast Fourier Transform (FFT) sizes of 128, 256, 512, and 1024. To ensure reliable and scalable performance, Orthogonal Frequency Division Multiple Access (OFDMA) is used, breaking the physical layer into Physical Resource Blocks (PRBs), each containing 24 subcarriers spaced 3 kHz apart. A scheduler allocates PRBs based on service needs, with Virtual Bandwidth Parts (VBP) assigned to each application. B2X is designed for efficient multicast and broadcast with carrier aggregation to increase capacity. It enhances mobile performance using intelligent Single Frequency Network (SFN) topologies, allowing content delivery over a wide-area SFN or cloud-based edge networks. For 5G/6G interworking and traffic offloading, B2X uses the O-RAN F1 interface to encapsulate the 5G/6G-PDCP (Packet Data Convergence Protocol) layer 2. The data is transmitted via B2X baseband over O-RAN fronthaul to SFN transmitter sites for emission. Dual-connected user equipment (UE/UBE (User Broadcast Equipment)) retrieves and passes the PDCP layer 2 to the 5G/6G UE PDCP buffer, completing the offload process.

45

Check out page 14, for news from SES Satellites about DVB-NIP, join us at #DVBWorld on 17 March 2026, for more insights

10

Just An Overview 📡 SRT Feeds: Powering the Shift to IP-Native Broadcast Production. The broadcast industry is rapidly moving away from hardware-heavy, location-bound workflows toward distributed, IP and cloud-based production models. At the center of this transition is SRT (Secure Reliable Transport) — now becoming the standard protocol for professional video contribution over the public internet. An SRT feed allows broadcasters to deliver high-bitrate, low-latency, and secure live video across unpredictable networks, making reliable contribution possible without satellite trucks or dedicated fiber. 🔧 Why SRT is transforming broadcast contribution. • Packet loss recovery ensures stable transmission on unstable networks. • Adaptive latency & jitter control maintain real-time performance. • AES encryption secures professional contribution feeds. • UDP-based transport optimized for live video delivery. • NAT & firewall friendly for remote and cloud workflows. • Significantly reduces infrastructure and transmission costs. 🎥 Where SRT is redefining workflows today. ✅ Live sports contribution & remote production. ✅ News gathering via bonded cellular networks. ✅ Multi-location studio production. ✅ Cloud-based playout & OTT workflows. ✅ Global event coverage without OB deployment. 📈 Industry evolution in transport. Satellite & SDI → Dedicated IP Fiber → Internet + SRT → Cloud-native production The future of broadcast is flexible, distributed, and IP-driven — and SRT is emerging as the protocol making this transition operationally and commercially viable. The real competitive advantage now lies in how efficiently broadcasters can move live video across networks. #BroadcastTechnology #SRT #IPBroadcast #LiveProduction #RemoteProduction #CloudProduction #OTT #SportsBroadcast #MediaTechnology #BroadcastEngineering

141

7 commentaires

Why do we write “dB” and not “db”? I usually don’t write about RF because it’s not a domain I’m deeply involved in, but I’ve read enough documents to notice something that bothers me a little: the use of “db” instead of “dB” when referring to decibels. While this might be a case of oversight or speed typing, it shouldn’t be. The correct form is dB, and understanding why we write it that way is a subtle test of whether someone merely works with RF equipment or truly understands what’s going on under the hood. To me, the basics and the history matter. They provide context, and that context helps build a deeper understanding of any domain, RF included. You don’t need to solve Maxwell’s equations using the Method of Moments (with the option to use Fortran77 or MATLAB 🤦🏻‍♂️), but knowing who Faraday and Maxwell were and what they contributed is, in my view, essential. So why do we write dB? Because the “B” stands for Bell, as in Alexander Graham Bell, in whose honor the bel was named. The lowercase “d” stands for deci, since we typically use one-tenth of a bel to describe gain or loss. Just like we use V for volts (after Alessandro Volta), A for amps (after André-Marie Ampère), or Hz for hertz (after Heinrich Hertz), the capital B preserves the legacy of Bell. Next time I see “db” in an RF document referring to decibels, I’ll probably call it out, but what do you think? Should we continue to honor these scientists, and follow the SI (Système International d’Unités) convention that symbols named after people are capitalized, in how we write engineering units? Or does that no longer matter?

49

10 commentaires

Interested in codecs? In an article in Radio World's latest ebook, Jacob Daniluck of Tieline explains the benefits of NMOS and Ember+ and how these protocols can be used to manage and monitor codec functions and AES67, ST 2110-30 and ST 2022-7 IP streams. Find it here: https://lnkd.in/ePcXPjhn

4

Ever wondered why your pcap traces are full of IGMP messages ?! That’s not a bug. It’s an advanced and often underrated feature of IGMPv3 called "proxy reporting and report suppression" Multicast networks can generate a flood of IGMP messages, especially when thousands of hosts are constantly joining and leaving groups. That’s where network switches come to the rescue! In this short clip from our full course, we break down the magic behind proxy report suppression and how switches step in to relieve the router from the heavy lifting. ✔ Learn how switches impersonate routers ✔ Understand the logic behind group-specific queries ✔ See what it really looks like in Wireshark 🎥 Watch the sample video to get a sneak peek into our full IGMPv3 course. at the Ateme Institute of Technology 💡 It's hands-on, crystal clear, and made for streaming engineers who want to master multicast. #StreamingTech #videostreaming #Multicast #IGMP #NetworkEngineering #AtemeInstitute #ccna #ccnp #ccie

19

2 commentaires

🚀 𝗘𝗹𝗲𝘃𝗮𝘁𝗲 𝗬𝗼𝘂𝗿 𝗦𝘁𝗿𝗲𝗮𝗺𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗦𝘁𝗿𝗲𝗮𝗺𝗩𝗫 𝘃𝘅𝗙𝗹𝗲𝘅 – 𝗧𝗵𝗲 𝗨𝗹𝘁𝗶𝗺𝗮𝘁𝗲 𝗦𝗥𝗧 𝗚𝗮𝘁𝗲𝘄𝗮𝘆 In the dynamic world of broadcasting and streaming, high-quality, high-bandwidth video transmission over any network is essential. Meet the StreamVX 𝘃𝘅𝗙𝗹𝗲𝘅 𝗦𝗥𝗧 𝗚𝗮𝘁𝗲𝘄𝗮𝘆, the most flexible and easy-to-use SRT Gateway, designed to deliver secure, low-latency video transport with unmatched performance. ✨ 𝗞𝗲𝘆 𝗙𝗲𝗮𝘁𝘂𝗿𝗲𝘀: • 𝗦𝗥𝗧 𝗚𝗮𝘁𝗲𝘄𝗮𝘆 𝗯𝘆 𝗦𝘁𝗿𝗲𝗮𝗺𝗩𝗫: Built on the innovative vxOS architecture, vxFlex ensures robust, secure video delivery with full support for ISDB-T 204-byte packets as well as DVB network, optimized for digital broadcasting standards. • 𝗩𝗲𝗿𝘀𝗮𝘁𝗶𝗹𝗲 𝗖𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗮𝘁𝗶𝗼𝗻𝘀: Supports any setup possible, from one-to-one to one-to-many scenarios, enabling seamless workflows for live contribution and multi-channel ecosystems. • 𝗦𝗰𝗮𝗹𝗮𝗯𝗹𝗲 𝗮𝗻𝗱 𝗙𝘂𝘁𝘂𝗿𝗲-𝗣𝗿𝗼𝗼𝗳: Easily extend from small-scale deployments to large, complex systems, including single-channel receivers, to meet growing demands without compromising quality. • 𝗘𝗳𝗳𝗼𝗿𝘁𝗹𝗲𝘀𝘀 𝗦𝗲𝘁𝘂𝗽: Configure with a few easy clicks through an intuitive dashboard, simplifying complex SRT workflows for all users. • 𝗢𝗻𝗲-𝗖𝗹𝗶𝗰𝗸 𝗘𝗻𝗰𝗿𝘆𝗽𝘁𝗶𝗼𝗻: Enable encryption with one click to ensure secure, protected streams across diverse networks. • 𝗦𝗲𝗮𝗺𝗹𝗲𝘀𝘀 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻: Fully compatible with StreamVX Flex appliance, Wellav CMP, Sencore OmniHUB 𝗔𝘀 𝗮 𝗽𝗿𝗼𝘂𝗱 𝗺𝗲𝗺𝗯𝗲𝗿 𝗼𝗳 𝘁𝗵𝗲 𝗦𝗥𝗧 𝗔𝗹𝗹𝗶𝗮𝗻𝗰𝗲, StreamVX is dedicated to advancing low-latency, secure video transport. Ready to transform your streaming infrastructure? 👉 𝗖𝗼𝗻𝘁𝗮𝗰𝘁 𝗦𝘁𝗿𝗲𝗮𝗺𝗩𝗫 𝘁𝗼 𝗲𝘅𝗽𝗹𝗼𝗿𝗲 𝗵𝗼𝘄 𝘃𝘅𝗙𝗹𝗲𝘅 𝗰𝗮𝗻 𝗽𝗼𝘄𝗲𝗿 𝘆𝗼𝘂𝗿 𝗻𝗲𝘅𝘁 𝗽𝗿𝗼𝗷𝗲𝗰𝘁! #SRTGateway #BroadcastTechnology #StreamVX #LowLatencyStreaming #DigitalTransformation

12

I am not in Amsterdam this week but even from a distance the momentum of IBC - International Broadcasting Convention ’s second day is hard to miss. Emerging themes are loud and clear. AI powered personalization and metadata enrichment are reshaping broadcast workflows. Cloud native gateways and smarter delivery networks are pushing IP production and distribution into new territory. Dynamic HDR conversion and 5G over broadcast experiments hint at more flexible higher quality viewing experiences. Studio robotics and automation are showing how leaner teams can do more without sacrificing quality. Beyond the show floor real time voice technology and advanced dubbing platforms are maturing quickly. Captions to dubbing pipelines accent nuance controls and fair compensation frameworks for talent are changing how localization will be done at scale. Behind the scenes asset intelligence tools are quietly making inventory licensing and maintenance smarter which are critical foundations for any studio or integrator preparing to scale. For broadcasters and dubbing studios in Africa these are not distant curiosities. They are signals pointing to where audiences workflows and cost structures are heading. What signals are you watching most closely as IBC continues? #IBC2025 #BroadcastTech #MediaInnovation #AIInMedia #Dubbing #WorkflowEngineering #AfricanMedia

6

𝐌𝐨𝐬𝐭 𝐛𝐫𝐨𝐚𝐝𝐜𝐚𝐬𝐭𝐞𝐫𝐬 𝐢𝐧 𝐭𝐡𝐞 𝐫𝐞𝐠𝐢𝐨𝐧 𝐚𝐫𝐞 𝐬𝐭𝐢𝐥𝐥 𝐒𝐃𝐈-𝐛𝐚𝐬𝐞𝐝. ST 2110 is not just a technology upgrade — it’s a shift in how broadcast systems operate. When the transition comes, the real challenge won’t be cabling or standards. It will be architecture thinking. Many broadcasters are still chasing 4K or 8K SDI deployments for live events. Higher resolution is exciting, but it’s incremental. ST 2110 is transformational — it changes how broadcast systems operate, not just what they display. SMPTE ST 2110 (defined by SMPTE) is not a cable replacement. It’s an operating model shift. From deterministic, point-to-point signal paths to shared, time-dependent network architecture. In SDI, failures are local. In ST 2110, failures are systemic. Timing becomes infrastructure. PTP stability defines your plant reliability. Traffic shaping (2110-21) determines whether your network breathes or collapses. Multicast discipline replaces cable certainty. And orchestration via AMWA NMOS? It gives visibility — not resilience. The uncomfortable truth: Most ST 2110 deployments don’t fail because of the standard. They fail because architecture thinking didn’t evolve. ST 2110 doesn’t simplify broadcast. It exposes weak system design.

8

2 commentaires

"EMLAB MULTI-COVERAGE: Precision Broadcast Network Planning." EMLAB MULTI-COVERAGE delivers advanced tools for accurate design and optimization of MFN and SFN broadcast networks—both analog and digital. Key Capabilities: + Real-time analysis of coverage and interference + Detection of synchronization issues in SFN deployments + Centralized management of grouped antenna systems + Easy configuration of SFN parameters including synchronization, modulation, code rate, guard interval, and TX delay + Full compliance with ITU and ETSI standards + Comprehensive reporting features, including Google Earth/Maps export and detailed population coverage analysis + Drive smarter broadcast decisions with powerful planning tools and clear, data-backed visualizations. A marvel from: ALDENA Telecomunicazioni SRL #8btsicorp #broadcasting #broadcastsales #broadcastengineering #broadcastsolutions

15

New MOQT draft has been published: https://lnkd.in/eg4hC8F6 𝗕𝗶𝗴𝗴𝗲𝘀𝘁 𝗽𝗿𝗼𝘁𝗼𝗰𝗼𝗹/𝗰𝗼𝗻𝘁𝗿𝗼𝗹-𝗽𝗹𝗮𝗻𝗲 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 ● 𝗖𝗼𝗻𝘁𝗿𝗼𝗹 𝗽𝗹𝗮𝗻𝗲 𝘀𝘁𝗿𝗲𝗮𝗺𝘀 𝗰𝗵𝗮𝗻𝗴𝗲𝗱: the spec moves from a single bidirectional control stream to a pair of unidirectional control streams (one per endpoint) ● 𝗛𝗮𝗻𝗱𝘀𝗵𝗮𝗸𝗲 𝘀𝗶𝗺𝗽𝗹𝗶𝗳𝗶𝗲𝗱: CLIENT_SETUP / SERVER_SETUP are collapsed into a single SETUP message ● 𝗦𝗲𝘁𝘂𝗽 𝗣𝗮𝗿𝗮𝗺𝗲𝘁𝗲𝗿𝘀 -> 𝗦𝗲𝘁𝘂𝗽 𝗢𝗽𝘁𝗶𝗼𝗻𝘀: 𝗦𝗘𝗧𝗨𝗣 contents are now defined as Setup Options (KV-pairs), with a stable namespace across versions ● 𝗥𝗲𝗾𝘂𝗲𝘀𝘁𝘀 𝗻𝗼𝘄 𝗹𝗶𝘃𝗲 𝗼𝗻 𝗯𝗶𝗱𝗶𝗿𝗲𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝘀𝘁𝗿𝗲𝗮𝗺𝘀: requests are moved to bidi request streams, and the old explicit cancel messages are removed (replaced by request cancellation + STOP_SENDING patterns) ● 𝗖𝗼𝗿𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻/𝗼𝗿𝗱𝗲𝗿𝗶𝗻𝗴 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 𝘃𝗶𝗮 𝗥𝗲𝗾𝘂𝗶𝗿𝗲𝗱 𝗥𝗲𝗾𝘂𝗲𝘀𝘁 𝗜𝗗: allowing a request to declare a dependency on an earlier one 𝗙𝗹𝗼𝘄 𝗰𝗼𝗻𝘁𝗿𝗼𝗹 & 𝘀𝗵𝘂𝘁𝗱𝗼𝘄𝗻 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 ● 𝗠𝗔𝗫_𝗥𝗘𝗤𝗨𝗘𝗦𝗧_𝗜𝗗 / 𝗥𝗘𝗤𝗨𝗘𝗦𝗧𝗦_𝗕𝗟𝗢𝗖𝗞𝗘𝗗 𝗿𝗲𝗺𝗼𝘃𝗲𝗱 ● 𝗚𝗢𝗔𝗪𝗔𝗬 𝗴𝗮𝗶𝗻𝘀 𝗮 𝗧𝗶𝗺𝗲𝗼𝘂𝘁 field (for graceful close before GOAWAY_TIMEOUT) 𝗘𝗻𝗰𝗼𝗱𝗶𝗻𝗴 & 𝗽𝗮𝗿𝗮𝗺𝗲𝘁𝗲𝗿 𝗵𝗮𝗻𝗱𝗹𝗶𝗻𝗴 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 ● 𝗡𝗲𝘄 𝘃𝗮𝗿𝗶𝗮𝗯𝗹𝗲-𝗹𝗲𝗻𝗴𝘁𝗵 𝗶𝗻𝘁𝗲𝗴𝗲𝗿 𝗲𝗻𝗰𝗼𝗱𝗶𝗻𝗴 (you’ll see lots of fields switch to vi64), and Message Parameters are encoded as Type/Value (with Type Delta) ● 𝗧𝗶𝗴𝗵𝘁𝗲𝗻𝗲𝗱 𝗿𝘂𝗹𝗲: unknown Message Parameters are a session error, while unknown Setup Options are ignored "𝗘𝘅𝘁𝗲𝗻𝘀𝗶𝗼𝗻 𝗛𝗲𝗮𝗱𝗲𝗿𝘀" 𝗿𝗲𝗻𝗮𝗺𝗲𝗱 𝘁𝗼 "𝗣𝗿𝗼𝗽𝗲𝗿𝘁𝗶𝗲𝘀" ● 𝗧𝗲𝗿𝗺𝗶𝗻𝗼𝗹𝗼𝗴𝘆 + 𝗯𝗶𝘁𝘀/𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝘀 𝘂𝗽𝗱𝗮𝘁𝗲𝗱: "Extension Headers" become Object/Track Properties, including the datagram header bit rename ● 𝗖𝗹𝗮𝗿𝗶𝗳𝗶𝗲𝘀 𝗺𝘂𝘁𝗮𝗯𝗹𝗲 𝘃𝘀 𝗶𝗺𝗺𝘂𝘁𝗮𝗯𝗹𝗲 𝗽𝗿𝗼𝗽𝗲𝗿𝘁𝗶𝗲𝘀 (properties can appear either in the mutable list or inside Immutable Properties), plus preservation rules 𝗡𝗲𝘄 𝗸𝗻𝗼𝗯𝘀 / 𝗺𝗲𝘀𝘀𝗮𝗴𝗲𝘀 / 𝗲𝗿𝗿𝗼𝗿 𝗰𝗼𝗱𝗲𝘀 ● 𝗔𝗱𝗱𝘀: RENDEZVOUS_TIMEOUT (SUBSCRIBE), PUBLISH_BLOCKED (SUBSCRIBE_NAMESPACE flow control), GREASE reservations, plus several new error/reset codes (e.g., GOING_AWAY, EXCESSIVE_LOAD, NAMESPACE_TOO_LARGE, TOO_FAR_BEHIND) ● 𝗔𝘂𝘁𝗵 𝘁𝗼𝗸𝗲𝗻 𝗰𝗮𝗰𝗵𝗲 𝗯𝗲𝗵𝗮𝘃𝗶𝗼𝗿 𝗶𝘀 𝗰𝗹𝗮𝗿𝗶𝗳𝗶𝗲𝗱 𝗳𝗼𝗿 𝗺𝘂𝗹𝘁𝗶-𝘀𝘁𝗿𝗲𝗮𝗺 𝗿𝗲𝗮𝗹𝗶𝘁𝗶𝗲𝘀 also SETUP auth-token overflow handling is softened (treat as USE_VALUE rather than failing SETUP) Worth noting: 𝗱𝗿𝗮𝗳𝘁-𝟭𝟳 𝗶𝘀𝗻’𝘁 𝗿𝗲𝗮𝗹𝗹𝘆 𝗮 𝘁𝗮𝗿𝗴𝗲𝘁 𝗳𝗼𝗿 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻, focus is to catch up to 𝗱𝗿𝗮𝗳𝘁-𝟭𝟲, then wait for 𝗱𝗿𝗮𝗳𝘁-𝟭𝟴 for 𝗶𝗻𝘁𝗲𝗿𝗼𝗽 𝘁𝗲𝘀𝘁𝗶𝗻𝗴.

57

Multicast networks — those digital channels in-between major broadcast networks on the dial — are becoming a bigger part of overall TV viewership, especially among households that use an antenna. https://lnkd.in/gqziECXR

23

1 commentaire

Why GPU‑Accelerated DVNR Is a Game Changer for Broadcasters In today’s fast-paced broadcast environment, delivering crystal-clear video is non-negotiable. Noise not only compromises visual quality, but also hinders compression efficiency—driving up distribution costs. That’s why Wavelet Beam’s GPU‑based DVNR solution, powered by CUDA and scalable HPC architecture, is so vital. It effectively removes noise without sacrificing detail, ensuring both live feeds and archived footage look their best. * Sharper picture quality * More efficient encoding = lower bitrates & costs * Scales to high‑volume workflows with ease For broadcasters and post-production teams operating at scale, this tech offers a tangible boost to output quality and system performance. Ready to optimize your workflow? Learn more at waveletbeam.com. #Broadcast #DVNR #GPU #CUDA #VideoQuality #BitrateOptimization #UHD #HDR #PostProduction

4

Beyond the Engineer's Office: APIs and the Expanding Language of Broadcast Insight... Click to view article ! https://lnkd.in/eY6YZb4t Simen K. Frostad Bridge Technologies Tim Langridge Gry Synnøve Bakkeli Kaldager Fiorenza Mella #broadcast #broadcasters #QoE #QoS #media #monitoring #adinsertion #api #broadcastmonitoring #SCTE ® (the Society for Broadband Professionals) #broadcastanalytics #ott #mediamonitoring #broadcastquality

18

3 commentaires