Working on AV systems means spending time with equipment and with the people who use it. Sometimes a problem needs a wiring or configuration change. Sometimes the missing piece is a way to see what the system is doing.
That is often where I start writing software. I want a useful measurement, a clearer control, or a record that helps explain an intermittent fault.
The studio audio monitor is one example
I built a monitor to measure studio sound levels and give instructors feedback. It analyzes audio locally, updates a dashboard, and buffers measurements when the internet connection drops.
The hardware and the software affect each other. Microphone placement changes the measurement. The analysis settings change what the reading means. The interface determines whether someone can use it during a class.
In Keeping an audio dashboard responsive, I explain why dashboard updates and database writes take separate paths.
Controls need to suit everyday use
A system can have plenty of capability and still be awkward to operate. I want to know which decisions staff make every day, which settings need to stay consistent, and what information helps them recognize a fault.
That may lead to a smaller set of controls, a preset, or a status view. It may also reveal that the existing interface can do the job with a few changes.
Experiments help me test ideas
I also work on local AI tools, generative visuals, and NIGHTSHIFT in Unreal Engine. Those projects give me different problems to investigate: memory limits, animation transitions, tool arguments, and the timing of a visual response.
I keep the test results because a working demonstration does not answer every question. A model that completes one tool call may still fail on a missing argument. A visual loop may look good before it has been connected to live audio.
Explain the result clearly
For a finished change, I want to be able to explain what it does, how it was checked, and what still needs attention. Whoever operates the system should have enough information to recognize normal behavior and report a useful problem.
That is the reason I work on AV and software together. The software gives me another way to solve problems with the systems I already work on.