Q: Have you ever noticed the amount of CPU/memory that SAM Broadcaster uses?
Users have reported that they cannot run SAM Broadcaster without the program taking up a lot of the CPU/resources.
Ever since SAM Broadcaster v2.x.x the program has always required huge amounts of the CPU/memory.
SAM Broadcaster has always been a resource hog no matter how much processing power your PC had.
More often than not SAM Broadcaster would cause the CPU to max out and freeze the PC which usually meant a restart of the computer.
SAM is a very system intensive piece of software. It requires a lot of the systems time and resources.
I saw this on a post on a forum recently.
This isn’t a problem that we seem to have with RadioDJ free radio automation software.
RadioDJ hardly uses the CPU and isn’t as memory hungry as SAM Broadcaster is known to be. Plus RadioDJ doesn’t seem to crash or freeze like SAM Broadcaster does.
RadioDJ can be ran on a system with as little as 1000 MHz CPU and 1GB RAM
The fact RadioDJ doesn’t use huge amounts of CPU/memory is just another reason why RadioDJ is far superior to SAM Broadcaster.
We’re sure Spacial Audio are well aware of SAM Broadcaster and the amount of resources it hogs.
WRONG! When SAM Broadcaster crashes it’s because the program is hogging so many of the PC’s CPU processes. It usually slams the CPU up to 100% during track changes.
RadioDJ uses about 7-10% during a track change infact as you can see from the above image it hardly uses any memory or CPU.
Every time Spacial release a new version of SAM Broadcaster it’s the same old story.
Versions 2/3/4 all hogged resources/crashed & it seems the newer versions do exactly the same.
Why do people still buy (lease) software from Spacial Audio? You’re only paying them to make worse software.
Maybe one day Spacial Audio will get their act together and give people a program that doesn’t use huge amounts of CPU & Memory…
But we won’t hold our breath on that one!
Last updated on: October 9th, 2017
at 09:18 AM Europe/London