For clarification, “Add All” adds the current modules within the plugin to your Rack module browser. In the future, any new modules included in the plugin won’t appear within Rack unless you go back to the library and manually add them. If you “Subscribe” you always automatically get all the plugin’s modules, including any new ones, in the Rack module browser.
I was about to say “I don’t see add all” in the library. But now I see that there are two library pages - one you get to from VCV (and that google take me to), the other one where “add all” is an option I guess you just need to bookmark that one so you don’t forget it?
Just a quick update: My plugin is still not available in the VCV Library.
The main reason is that all my mapping modules consume high to massive amount of CPU ressources within the VST plugin. I believe this is because any parameter change on a module is propagated to the VST host for automation etc. I’ve reported this issue a few weeks ago but haven’t heard back from VCV support yet.
I don’t think it is in anyone’s interest to have modules available which cause crackling and are pratically unusable.
You might try emailing VCV again Ben. I have found they have been pretty responsive recently and it might be your email just got ‘lost’ in all the support emails generated with the release of v2. A few weeks is certainly a reasonable amount of time to follow up if you haven’t had a reply.
Yes true. When morphing while using Transit especially right? Even on the lowest CPU setting for the morph, it maxes out the information the VST can process or something.
my workaround so far is just using 8face in standalone mode preferably not saving the state of modules directly if possible but of constant voltage modules connected to them , in the case of sequencers that have patterns I would start with 8face flashing out ideas then transfer them to the sequencer own memory. (with the handy copy and paste…) .
perhaps a module that only save presets for constant voltages will work better in the vst version ?
Not sure what you mean by that. 8FACE has no problems in the VST as far as I am aware of, nevertheless I’m waiting for a statement by support before doing any special workarounds.