Jump to content

available ram servers


Recommended Posts

In general, 32bit plug-ins should be avoided in new projects. The developer abandoned them years ago or they have replaced them with 64bit versions.

 

I have never messed with BitBridge Server Configuration

It is only relevant when using 32bit VST plug-ins and in most cases, automatic assignment is good enough.

 

By default, the servers are automatically managed by the software and the servers are loaded using server 1 first.

 

Manual server assignments may be made on a per-project or per-plugin basis.

Per-plugin assignments override per-project assignments.

 

To manually assign plug-ins into specific servers on a per-project basis:

  1. select the server to use in preferences
  2. add the plug-ins to the project for that server
  3. repeat steps 1 and 2 until done
  4. save the project

The server assignments are stored in the project.

 

To manually assign all instances of a plug-in to specific server, use the BitBridge Server value in the VST  Plug-in Properties dialog.

This dialog is found in the VST2/3 drop down in VST standard header and in the Plug-in Manager.

To access the standard header for a plug-in running in BitBridge, hold down the ALT key when adding the plug-in or opening its UI. Usually the standard header opens under the plug-in UI.

Here is an example opening the old Cakewalk BitMeter a 32bit VST and setting its BitBridge Server from automatic to server 2.

t9mucAN.gif

The changes will be picked up the next time the project is opened or the plug-in is loaded.

Per-plugin server assignments are stored along with the rest of the plug-in properties in the VST Inventory in the registry.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...