Hello, We've been using Rivendell as a sustaining playout system in the past and it's proved to be very reliable and flexible.
Currently we have one studio, with its own playout system (currently not Rivendell) simply used for live programmes. We have a second playout system (again not Rivendell) which also feeds the main desk. This runs the pre-recorded programmes, sustaining service, etc. This all works well and we can switch the sustaining playout live to air, bypassing the desk, to enable the single studio to do pre-recs, etc. We're now constructing a second studio and then overhauling the first one. We're planning to switch to Rivendell as the sole playout system. I have a Rivendell machine serving the second studio (currently under test) and a separate network server for MySQL, /var/snd and running the web based services (running rdxport, etc.). This all works fine. My aim is to have three playout systems. One for each studio and a third - a kind of master control - handling the playing of pre-records, sustaining playout, remote contributions, etc. So the master control would follow the main schedule, switching the studios live, playing pre-recs, etc. Is this possible with Rivendell? Is this the best way to achieve what we want to achieve? I'd be very grateful to here how other people handle multiple studios, pre-records, etc. Many thanks, Steve.
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
