For a little while, the CommunityFM (to-air) radio station I was in charge of, ran its entire system with 3 raspberry Pi B2's. They were running our own very-hybridised System D linux. There was a thin client in the studio which acted like a control module for the "real" computer ( another Pi ) at the transmission tower. We weren't sending a microwave feed from studio to tower as most traditional setup, and we had a 'listener' pi doing things like sending telemetry to the tech's residence, and re-booting or switching over in times of power loss. We ran another separate Raspberry Pi A as an off-air logger.
.
Needless to say our power costs were slashed to about 30% of original consumption, and then we had air-conditioning costs cut because we weren't cooling excessive equipment in our transmission room. The place was a quiet a a ghost, and I wrote some software for iPad that allowed our presenters to broadcast from < anywhere!! > over IP. The only down-side was that we were always searching for a good studio quality microphone that didn't consume a lot of power when doing outside interviews. Our studio microphone was, however, almost to good, we had to put our clock on the other side of the studio window.
Other people took over and were afraid that we were using $50 computers when we should have been using $$2000 +, but we were broadcast spec through our mondulators etc. Not once ever, even when we loaded it up with 10,000 processes, did it ever crash. Not once. Meanwhile their expensive PC's were always needing attention.
Such is the life of a community or public radio. Do something worthwhile, and they come out of the woodwork to stuff it up in any way they can. I've got the system at my place and can set it up again with the PI 4 and I am pleased the Ethernet bottleneck through USB has been fixed.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For a little while, the CommunityFM (to-air) radio station I was in charge of, ran its entire system with 3 raspberry Pi B2's. They were running our own very-hybridised System D linux. There was a thin client in the studio which acted like a control module for the "real" computer ( another Pi ) at the transmission tower. We weren't sending a microwave feed from studio to tower as most traditional setup, and we had a 'listener' pi doing things like sending telemetry to the tech's residence, and re-booting or switching over in times of power loss. We ran another separate Raspberry Pi A as an off-air logger.
.
Needless to say our power costs were slashed to about 30% of original consumption, and then we had air-conditioning costs cut because we weren't cooling excessive equipment in our transmission room. The place was a quiet a a ghost, and I wrote some software for iPad that allowed our presenters to broadcast from < anywhere!! > over IP. The only down-side was that we were always searching for a good studio quality microphone that didn't consume a lot of power when doing outside interviews. Our studio microphone was, however, almost to good, we had to put our clock on the other side of the studio window.
Other people took over and were afraid that we were using $50 computers when we should have been using $$2000 +, but we were broadcast spec through our mondulators etc. Not once ever, even when we loaded it up with 10,000 processes, did it ever crash. Not once. Meanwhile their expensive PC's were always needing attention.
Such is the life of a community or public radio. Do something worthwhile, and they come out of the woodwork to stuff it up in any way they can. I've got the system at my place and can set it up again with the PI 4 and I am pleased the Ethernet bottleneck through USB has been fixed.