Remote voice tracking,
explained.

Voice tracking means a DJ records a break — intros, outros, liners, a few minutes of talk — without being live in the studio, and the system plays it back at the right moment against the real log. "Remote" just means the DJ did that recording from somewhere other than the station. Here's how stations actually do it.

Workflow 1: Email or Dropbox

The DJ records in whatever app they have, exports an MP3, and sends it over by email or a shared Dropbox folder. Someone at the station then manually drops it into the right slot in the log.

• Pros: Zero cost beyond what you already pay for storage/email. Works with literally any station.
• Cons: No access to the real log or the actual songs it plays against, so timing against the outgoing/incoming track is a guess. Someone has to manually place every file. Mistakes (wrong file, wrong slot) are common. See the full ControlForge vs email and Dropbox breakdown.

Workflow 2: A matched desktop client

Automation vendors like StationPlaylist sell a dedicated remote voice-tracking client (their Remote Voice Tracker lists at $199 for the Pro/unlimited-user edition or $129 for Standard/5 users, per stationplaylist.com). It has to match the version of the automation software running at the station, installed on every DJ's PC.

• Pros: Pulls the real log and songs, so DJs can time against the actual ramps.
• Cons: A Windows install per DJ, version-matching headaches, and no mobile/phone option advertised on the vendor's own site as of October 2026.

Workflow 3: Browser-based, from any device

Tools built this way (ControlForge, and AirForge's built-in voice tracking) run entirely in a browser. The DJ logs in, sees only their scheduled hours, hears the real outgoing and incoming track, and records with on-screen waveform, mic meter, trim and normalize — from a laptop, or a phone's own browser, nothing installed.

• Pros: No install, no version matching, works from a phone. Uploads typically resume automatically if a DJ's home connection drops mid-upload.
• Cons: You're trusting a cloud tool with your log and audio; check how it integrates with your specific automation before switching.

Gear a DJ actually needs

• A USB microphone (a basic cardioid condenser is plenty to start)
• Closed-back headphones, so the mic doesn't pick up playback
• A reasonably quiet room — a closet full of clothes is a legitimately good vocal booth
• A stable-enough internet connection for upload; look for a tool that resumes uploads automatically rather than losing the take

Which workflow fits your station

Pure hobby stations with nobody live: email/Dropbox is fine, slowly. Stations already running StationPlaylist who only need basic remote tracking: the matched client works, budget for the per-seat cost. Stations that want DJs recording from phones, want guests or an AI DJ for unclaimed hours, or just don't want to manage Windows installs per DJ: a browser-based tool like ControlForge or AirForge is built for exactly that.