> I'm not sure that helps, or hurts you. > Depends which machine is running caed. the server. originally it had /var/snd, the audio card, and caed.
>> I could move the >> soundcard to the airplay machine if we are going to keep this config, >> but really it shouldn't make a difference anyway should it? > Latency between the source audio file, and the sound card. so it would be NAS to server , or NAS to Airplay machine, latency (in theory) would be no different? Nathaniel C. Steele Assistant Chief Engineer/Technical Director WTRM-FM / TheCrossFM On 11/28/2011 2:57 PM, Cowboy wrote: > On Sunday 27 November 2011 12:17:14 pm Nathan Steele wrote: > >>> OK, if I understand you correctly, the server via eth0 mounts the >>> NAS from 192.168.x.x >>> Then, the server exports /var/snd via eth1 on 192.168.y.y and the >>> workstations mount /var/snd from 192.168.y.y >>> >> Pretty much, the NAS is mounted 192.168.x.x on eth1, >> and the export (and all other network traffic) is on 10.100.y.y > OK...... > >> The server also has the soundcard that is playing out. this was >> originally done to have the audio and playout on the same machine, even >> though the airplay app is actually on its own machine. > I'm not sure that helps, or hurts you. > Depends which machine is running caed. > >> I could move the >> soundcard to the airplay machine if we are going to keep this config, >> but really it shouldn't make a difference anyway should it? > Latency between the source audio file, and the sound card. > >> the >> production machine does have it's own soundcard. by the way, airplay has >> continued just fine since the transition, but we still can't import or >> VT from the production room because of this permissions problem. > _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
