I am guessing that it would be quite common for mAirList to be operated over a network therefore it would seem logical to have a single set of audio on a server which can be accessed by multiple playout instances.
If that is the case then what is the recommended way of referencing the server files? I have discovered that a UNC reference to a share on the server will work so is this the way to go?
The downside to a single bank of audio of course is that if the server is unavailable for any reason then everything comes to a grinding halt unless there is a fallback position such as checking a backup server or reverting to audio stored on the local PC.
Has a structured fallback been implemented in mAirList – if not can I add this as a future enhancement consideration.
Thanks
Ron.
At my home studio, I have 2 PCs which are used for audio… a playout PC and a streaming/server machine. All drives are shared on the network (all run XP SP2), but only 2 HDs are mapped to drive letters.
Studio Playout PC has songs stored on the 2nd HD, which is set to D drive - and is mapped as D on all other machines. The streaming PC also has a 2nd HD set to S, and is also mapped as S.
This allows both machines to access D: and S: as if they were local drives - The playlists can be used on either machine, as can schedulers, as all folders match.
Charlie,
I assume that the directories (D and S in your case) are synchronised and, if I understand you correctly, you have D and S drives on both machines which have the same content.
If that is the case then what happens when you scheduler says play S:\xxxxxx.mp3 and it is not available??
This was the point of my posting - a file location list could be defined in the configuration file so that your scheduler would only request xxxxxx.mp3 and mAirList should try S:\xxxxxx.mp3 and if that fails try D:\xxxxxx.mp3 and if that fails C:\xxxxxx.mp3 etc assuming that S D and C were defined in the configuration file. (or their equivalent UNC names)
Ron.
Not syncronised as such - Just 2 HDs in 2 PCs, but mapped as matching drive letters. Yes, if one PC fails (ie: the streamer), then S: is unavailable.