To run a (second) set of Audisi ONE for test purposes WITHOUT affecting the actual version.
This way you can perform several tests, like a database upgrade to a new version, test new functionalities or convince yourself of proper functioning of faderstarts, playout, im- and exports, device connections, client-server communication, etc.
SERVER MACHINE
- Create a folder named ‘Beta’ inside the C: or D:\Audisi\ONE\Bin directory. The name Beta is not mandatory, but it covers the purpose of this folder.
- Copy the actual content of the Live folder (or a new version) into the Beta folder. Of course without the ONE_Base.abs file, because this file is in use by the ONE-Server.
- Copy a recent database backup file (*.abs) into the Beta folder. Rename the file to ONE_Base.abs.
- Create a new shortcut for the ONE_Server.exe in the Beta folder. Rightclick this shortcut and add these command line parameters to the Target line:
srv1ipport=40001 srv2ipport=40001
40001 is just an example, feel free to use any 4xxxx number if available
- Double click the shortcut. The ONE-Server will now start listening on Network connections 1 and 2 to port 40001 for incoming clients.
- Any client that should connect to this Beta Server should have it’s own shortcut with srv1ipport=40001 on its Target line.
CLIENT MACHINE
- Create a folder named ‘Beta’ inside the C: or D:\Audisi\ONE\Bin directory.
- Copy the actual content of the Live folder (or a new version) into the Beta folder.
- Create shortcuts for client applications with ‘srv1ipport=40001’ on its Target line.
SHORTCUTS
Hint: store the Beta shortcuts on the desktop or inside the Beta folder for re-usage. Use names like BETA_ONE-Server, BETA_GML-Manager etc.
SAFETY
Be aware of the fact that the Live and Beta applications use separate database, but they use the same database settings.
Modify the File path for type ‘Audio items (database)’: define another location for audio files.
Otherwise you may modify existing audio items with the result that the Live database is not aware of those changes. In case you need to test audio/video files: copy just a few files that you might need for test purposes from the main storage to the Beta destination.
LOG FILES
Live and Beta applications will write into the same Event log files. Change the (Beta) log file destination if you would like to have separate log files.