Russ Dizdar Ragged Edge Radio

What Ragged Edge Radio Actually Is

Russ Dizdar was a British radio industry guy who spent decades in broadcasting before moving into software. Ragged Edge Radio was his attempt to build a browser-based radio automation platform that didn't require installing heavy desktop software on your station's server. You logged in from a web interface, uploaded your audio, built playlists, set up scheduling, and it handled the streaming output. That was the pitch, anyway. I used it back around 2013-2014 when I was running a small internet station. The appeal was obvious - no more dealing with Windows Media Player crashes or SAM Broadcaster license issues on a CentOS box. Just a web panel and a stream.

Getting Started with Russ Dizdar Ragged Edge Radio

You'd sign up on their site, get credentials, and then access the management panel. The workflow was straightforward: add tracks, create shows, assign them to time slots, and hit broadcast. It handled metadata, crossfades, and generated an Icecast-compatible output stream that you could route to your distribution endpoint or let it push directly. The first thing you needed to understand was that this was a hosted service, not self-hosted software. That meant your entire station's uptime depended on their infrastructure. When it worked, it worked fine. When it didn't, you had no server to SSH into and fix things yourself.

I ran into a specific problem that took me weeks to resolve. The playlist scheduler would occasionally drift - showing times that didn't match actual broadcast time. A track scheduled for 8:00 PM would play at 8:12 PM. The root cause was that the system calculated schedule offsets using the browser's local timezone instead of normalizing everything to UTC on the server side. My workaround was to manually adjust all my show start times by the offset difference and document it in a spreadsheet I kept open while managing the station. It wasn't elegant but it kept things from getting worse. Another issue I hit was with audio file validation. The system rejected certain MP3 files that I had encoded myself - specifically those with ID3v2.4 tags. Ragged Edge's parser apparently only handled ID3v2.3 correctly. I fixed it by using MP3Tag to downgrade the tag version before uploading. Took maybe ten minutes once I figured out what was happening, but I wouldn't have found that without going through it.

How It Compared to Other Solutions

The main alternatives back then were SAM Broadcaster, RadioDJ, and Zeplin. SAM was the industry standard but expensive and Windows-only. RadioDJ was free but a desktop app with a steeper learning curve. Zeplin was also web-based and similar in concept. Ragged Edge sat somewhere in between - less polished than Zeplin in some areas, more accessible than RadioDJ for people who didn't want to manage their own software installation. The counter-intuitive thing about web-based automation is that it's actually harder to troubleshoot. When SAM Broadcaster or RadioDJ crashes on your local machine, you can see the error, restart the process, check logs. With a hosted service, you're emailing support and waiting. For a station running 24/7, that waiting period is real downtime. I learned this the hard way during a holiday weekend when their support response time was measured in days, not hours.

The Downsides Nobody Talks About

Here's the honest part: Ragged Edge Radio was never going to scale to professional broadcast standards. The audio processing was basic - you got a compressor and limiter but nothing approaching the kind of EQ and dynamics control a terrestrial station would need. If you were running a community station playing folk music at low volume levels, it was fine. If you were trying to compete loudness-wise with commercial stations, you'd be disappointed. The subscription model also meant your costs went up as your needs grew. Bandwidth, storage, number of concurrent streams - all of it added to the monthly bill. I calculated that after two years, I'd spent more on subscriptions than I would have on a decent desktop license for SAM Broadcaster plus a VPS to run it on. The convenience tax is real. There's also the vendor lock-in problem. Your playlists, your schedules, your show structures - all stored on their servers in their format. Exporting everything out was possible but not seamless. I tried migrating off at one point and spent a full day reconciling metadata that didn't match between their system and whatever I was moving to. Files were fine, but the metadata cleanup was brutal.

What I'd Recommend Instead Today

If you're starting a station now, I'd look at open-source options first. RadioDJ is still actively developed and completely free. For a more modern web-based approach, you might consider AzuraCast - it's self-hosted, runs on Docker, and gives you full control over your infrastructure. The learning curve is higher but so is your independence. The exact Russ Dizdar Ragged Edge Radio service appears to have been discontinued at some point. Dizdar himself has moved on to other projects in the radio tech space. If you're looking at it for archival reasons or because you inherited a station that was using it, the export process is your first priority before anything else. Get your data out while you still can. The broader lesson here is that any hosted radio automation service is a middleman between you and your audience. They make it convenient until they don't. Know your data, know your workflows, and always have an exit plan written down before you need it.