A State of Control

A State of Control is a trade-level podcast about AV control programming, automation, and the decisions behind reliable audiovisual systems. It is technical, but not abstract. Steve Greenblatt frames each discussion around the pressures programmers and integrators meet in the field: scope, labor, client expectations, closeout, documentation, security, and long-term support. The show regularly asks what control work is worth when much of it is invisible until something fails. That gives the conversations a practical edge. Source code ownership becomes more than a contract argument. In the show's hands, it becomes a customer-service issue, a licensing issue, and a maintenance issue, especially when a higher education customer wants one code package deployed across many classrooms. Security gets similar treatment. The episodes do not glamorize it, and they do not pretend it is easy. They connect compromised credentials, contractor access, root-cause analysis, and professional responsibility to the everyday choices that happen under schedule pressure. Crestron Masters episodes add another layer, capturing how programmers use industry events for training, peer exchange, certification, and a sense of professional home. The show also tracks broader shifts in AV, including standards-based systems, API-driven interfaces, PowerShell configuration, and the enterprise IT influence on AV workflows. AI comes up as a tool, not a magic replacement. Configuration-based systems get a fair hearing too. A classroom that only needs a simple button flow may not require elaborate custom code, but the show still emphasizes that expertise sits behind the decision to keep things simple. Older episodes on code hygiene, training, certifications, and software architecture show the same concern from another angle. The recurring question is not just who can program. It is who understands the system well enough to make it dependable. The tone is conversational and occasionally blunt, with industry shorthand and lived-in examples rather than polished vendor language. For AV programmers, designers, integrators, and technical managers, it offers a useful record of how the control side of the business thinks through change. It is especially strong when the panel disagrees without losing sight of the room, the client, and the work still waiting after installation.