I’m devising an mAirList configuration for a radio station with multiple studios.
All audio, and most of the settings will be common to all workstations. So in my intitial experiments they start mAirList with the “-rootfolder” parameter pointing to a network share, so the appearance and behaviour is the same. All is as expected.
But there are some things we need to set locally to each machine. I can see solutions to some issues, but not others :-
Auto / Assist mode - that could be saved to a local file by a script, and activated (or not) by OnLoad in a background script.
Audio Devices - the PCs may have different hardware, with or without multiple devices. So the device configuration will have to be unique. Is there some way to maintain a local copy of “devices.ini”?
System Log - while it’s possible to custom set the path, the actual path setting is stored in logging.ini that lives in the general config folder, which we’d like to have as common.
One workaround I’ve contemplated is storing a global common config on the server. On each PC the mAirList desktop icon initially fires a script that downloads those global files, over-writing the local copies. Files for local settings are not over-written, but just protected as required. The script would then start mAirList.
It’s rather clunky, but it may do the job. If there’s a more elegant way to have this “hybrid” arrangement I’d be really interested to know how.