scook

Make sure a project is open when changing bindings.

Can't answer why but Eventide rarely sends update notifications. I did not get anything for this update. Often updates happen around the time they announce a new product so, I checked today when looking at Physion MKII.

In addition to releasing a new plug-in It appears Eventide updated all their plug-ins on Aug 30. Installers available here

Given the crash was coming from M1.dll there is not much insight BandLab can provide. Unless the problem is repeatable on their end, it is unlikely any support group will be very helpful. I have seen some reports where a plug-in will crash if the ExceptionHandlingSeverity in Preferences > File > Initialization File is set too high. The default value is 1 and should be left at 1 unless debugging a specific problem. Sometimes bad plug-ins can have a knock-on effect. This is when some safe-mode sleuthing is necessary. Hold down the SHIFT key while opening a project to open in safe-mode. Sometimes this is enough to get a project to load OK. Sometimes stepping though all the plug-ins, allowing them to load one at a time is enough. Sometimes it takes skipping one or more plug-ins before the "crashing" plug-in loads correctly.

Should be OK. Download the Cakewalk Installer from the bottom of this page and install CbB using it.

It depends. Simply running uninstall and re-installing does not affect the registry or user modified files on disk. Running a clean install includes steps to remove registry entries used by CbB and all Cakewalk software (step 5), remove the user directories for CbB and all Cakewalk software "%appdata%\Cakewalk" (step 8) and remove everything in "C:\Program Files\Cakewalk" and "C:\Program Files (x86)\Cakewalk" which could include all Cakewalk software and any third-party plug-ins installed in "C:\Program Files\Cakewalk\VSTplugins" (step 9).

The item circled in red is a MIDI activity meter and has nothing to do with audio. The image shows a project with one MIDI track with its output and channel set to TTS-1 BUT there is no audio track for the TTS-1 audio output. Add an audio track and set the input to TTS-1. The channel assignment in track 1 is not necessary. Alternately, when adding TTS-1 to a project add it using an instrument track. An instrument track is an audio+MIDI track pair that presents itself in the project as a single track. Or the best solution as long as Preferences > MIDI > Devices has no output device selected: use File > Open to open MIDI files instead of importing the MIDI file into an existing project. This will automatically add TTS-1 to the new project set up ready to play the opened MIDI file. This is the best solution for playing MIDI files because importing MIDI files into an existing project strips out some MIDI data such as tempo. Opening a MIDI file does not strip data like the import process does.

The transport shows the Record Bit Depth setting

The ellipses indicate there is at least one clip to the right. Not a big deal in this case because the clips are also visible, but this can be useful when the clips in the track are not visible. There is no option to suppress them. Some set their color the same as the track background, so they fade into the background.

The manufacturer presets are not loaded correctly in the PC plug-in. In addition to turning off the PC, the output level is zeroed, and other controls are not set as they are in the regular VST plug-in. This is part of the reason I believe the problem lies with changes made to CbB 2020.04. Instead of delete and re-instantiate try using the "--Full Reset--" PC preset to recover the PC. Yeah, this is really not comparable. The regular VST format works as expected in CbB too. As I mentioned in one of the updates my post above, the issue is not unique to the Softube FET compressor but can be seen in other Softube and Boz Digital PC modules. I believe this issue was introduced with the CbB 2020.04 per-PC module presets. Prior to that, there was no way work with presets for individual PC plug-ins unless the PC module contained its own preset manager like BREVERB. For now, if one really wants to use the factory presets in the PC, open up the presets in the VST plug-in, copy the settings to the PC and save PC specific presets. Of course, because the controls are not identical, some factory presets may not make sense for the PC. Update: reported to BandLab as a bug

I don't have a problem with the GR meter but loading presets is a problem. Can't say I have ever bothered with the presets. I also tested with an older version of the compressor (v2.4.83 from 2019), it may have never handled PC presets properly. Individual presets were added to CbB in 2020.04, around the time when Softube v2.4.96 was released. With v2.4.96 all the Softube PC modules started crashing and continued to be a problem until v2.5.39.0 around April 2022 when Softube fixed the crashing problem. Softube is likely unaware of the preset problem. Update: The preset problem is not limited to the FET compressor. I just ran through a few presets using the VST2 and PC versions of TSAR-1R. The PC reverb fails just like the PC compressor. It appears Softube still has some work to do on all their PC modules. Update 2: I am not sure if the per-module preset feature added in CbB 2020.04 works with any 3rd party PC modules. I just took a look at Boz Digital +10db and Hoser XT EQs. Preset seem to fail with these PC modules too. Update 3: After messing with this a little more, it appears the problem may be with how CbB is processing manufacturer supplied presets. Creating and loading new presets seems to work OK. If I had to guess, the problem may be due to the layout differences between the PC and VST plug-ins.

It depends on the plug-in. Most plug-ins capable of accepting MIDI data have "Enable MIDI Input" automatically selected causing the plug-ins to show up in MIDI track output drop downs. Some plug-ins require the user to configure the plug-in itself to use MIDI data and manually select "Enable MIDI Input" in the VST2/3 drop down in the plug-in standard header before the plug-in appears in MIDI track output drop downs. Then there is the issue of an incomplete MIDI implementation in the original VST3 spec and slow implementation of updates to the spec by plug-in manufacturers leading some users to stick with VST2 for certain applications. I do not have any IKM plug-ins to test.

If you are trying to control Amplitube 5, based on the image above the track 1 output should be set to Amplitube and not Axe I/O.

Please provide more than symptoms when asking for help. In this case, keyboard make, model and if the device is connected to an audio interface using a 5 pin DIN or directly connected to the PC using USB would be good to know. Whether a MIDI keyboard appears in CbB depends on if the keyboard was connected prior to starting up the DAW, how the keyboard is connected to the PC and if it requires driver.

Yes, the VST2 dll pulls double duty as a regular VST and PC module just like the Cakewalk CA-2A. And just like the CA-2A the plug-in UI depends on where the plug-in is instantiated.

that seems wrong, all my vst3 korgs have the .vst3 extension in that location (as opposed to .dll in the vst2 path) I believe this is a typo or miscommunication with KORG support. Even though they are actually dynamically linked libraries, all VST3 plug-in binaries MUST have a vst3 extension. Files with a dll extension under "C:\Program Files\Common Files\VST3" are support files and are not scanned. AFAIK KORG does not have any files with a dll extension in the VST3 area. Like most manufacturers KORG permits users to specify where VST2 plug-in should be installed, however; some of their installers also put a copy of the VST2 binaries in "C:\Program Files\Common Files\KORG\Collection".

It might be the one in CSC. All the bundled CSC content came from DP and Rapture. I can't imagine anyone using CSC if they had DP/Rapture unless the program came from a CSC expansion pack. I purchased one CSC Expansion pack but instead of using it in CSC, I moved the samples to my Rapture folder and reconstructed the programs in Rapture.

This is usually because a project is open. The MIDI driver mode cannot be changed when a project is open.

SONAR Home Studio (later versions), Artist, Professional or Platinum all included a 64bit version of Rapture Session which can load and play CSC programs. Running the Rapture Session installer after CSC will automatically pick up the CSC programs making them available in Rapture Session.

Scrub Tool Keyboard shortcut J toggles the tool

The ASIO driver is an audio driver. The MIDI driver mode has nothing to do with the audio driver but can prevent the DAW from seeing MIDI data if it is set to the wrong MIDI driver mode. Check the link in my previous post for more info.

Not in my experience. Here is an example of a clip containing notes of different durations all set to two beats by directly entering the value in the Event Inspector

They may be reverting to the historical update schedule used when SONAR was active. The local help and User Reference PDF are reformatted snapshots of the web-based documentation. The web-based help received updates between releases and with every major release. The local help (re-introduced with 2022.06) was synced to the web-based help every major release. The User Reference PDF was updated less frequently often skipping several releases between updates. Something that has not happened since the introduction of CbB is the integration of the "What's New" section into the main body of the documentation. Prior to SONAR Artist/Professional/Platinum series, this was done with every new product release (ex. X1 to X2). During the SONAR Artist/Professional/Platinum era, it would happen every year or so. Now that all three documentation formats are back, it may be time for integrating "What's New."

After creating a track template, using something like autohotkey can reduce adding the template to a project to a single key combination. The following autohotkey snipped uses Windows+SPACE to load my Guitar track template into a project (note: I keep all my templates is a folder called "Custom"). #space:: Send,!it WinWait,Import Track Template Send,Custom{Enter} Send,Guitar{Enter} Return

Are SONAR and CbB using the same MIDI driver mode?