There are several scenario available, each of them with pros and contra. As
far as I learnt you can/must share these things. They don't need to be all
on the same computer, you can imagine also mixed configurations.
- Audio catalog: a good way is doing using NFS. You could use Samba, but no
reason if they're all Linux computers.
- Database: MySQL or MadiaDB or whatever. Setup the Rivendell MySQL user,
i.e. 'rduser' to be accessible from all over the network.
- Apache/httpd (import/export tasks). Every computer can have its own or
share it over the network. No special settings in here.
- Audio resources (read 'audio cards'): one rdariplay can sound on other's
audio card.
I think it's all. There isn't a right or wrong way of doing it. It depends
on your needs.
The only think I would suggest, even if it seems I'm the only one
experiencing it, is moving audio files on the same machine of main audio
card. Should sound faster.
My 2 cents.

Alessio


2013/5/14 Jorge <[email protected]>

> No concern at all.
>
> T-Mobile, America's First Nationwide 4G Network
> Sent by Samsung Mobile
>
> Brian McKelvey <[email protected]> wrote:
>
> >Support and updates for 11.04 have already ended, as it's not a long term
> support release. Is that a concern?
> >
> >Sent from my iPhone
> >
> >On May 13, 2013, at 4:08 PM, Jorge <[email protected]> wrote:
> >
> >> Thank you, I'm running ubuntu.11.04.
> >>
> >> T-Mobile, America's First Nationwide 4G Network
> >> Sent by Samsung Mobile
> >>
> >> Gavin Stephens <[email protected]> wrote:
> >>
> >>> These are probably the most important wiki entries to browse over:
> >>>
> >>> http://rivendell.tryphon.org/wiki/DHCP_vs._static_IP_addresses
> >>> http://rivendell.tryphon.org/wiki/Remote_Client_Access
> >>> http://rivendell.tryphon.org/wiki/NFS_Server_and_Client_Configuration
> >>>
> >>> Some of it is OS specific like Ubunto setup, but it may help give you
> an
> >>> idea. I originally setup two seperate RD's, one OnAir the other
> Prouction.
> >>> In my case OnAir was the store and database so I set that all up to run
> >>> independently first. I set them with static IP's then tackled the
> hardest
> >>> part which was configuring SQL on the the one that will be the server.
> Once
> >>> I did that, configured the Production RD to connect to the SQL RD.
> Then I
> >>> did the NFS part to get the audio sharing, and last setup the host in
> >>> RDAdmin on the SQL server for the client PC as the sound cards and
> settings
> >>> for the client PC are also stored in the SQL database.
> >>>
> >>> I'm sure others will be able to give specific advise to whatever OS
> you're
> >>> using.
> >>>
> >>> Cheers,
> >>> Gavin.
> >>>
> >>>
> >>> ----- Original Message -----
> >>> From: "Jorge" <[email protected]>
> >>> To: <[email protected]>
> >>> Sent: Tuesday, May 14, 2013 8:59 AM
> >>> Subject: [RDD] Networked rivendell
> >>>
> >>>
> >>>> I know it has been discussed, can any one point me in the right
> direction?
> >>>> We want to have the on-air machine networked to the PD/production
> computer.
> >>>> All audio and log files will reside on the PD computer.
> >>>>
> >>>> T-Mobile, America's First Nationwide 4G Network
> >>>> Sent by Samsung Mobile
> >>>> _______________________________________________
> >>>> Rivendell-dev mailing list
> >>>> [email protected]
> >>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
> >>>
> >>>
> >>> _______________________________________________
> >>> Rivendell-dev mailing list
> >>> [email protected]
> >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
> >> _______________________________________________
> >> Rivendell-dev mailing list
> >> [email protected]
> >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
> >_______________________________________________
> >Rivendell-dev mailing list
> >[email protected]
> >http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
> _______________________________________________
> Rivendell-dev mailing list
> [email protected]
> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev

Reply via email to