scook

Just because BitBridge supports 32 servers (assuming the documentation is correct) does not mean users may manually assign servers higher than 16.

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: select the server to use in preferences add the plug-ins to the project for that server repeat steps 1 and 2 until done 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. 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.

Audio clips are not stored in the project files. The clips are stored separately most often in an Audio folder wherever the project file is located. Project files contain references to where the clips are physically located. When clips are missing in a project, the area where the clips should be in the project display placeholders, effectively clips with no sound. Delete these placeholders from the tracks in the project then save the project and the references to the missing clips will no longer be in the project.

Delete the clip references in the project then save the project.

See https://www.waves.com/plugins/abbey-road-studio-3#tab-tech-specs|tab-supported-hosts There are only a few hosts that support surround sound and CbB is not one of them.

No, this is done in the DAW. The hardware does not matter.

Sounds like you're running CbB as Administrator. Windows automatically disables drag/drop between applications running as non-admin and admin. Very likely but rather that discuss the differences between CbB and SONAR X3 here, I hope @usalabs elects to create their own thread so that whatever problems they have may be addressed there rather than in this OP's farewell thread.

Not my experience, here is a video using CbB showing the import behavior attributed to X3. It works the same way regardless of the project track count. If there are specific issues, it may be better to address them in a new thread rather than appending them to this old thread.

When originally released, it was a single plug-in modeled on the hardware. The current release includes the original plug-in along with separate gate and compressor plug-ins. Seems like a decent price for 3 plug-ins. I paid $66.36 in 2016 for the original version. Can't say I use it all that much but then again, I have quite a few dynamics plug-ins before including all the channel strips with built-in dynamics processors.

I don't use MuseScore so don't have any idea how flexible the export process is. That said, if it can create a file without a lot of setup info, that would be best. When it comes to editing a MuseScore created file in CbB, it may be necessary to modify "%appdata%\Cakewalk\Cakewalk Core\TTSSEQ.ini" in order to see all the data in the Event List View. By default, CbB creates a "General MIDI setup measure" from some of the data at the beginning of a MIDI file and as a result this data is not displayed in the Event List View. Using a text editor open TTSSEQ.ini and in the [Options] section modify the GeneralMidiSMFs line to GeneralMidiSMFs=0 I second the recommendation to avoid using 32bit plug-ins like Arminator 2. Using it was a bad idea 10 years ago and has not improved with age. There are thousands of free and paid alternatives. And while there may not be another free CS-80, that does not make a SynthEdit version any more attractive. Here is a thread dedicated to free synth plug-ins.

precisely I have no problem with the FR just offer the current method while waiting for the FR to materialize.

Here are a few ways to delete markers

AFAIK, there is no way to connect the controller to the Focusrite Scarlett Solo because the audio interface does not have a MIDI input. The good news is, from a latency perspective, it does not matter whether MIDI is connected directly via USB or to an audio interface that also supports MIDI connections. Latency is strictly an audio problem. "MIDI latency" or the time it takes between pressing a key on the keyboard and hearing sound is all about the buffering in the DAW to keep everything in sync (plug-in delay compensation) and playback buffers in the audio driver (along with a relatively tiny safety buffer in the interface hardware itself). The time it takes for MIDI data to get from the keyboard to the DAW is nothing compared to the audio buffering necessary for monitoring audio from the DAW. To keep "MIDI latency" low, record MIDI as early as possible during project development, avoid plug-ins requiring large lookahead buffers when recording and keep the audio driver buffer as low as possible.

To import multiple clips, one after the other, into a track starting at 0 Select clips (in the gif below, I used a selection from the media browser) Click-drag the clips to the area between the track header and the clips area (AKA track scale) Hold down CTRL+SHIFT Release the mouse button to drop the clips in the track.

Yes, once recorded the data does not change. I am not sure which method was used to get the plug-in to play. Opening the clip in the Event List view will show all the data in the clip. Most often the part that shuts down sfz engine synths is at the beginning of the clip, but it could be anywhere.

Where did the MIDI data come from?

It is all down to the MIDI data streaming through the plug-in. All Cakewalk sfz engine synths have been sensitive to unexpected data since their inception. If the data is being generated in Tripleplay, review its configuration.

Usually, the result of unexpected data found in 3rd party MIDI clips For more info see

Input echo is the button to the right of the record button in a track

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=DrumEditor.05.html

How to report a crash If there is no crash dump, try setting ExceptionHandlingSeverity to 7 in Preferences > File > Initialization File The closest thing to a debug mode is safe mode. When running in safe mode it is possible to skip loading plug-ins, one at a time. To invoke safe mode, hold down the SHIFT key while opening a project.

Add Chordz to the project using a simple instrument track. Set the input to the virtual controller and enable input echo. Set the input on the instrument/MIDI track of the synth to Chordz and enable input echo. Play the virtual keyboard.

For now, play the virtual controller through a plug-in like FN42 Chordz and use it as the input to other instrument/MIDI tracks.

The info about attached file shows zero bytes. Instrument definition files are text files and http://www.korgpa.sk/ins/korg_pa4x_all_basic_2015v2.ins appears to be a valid instrument definition file. Use "Save as" to save the file and give it a .ins extension. Note, CbB does not use these files directly instead an instrument definition file must be imported into the master.ins in the user's directory. Here is the documentation about importing instrument definitions into the master.ins.

As you can see from the image above, the metronome settings are stored in projects and project templates just like everything under Preferences > Project. Instead of using factory supplied templates consider making copies of the factory templates you use with the metronome setup as desired. Do not modify the factory templates as they may get overwritten by an update. Either give the new templates names unlike the factory template names or set up a custom folder to store your templates and point the Templates entry in Preferences > File > Folder Locations to the custom folder. CbB Installers do not write to a custom templates folder, instead; they always update the default folder.