scook

There should be no problem. Updating CbB from any version older than the most recent prior production release causes BA to download and run the full CbB installer.

The initial error message suggests changing the Driver Mode. This is located in preferences When using the internal sound chip try one of the WASAPI modes if running Win10, WDM for other OSes and last choice is MME

It's all yours Craig Why should I have all the fun

CbB always records the signal at a track's input. Any time one wants to record a signal affected by plug-ins, the track containing the plug-ins needs to be routed to an aux track or another track using a patch point. The wet signal may be record in this track. Try this,,, 1. Add Sonitus Gate in the FX rack on the mic track 2. Click the Audio button on the Sonitus UI changing it to Duck 3. Enable input echo on the mic track 4. Route the mic track output to a new aux track 5. Record enable the aux track 6. Create a send on the music track to the Sonitus:fx Gate (Side Input) 7. Enable input echo on the music track Now any time signal hits the music track, the aux track will be muted. Anytime this method of recording a wet signal is used, it is a good idea to record the dry track too, just in case. May need to experiment with the hold and release times to make sure the gate does not open with quite parts of the music.

The few 32bit plug-ins I have are all from SONAR Product/Platinum. They are all installed in the default plug-in path C:\Program Files\Cakewalk\Vstplugins. They scan OK. Yesterday, I have reason to load Cakewalk Sound Center. I just installed and tested DSK xXx, a 32bit synth into C:\Program Files\Cakewalk\Vstplugins\DSK xXx Could try installing one of the plug-ins on a different drive.

It is hard to help without better info. Is the "custom folder" compressed?

Deselect "Copy all audio with project" in the "Save As" dialog. There is no requirement for "Save As" to always copy clips when creating a new project and the new project may even reside in the same folder as the original. In the track view Apply Trimming crops clips to the size used in the project. May want to experiment with both of these on a copy of the project to see how the work.

Either export a mix or the individual tracks starting at 0.

If there is an autosave copy or versions either copy them somewhere else (so they don't get overwritten) or rename the bad project file. Then try opening the bad project in safe mode by holding down the SHIFT key while opening it.

Any particular 32bit plug-ins being reported as "NOT a VST plug-in" Where are these plug-ins installed? What version of C:\Program Files\Cakewalk\Shared Utilities\VstScan.exe is installed?

how do these compare...?

Plug-in automation is available on a per-plug-in instance basis. A single instance of a plug-in with multiple outputs has one set of automation lanes available to it. They may be placed on any track. Until MIDI automation is added to instrument tracks, it is necessary to (temporarily) split instrument tracks to access MIDI automation on the MIDI track created.

May want to follow the link the image to the help center and open a ticket with them.

Here is the thread to report problems with 2020.04 Put the project on One Drive, Google Drive, Drop Box or a host of your choice and post in the thread with a steps to reproduce and a link to the project.

There are several ways to enter MIDI data mentioned in the second thread

Sounds like a good autohotkey project

Here is how I add Wheel to the Controller Pane in the PRV For now Instrument tracks do not provide access to MIDI automation so there is no point in using instrument tracks if you know you want to draw MIDI automation in the track view. When Cakewalk sfz synths go silent is it often due to try to play unsupported data. This may be cleaned up in the Event List view or by enabling "Do not intercept NRPNs" in Plug-in Properties from the plug-in header. When running 32bit plug-ins in CbB using BitBridge the track header is in a separate window. To gain access to the window hold the ALT key when adding the synth to a project or opening its UI. The header usually opens behind the plug-in.

This is a feature request (and given Noel's reply will likely not materialize). For now, screensets are a per-project setting. To have your screenset available in new projects create a template from an existing project that already has the screensets in it. Going forward, use the new template(s) for new projects and the new projects will inherit the screenset from the template(s).

Notice in the animation, MIDI automation for wheel events shows a 0 in the middle for the automation lane. MIDI automation works just like any other automation in the Track view. MIDI automation is only available on MIDI tracks so, if using an instrument track, it must (temporarily) be split into its constituent audio and MIDI tracks to gain access to the MIDI envelop dialog. It does not create CC for Wheel. It is the area where the Wheel data along with CC data are displayed in the PRV. I could have written that a little better.

BTW removing files from the default folder is a temporary thing. They may get added back by an update. Updates do not affect custom folder locations (this is important) and why I create custom folders for templates and drum maps. Good news.

Yeah. that is a pain. You may change the name of the drum map file so that it appears at the top of the list. What I did was create a new folder and put the drum maps I use in it and change the Drum Map folder in preferences to the new folder.

Like other per-project settings Screensets are saved in project templates

This is pretty definitive and one reason I don't buy AAS products (Now if they made new VCV Rack modules it would be different). From https://www.applied-acoustics.com/tassman-4/faq/

Drum maps are stored in the project and provide several features to handle MIDI data. Drum map presets like the one I built use the same tools as a drum map stored in a project but are stored on disk and may be loaded and stored in projects at a later date. Any drum map may be stored as a preset by giving it a name and saving it using the Drum Map Manager.