we are currently testing the software. The only part that we are stuck on is voicetracking for our DJ from their home.
I’ve been able to set up de connection. At home we can see and modifie the database/playlist.
But when I try to cue a song I get this error message : " HTTP/1.1 404 Not Found "
Not sure what the source is?
Second question, what do you use to get the central database to sync with the database @home with the dj’s?
Might be handy (and should create less network transfer) if they have a copy of the database @ their place.
Any help on those 2 subjects would be appreciated.
Found something, when using the non secured version http in stead of https it’s working. I’m able to cue tracks and do voicetracks.
If somebody can explain why there is this difference?
Now there still is this sync issue for different deejays at their home.
Actually it should work with either http or https. Please tell me the exact version and build you are using (on the client and server), and I will check if there is a bug.
Regarding the sync, if the DJs have a sync’d copy of the library on their local harddisk, they can register it as a “storage redirection” in the mAirListDB connection properties. mAirList will look into the local folder rather than using the server now.
But the actual sync is not part of mAirList, you must use something like Dropbox etc.
Hello Torben,
We are running version 5.1.2 build 2774
I’ve set already something with an ftp server on the centrale pc. That part is working.
Now I only have to find the storage redirection option for that issue.
Does the location on the Dj’s pc need to be the exact same as on the onair?
Example at home “c:\database” on air “y:\music 1” ?
Only “Some Artist\Some Title.mp3” is stored in the dataset of the item, and the storage directory is prepended again when the file is requeted.
By using Storage Redirection, you can instruct mAirList to prepend a different path instead of C:\Music. The one that matches the sync’ed copy on your local PC.
When accessing through the DBServer, the filename will look like “dbserver:”, which is internally resolved to an HTTP URL. But storage redirection should work nonetheless.