scook

Seems OK here. Test with a simple project. IOW, create a new project, save it, close and re-open CbB. The program may be hanging on exit. If this happens, the project MRU list does not get updated. Check the Windows Task Manager after closing CbB to verify the program has shut down. This can be plug-in related. Especially when using 32bit plug-ins. Another cause is CbB waiting on the audio interface. Make sure the driver is current.

The Windows Event viewer may offer some clues

Please, do not cross post

no, read the help about the option

If the pitch bend data is recorded it is up to the soft synth how it deals with the data just like the rest of the MIDI data it receives. Not all soft synths respond to pitch bend data. For those that do, not all patches for the synths may use the data or may have it mapped to something other than pitch. TTS-1 is a good test plug-in. It is a GM synth.

Does the data get recored?

Is the Input Echo enabled on the instrument/MIDI track? The Input Echo button is right of the record button.

Configuring effects as synths is not necessary and has not been starting with SONAR X3. I do not have any Bias plug-ins but just tested with TH3 Cakewalk VST3 3.4.9 on CbB 2020.11 build 99. Win10 2004. After adding the plug-in to the FX rack, I selected "Enable MIDI Input" from the VST3 drop down (this eliminates the need to config as a synth) Added a MIDI track setting the input to my controller, the output to TH3 and enabled Input Echo In the TH3 UI I dragged BassFace '59 into the workspace Right-clicked on the BASS knob on the BassFace and selected "Learn Global MIDI" While moving the mod wheel on the controller, clicked OK in the "Learn MIDI" Dialog. The BASS knob now responds to the controller mod wheel.

Similar thread

The colors are theme dependent. In the default Tungsten theme Orange are VST2 format Green are 32bit VST2 format (maybe 32bit VST3 too, I do not have any to test) Gray are DX and VST3 format. The DX plug-ins icons have an X above the keyboard

similar thread

Read about this early today and downloaded it. Now at release 1.0.1. Not bad.

Fullbucket recently released Bucket Pops a VST2/AU, Mac/PC, 32/64bit plug-in modeled on the Korg Mini Pops-7 rhythm machine from the 60's.

The scan frequency is set in VST preferences By default, the scanner only attempts to load a plug-in one time. It does not matter how often the scanner runs. At that time the plug-in is evaluated and the results are stored in the VST registry. The exceptions to this are plug-ins that load via a shell program such as Waves - the scanner must scan these every run. Users that have large number of plug-ins that use this type of architecture usually set the scan frequency to manual. (Arturia does not use a shell program) the rescan settings are enabled in VST Preferences - just below the scan frequency drop down these options should always be turned off unless attempting to solve particular scanning problems and then they should be enabled for a very limited time. It is unusual for the Arturia plug-in fail scanning. This is likely a system specific problem and needs more detail to diagnose. An image of the typical error message may help. Plug-in category tags are a VST3 feature. When Cakewalk added VST3 support, they added categories to the database for quite a few VST2 and DX format plug-ins. Most VST3 plug-ins have category tags supplied by the manufacturer. Those VST3 plug-ins that have no category tags and VST2/DX plug-ins not found in the category database go in the Uncategorized folder. Regardless plug-ins may be re-categorized using the plug-in browser. Plug-ins may be added to the Exclude List at any time. Plug-ins on the Exclude List are ignored by the scanner and not displayed on plug-in lists. If an excluded plug-in is referenced in a project, it still loads and runs in that project. The Exclude List is maintained in the Plug-in Manager, a tool in the Utilities menu. To add a plug-in to the Exclude List using the Plug-in Manager, click on the plug-in in the Registered Plug-in list in appropriate plug-in Category then click the "Exclude Plug-in" button below the Plug-in Categories. To take a plug-in off the Exclude List using the Plug-in Manager, click on the plug-in Category, click the "Show Excluded" radio button, click on the plug-in name in Registered Plug-ins then click the "Enable Plug-in" button. Please note how much easier it is reading posts that take advantage of mixed case and whitespace.

How was the transposition done? How was the project saved? A few more details about the project may help. Assuming the saxes are generated from MIDI what synth(s) where used. Was their an instances of the synth for each instrument/MIDI +audio track pair? The "Silent Hardware" message usually means some tracks/buses have their output or send(s) is set to None.

Audio clips written by destructive processes use the Render Bit Depth setting.

This feature already exists. See the thread that formed the basis of this request

@msmcleodthe audio driver is 16bit and the drop down appears to be disabled. If this is the case, the driver can only send 16bit data, There is no advantage to recording at a higher bit depth than the driver driver is capable of sending. AFAIK, doing so simply pads the file with zeroes adding no useful data.

similar report

Think of Rapture Session as the replacement for Cakewalk Sound Center. Both are designed to play programs created for other synths. They have simplified interfaces with few controls. The programs for Rapture Session came from the new content bundled with Rapture Pro. Rapture Pro was the replacement for the original Rapture and Dimension Pro. It included all the programs bundled with those synths and many more. Unfortunately, BandLab has not released their version of Rapture Pro; the synth is not available at this time.

Rapture Session is a program player. It does not have a way to adjust the program behavior outside of the Instrument tab. Pitch Bend range is typically not displayed on that screen. Dimension Pro, Rapture Classic and Rapture Pro all have per-element settings for pitch bend range. Here an image of DP showing the pitch bend range setting for Element 1.

This is because these plug-ins were built for the original version of the ProChannel released with SONAR X1. In this version there was a dedicated slot for each plug-in category. IOW, the ProChannel could have one Frequency processor, one Dynamics processor, one Distortion processor and so on. The order of the processors could be changed but only one processors of each type could be used in the strip at a time. This changed with the introduction of the modular ProChannel in X1 Producer Expanded. The modular PC eliminated dedicated processor slots allowing more than one compressor, EQ , etc. in a PC at a time. The PC-2A and the newer CA-2A are examples of PC modules developed for the modular ProChannel. As mentioned before, while QuadCurve EQ resides in the PC and looks like a PC module, it serves as the replacement for a function that pre-dates the ProChannel. For this reason, it does not act like regular PC modules.

32bit VST plug-ins run just as well in 64bit DAWs on Win10 as they do on Win7. The plug-ins do not run directly in the DAW. Instead they rely on bridge software to host the plug-ins and communicate with the DAW. 32bit DX plug-ins do not run in 64bit DAWs. There is no comparable bridge for DX plug-ins. That said, some 32bit DX plug-ins will work by using a VST wrapper making them appear as 32bit VST plug-ins to bridge software. This is a very fragile solution.

Try the different driver modes in preferences. Make sure to set Cakewalk to 48kHz sample rate. According to this pdf, the device is fixed at 48kHz 24bit.

Yeah, if the project is old enough, it will not have the QCEQ loaded and does show Gloss EQ (aka Quad Curve EQ) in the PC menu. I have not opened a file that old in years. If this is the case here, the install is OK. AFAIK, once added the QCEQ cannot be removed by DAWs that support the ProChannel. The QCEQ is treated a little differently from the PC modules.