[RDD] Rivendell Running on Raspberry Pi 2
steelegbr at gmail.com
Thu Jul 2 10:46:57 EDT 2015
The idea Pis as thin clients rather than actual playout boxes isn't a bad
one. Though I'd be inclined to look at a vendor supported thin client
option for a big station over Raspberry Pis. They come with the cost
benefit but have been known to eat through SD cards and prove generally
unreliable on occasion (we've got a national fleet of them doing digital
signage in studios where I work).
There's also split ads and whatnot to worry about in a big installation.
I'm not sure I'd go with just one big box in the middle running all the
audio, even if you usually rely on one SQL/file server (with a warm/cold
Either way, splitting audio out from a thin client unit in the studios
could be a winner. Especially if it costs less and proves more reliable
than KVM extenders used in the installs I've supported.
The one I've been meaning to get the time (and licences) to play with is
VMs in a fault tolerant environment using LiveWire or Rivenna. Potentially
a bit overly complicated for a small service but the sort of thing you
start thinking about with multiple splits and services.
On 2 July 2015 at 15:27, Brad Beahm <brad at kliqfm.com> wrote:
> The idea of running Rivendell on the Pi could be quite appealing for
> multi-station radio groups... under certain conditions.
> If I had the time and money here's how I'd do it.
> BUILD A BIG BULLETPROOF SERVER-
> Use server class hardware, redundant drives, lots of RAM and a big UPS to
> run the official Broadcast Appliance server version from Paravel. That
> would hold the /var/snd audio and mySql database. And I'd put in the
> professional Audio Science audio card(s) into the server machine. (or if
> you've got a AOIP plant the network audio drivers would be on that server
> machine). GPIO and Switcher cards could also go there for satellite uses.
> The Pi's would then just connect to the server as individual hosts. They
> could be setup to use the Core Audio Engine on the server so their cheap
> audio isn't a problem. I think you'd also be able to us the Pi's GPIO pins
> to control starts/tallys from equipment in the studio
> I'd mount the Pis behind the monitor in studio (could be touchscreens).
> The only cables you'd need to run would be the Ethernet, power,
> keyboard/mouse and any GPIO.
> It'd be a lot more efficient to have a bunch of Raspberry Pis as thin
> clients to the server than to try and build out whole machines for each
> studio. Keeping spares would be a lot easier too as you could keep fully
> configured Pis or just a few configured SD cards handy. A swap would only
> take a few minutes.
> And at $40 you could put a Pi in about every office (Traffic, PD, Prod,
> Engineering) to allow logs, music, and spots to be imported conveniently.
> The overall system cost could be pretty low compared to a similar system
> of that size from other automation vendors. (I'm thinking of products like
> Enco1 http://www.enco.com/products/enco1.html)
> On Wed, Jul 1, 2015 at 11:20 AM, Brian McKelvey <theturtle32 at gmail.com>
>> Sure can! The built in audio output is unbalanced and very, very noisy.
>> Terrible, really.
>> But I had no problems at all connecting a USB audio adapter and using
>> that instead. Even a $7 one from Amazon has a dramatically better noise
>> floor than the built in audio.
>> So yeah, basically any Linux-supported USB audio device should work fine.
>> Sent from my iPhone
>> > On Jul 1, 2015, at 4:46 AM, Rob Landry <41001140 at interpring.com> wrote:
>> >> On Wed, 24 Jun 2015, Brian wrote:
>> >> Just thought I'd share with you that I got Rivendell running
>> flawlessly on a Raspberry Pi 2 Model B.
>> > Can you get good quality audio out of it?
>> > Rob
>> Rivendell-dev mailing list
>> Rivendell-dev at lists.rivendellaudio.org
> Rivendell-dev mailing list
> Rivendell-dev at lists.rivendellaudio.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Rivendell-dev