Got it, thanks.
devices.xml had 12 different machine configs in it, which is unusual. This suggests you are copying installation files from one machine to another, maybe the entire /Users/.../Library/Application Support/Circular Labs/Mobius directory?
Things aren't as simple as they were in Mobius 2 which had everything in a single mobius.xml file. There are now around 8 .xml files, some of these contain user content and others contain system content. For the system files like symbols.xml and static.xml, these change on each build so it is vital that you not replace what the installer puts down with files from a previous build.
If you do in fact move between 12 machines and copy config files, that would explain why there are 12 <Machine> entries in devices.xml and scripts.xml. If you DON'T have 12 machines, then there is something strange going on with the what the OS gives me for the machine name. If you do occasionally go into System Settings and change the machine name, that would also cause this. But some of these names look concerning:
Mac
Mac.fios-router.home
Mac.hsd1.nj.comcast.net
Mac.lan
This suggests that the machine name is "Mac" but what the OS tells me the unique machine name is will
be different depending on the network you are connected to. If this is a laptop that you move around between work spaces, or venues, that might explain it. I do most of my work on Windows and I don't connect to different network routers, so this may be a Mac quirk I need to figure out.
What I don't understand is why you lose script externals when swapping between the standalone and plugin versions. Assuming you're on the same physical machine and connected to the same network when you do this, I would expect the OS machine name to be the same, unless Reaper doctors it in some way which would surprise me. One possibility is that there was an incomplete installation. On Mac, the standalone app and the plugins go in three different locations on disk, so it is important that you use the installer app, and may need to "rescan" plugins in the host after installation. Use Help->About to check the build number in the standalone app, then again when running the plugin and make sure they are the same.
Anyway, there are still some mysteries here I'll need to explore, but let me explain how this works so we can get it patched up in the meantime.
There are two files that store different configurations for different machine names: devices.xml and scripts.xml.
devices.xml is where these live:
audio device names
audio channel selections for Mobius ports
midi device names
midi device usages (enabled, export, sync, thru)
plugin input/output port counts
the location of the User File Folder
scripts.xml has two things:
the list of "script external" files and directories
the "flat list" of all script files found in either external folders or within the installation
The important one here is the script externals list. The flat list will be regenerated automatically
whenever Mobius starts.
The script externals list is what you are editing when you go to the Scripts->Library window and click
the Externals tab. It is a list of path names to indidividual script files or to directories that
contain multiple script files. These are "absolute" or "full" paths, on Mac they usually start with /Users/yourname/... or /Device/diskname/... Because these are absolute paths, they are not always the same from one machine to another, even though they will ultimately contain the same .mos or .msl files.
So...I don't know if you want to do this, but what you can do is look through those .xml files and find the <Machine> entry that seems to have the most stuff in it. Delete the others. Then bring up Help->Environment window and look at the lines at the top, they will be similar to this:
Mobius 3 Build 45 Standalone
Computer name: Baldr
Configuration path: c:\dev\mobius3\Mobius\Source
Audio block size: 256
The name after "Computer name:" is the name I am using to locate machine configurations. Go back to scripts.xml and find the <Machine config that you want to use:
<Machine name="Thor">
<Externals>
<External path="c:\dev\mobius3\Mobius\Source\test\scripts\bindingarg.mos"/>
<External path="c:\dev\mobius3\Mobius\Source\loadmidi.msl"/>
<External path="c:\dev\mobius3\Mobius\Source\loadmidi2.msl"/>
<External path="c:\dev\mobius3\Mobius\Source\events.msl"/>
<External path="c:\dev\mobius3\Mobius\Source\testscripts\multiclick.mos"/>
<External path="c:\dev\mobius3\Mobius\Source\testscripts\sustest.mos"/>
<External path="c:\dev\mobius3\Mobius\Source\testscripts\vartest2.msl"/>
<External path="c:\dev\mobius3\Mobius\Source\testscripts\pubvar.msl"/>
<External path="c:\dev\mobius3\Mobius\Source\testscripts\varquery.msl"/>
<External path="c:\dev\mobius3\Mobius\Source\testscripts\sustest.msl"/>
<External path="c:\dev\mobius3\Mobius\Source\testscripts\reptest.msl"/>
<External path="c:\dev\mobius3\Mobius\Source\testscripts\susreptest.msl"/>
</Externals>
Change the name to the one you see in the Environment window. In this case I would change "Thor" to "Baldr".
Alternately, you can keep all the <Machine> sections, and copy/paste the <External path="...
lines from one machine to another.
There are things I could do to make this easier. Some sort of migration tool that copies configuration files from one machine to another and tries to fix the file paths. Or perhaps make multi-machine configuration an option that only I use and everyone else only gets a single <Machine> that may not always be portable.
That may not help though if machine names change randomly based on the network you're connected to. If I can understnad the rules around that, it may be enough to just treat these as all the same:
Mac.fios-router.home
Mac.hsd1.nj.comcast.net
Mac.lan
Only use the part up to the first period as the machine name and ignore the rest.
The User File Folder would solve most but not all of this. If you put your scripts in there rather than using <Externals> then you wouldn't have to keep redefining the external files every time this happens. The location of the User File Folder itself though is in devices.xml and is machine specific. So each time this mysterious name change happens, you would have to go back to File->User File Folder and enter that one location again.