Lately I’ve been running into issues with seeing modules that I built using
make install
My modules are not appearing in the module browser because the moduleWhitelist in settings.json doesn’t list them.
My subscription state is at the individual-module level, so settings.json contains something like:
“voxglitch-devices”: [“spores”, “centralics”, …]
When I add and build a new module, its slug isn’t on that list, so the browser hides it.
Current workaround: before launching Rack I edit settings.json and replace the array with `true`. That works for the session, but Rack rewrites the file on shutdown to match my library subscription state, so I redo this every launch. This wasn’t a big problem before, because I hadn’t marked myself as a buyer for any of the modules.
The recommended fix there is to subscribe to the whole plugin via library.vcvrack.com. That requires publishing the new module first, which is what I’m trying to avoid until I’ve tested it locally.
Questions:
1. Has anyone found a more durable workaround than editing settings.json each launch?
2. Is there an undocumented dev flag, or a way to mark a plugin as “in development” so its modules are not filtered?
Running Rack with the -d parameter makes it use its local folder as the source for everything (settings, plugins…)
Don’t want that? Don’t use that? No change?
You can always use two copies of settings.json with different names; run Rack with batch files / shell scripts that switch between your different settings.json versions and then call the main program.
Another option, also mentioned in the manual, use environment variables and different folders for settings.json.
Now… did you add your own modules from the library; but not the complete plugin? (Why?) There’s your problem… just remove the entry for your own plugin from the whitelist and all your modules should show up.
Yeah, as countless people have said in here countless times - subscribing to individual modules is a bad design with unwanted surprises, so don’t do that, only subscribe to whole plugins.
I think the following should fix your situation:
Go to the library and unsubscribe the plugin. That should clear out the module subscriptions.
Open Rack and wait 30 seconds until it has synced the subscription state from the library.
Go to the library and subscribe to the plugin.
Open Rack and wait 30 seconds until it has synced the new subscription state from the library.
Close Rack. Now the silly module whitelist for the plugin should have cleared, and any new modules in it will also show up.