<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Broadcast on Matt Thomas</title><link>https://matt-thomas.work/tags/broadcast/</link><description>Recent content in Broadcast on Matt Thomas</description><generator>Hugo -- 0.154.4</generator><language>en-gb</language><lastBuildDate>Thu, 16 Apr 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://matt-thomas.work/tags/broadcast/index.xml" rel="self" type="application/rss+xml"/><item><title>The Emerging DevOps Role in Broadcast Engineering</title><link>https://matt-thomas.work/posts/devops-broadcast-engineering/</link><pubDate>Thu, 16 Apr 2026 09:00:00 +0000</pubDate><guid>https://matt-thomas.work/posts/devops-broadcast-engineering/</guid><description>Broadcast infrastructure is becoming software. The practices that the software industry developed for managing that complexity - DevOps - are increasingly relevant to broadcast engineers. Not as a job title to chase, but as a set of disciplines that make complex, software-defined broadcast systems more reliable and maintainable.</description></item><item><title>Dolby E - Why It Still Matters in Broadcast Contribution</title><link>https://matt-thomas.work/posts/dolby-e-broadcast/</link><pubDate>Mon, 30 Mar 2026 02:00:00 +0000</pubDate><guid>https://matt-thomas.work/posts/dolby-e-broadcast/</guid><description>Dolby E has been part of broadcast audio infrastructure for over two decades. Despite the move toward IP and immersive audio, it remains deeply embedded in contribution and distribution chains - and understanding it is still essential for broadcast engineers.</description></item></channel></rss>