For decades, the standard radio station setup meant two computers: one for on-air automation, one for production. Touch the on-air machine and you risk dead air. That rule made sense in 2005. On a modern Mac, it's worth questioning.
The logic was sound, and for a long time it was correct. Early automation computers were running at the edge of their capabilities. Playing audio files, managing a schedule, and handling transitions was enough to keep a Pentium II busy. If you opened a production application on the same machine — a DAW, an audio editor, even a web browser with too many tabs — you risked dropouts, stuttering, or a full crash. And on Windows, crashes weren't rare. They were Tuesday.
So the industry adopted a rule: the on-air computer is sacred. Don't touch it. Don't install anything on it. Don't even look at it funny. If you need to record a promo, edit audio, or do anything that might consume CPU or memory, you do it on the production machine next to it.
This made perfect sense when a "powerful computer" had 512 MB of RAM and a single-core processor running at 800 MHz.
It makes a lot less sense when you're sitting in front of a Mac with an M-series chip, 16 GB of unified memory, and an operating system designed from the ground up for real-time media processing.
A modern Mac — even a Mac mini, the most modest Mac in the lineup — has more processing power than the most expensive broadcast workstations of ten years ago. Apple Silicon chips are designed for media work: hardware-accelerated audio encoding, dedicated efficiency cores for background tasks, unified memory that eliminates the bottleneck between CPU and GPU. Playing audio files while editing a separate audio project is the kind of workload these machines handle without breaking a sweat.
To put it in perspective: an M-series Mac can simultaneously play back dozens of audio tracks in a DAW, transcode video, and browse the web while its fans stay silent. Asking it to play one audio file through your automation software while you edit a promo in another application is like asking a freight train to carry a grocery bag.
Core Audio — the macOS audio subsystem — is fundamentally different from Windows audio. It's a low-latency, real-time audio framework that's been refined for over twenty years. It handles multiple audio streams from multiple applications to multiple hardware outputs simultaneously. It doesn't fight with itself over device access the way Windows audio drivers historically have.
This matters for a single-computer station because it means your automation software and your production software can use separate audio outputs on the same machine without interfering with each other. macOS routes the audio cleanly, application by application, device by device.
One of the real reasons the two-computer rule persisted on Windows was the operating system itself. Automatic updates that reboot without warning. Driver conflicts after a system update. Background processes that suddenly consume all available CPU. Blue screens of death. These weren't theoretical risks — they were things that happened to stations, on the air, in the middle of the night.
macOS doesn't force restarts for updates. It doesn't install drivers behind your back. It doesn't suddenly decide to defragment a drive while you're broadcasting. The operating system stays out of the way, which is exactly what you need from a computer that's keeping your station on the air. With a few simple optimizations, you can make it even leaner.
The key to running automation and production on the same Mac is keeping the audio paths separate. Your broadcast audio and your production audio need their own inputs and outputs so they never cross. This is easier than it sounds.
You need two things:
Many professional USB audio interfaces have four or more channels. If yours does, you can use channels 1–2 for broadcast and channels 3–4 for production — all on the same physical device. Your automation software outputs to channels 1–2. Your production software outputs to channels 3–4. The audio never crosses.
If you prefer physical separation, two small USB interfaces work just as well. A Focusrite Scarlett 2i2 for broadcast and a second one (or even the Mac's built-in headphone jack) for production monitoring. Total cost: under $200.
In macOS, every audio application lets you choose its input and output device independently. Your automation software points to the broadcast interface. Your DAW or audio editor points to the production interface (or production channels). They operate in parallel without knowing or caring about each other.
This is not a hack or a workaround. This is exactly how macOS is designed to work. Core Audio manages the routing, the buffering, and the timing for each application independently. Two apps, two audio paths, zero conflicts.
You're sitting at your desk. AutoCast is running on the left side of your screen, playing music through channels 1–2 of your audio interface, out to the transmitter. On the right side, you have your audio editor open. You're recording a promo through channels 3–4, listening on your headphones. AutoCast doesn't flinch. The audio to the transmitter is clean. The promo recording is clean. Two completely independent audio workflows on one machine.
When the promo is done, you save it and import it into your automation library. It's ready to air. You never left your chair, never switched machines, never transferred a file over the network.
A single Mac handles the workload of most small and medium stations without issue. But there are situations where two machines still make sense:
If you have DJs or producers who need to do production work while someone else is on the air, a shared computer becomes a coordination headache. Two machines let two people work independently without stepping on each other.
If your production work involves video editing, large multitrack sessions, or CPU-intensive processing that pushes even a modern Mac, a dedicated production machine keeps that load isolated. For most radio production — editing voice tracks, mixing promos, cutting interviews — this threshold is very hard to reach on Apple Silicon.
Some stations want a second machine as a hot backup. If the primary fails, the backup can take over. This is less about production capability and more about insurance. For stations that serve as emergency broadcast facilities, the redundancy argument has real merit.
If the idea of doing production on your on-air machine makes you nervous, that's a valid reason to keep them separate. Radio is a reliability business, and if two machines help you sleep at night, the extra cost is worth it. But know that the technical reasons for the separation have largely evaporated.
Going from two computers to one isn't just about simplicity. It's real money and real operational advantages for a small station:
Here's what a complete single-computer station looks like. Nothing exotic. Nothing expensive.
Total investment beyond the Mac itself: roughly $400 to $600 for the interface, mic, headphones, and UPS. Compare that to buying, configuring, and maintaining a second computer.
The two-computer rule was a sensible response to unreliable hardware and an unpredictable operating system. It kept stations on the air when the alternative was risking dead air every time someone opened the wrong application.
Modern Macs running macOS with Core Audio have eliminated the technical justification for that rule. The hardware is powerful enough. The operating system is stable enough. The audio subsystem is sophisticated enough to keep two completely independent audio workflows running in parallel without interference.
If you're a small station — especially a one-person operation where you're the engineer, the DJ, the producer, and the program director — a single Mac can do everything you need. One machine. One desk. One workflow. And the budget you would have spent on that second computer can go toward a better microphone, a better audio interface, or music licensing fees.
The two-computer rule served its time well. For most small stations running on modern Macs, it's time to let it retire.
TuneTracker System 7 is built for macOS and designed to coexist gracefully with whatever else you're running. Free version available.
Download TuneTracker FreeContinue Reading
Practical guides for broadcasters who care about their craft and their community.