Getting started with Musebots on Mac OS 10.12 (Sierra)
Some odd security issues in OS 10.12 will affect musebots after downloading them. Note that this only occurs on Mac OS 10.12.
Description of problem:
After downloading a zipped musebot (Conductor or Musebot), and unzipping it, the OS assumes that its path is inside the /private/var/folders directory. As a result, musebots cannot find their own config.txt files, and the Conductor cannot find the musebots.
To solve this problem, follow these steps:
- download the desired Conductor and musebots archives, and unzip them;
- or download “Musebots_Getting_Started.zip”
- create a new working folder (i.e. “Musebot work”) somewhere on your computer;
- Inside that folder, create a new folder and name it “Musebot Conductor Application”;
- Inside that same folder (Musebot work), create another folder and name it “Musebots”;
- note that these folders must have those actual names
- create individual folders for each musebot (with the correct names, i.e. ae_CleanBeatBOT);
- the easiest way to do this is to copy the name from the downloaded musebot
- note that the folders must have the same name as the musebot
- for each musebot/conductor, move all the files except the musebot application into the respective folders.
- move the musebot/conductor application to the correct folder.
The process of individually copying the musebot applications seem to correct the file path problem. You can test this by running the Max_Musebot_Conductor, and seeing if
- the Conductor populates the Musebots folder correctly
- launching a musebot actually launches it, and the musebot receives the OSC messages.
Note that when you first launch a musebot or conductor, you will receive a warning message that the application has been downloaded from the internet.