scook

This is easy to test. Roll back to the previous version. In every new release announcement is an installer to revert to the previous release. See for the 2021.09 rollback installer.

If bounce to clip does not re-enable the Region FX option, may want verify the Melodyne license is activated. The info is available on the help menu.

If this is the version bundled with CbB, it sounds like the trial period has expired. When the trial expires, only monophonic audio to MIDI and tempo detection continue to function.

CTRL+M opens selected clips in Melodyne as a Region FX. This requires the VST3 format of Melodyne. Verify the VST3 plug-in is installed. It does not work with the VST2 plug-in.

From Preferences run a VST Reset with Scan in Sandbox and Generate Scan Log enabled If the log does not help may want to post an image of your scan path from preferences.

This makes a difference. Looks like a bug to me. I'll report it.

I checked before posting and had no trouble using quick groups on the output drop down in the track inspector. Of course, the tracks need to be selected first.

Quick groups work in the track inspector and track headers in the track view just like the console view. Select the tracks then while holding down the CTRL key change the output dropdown. If the output drop down is not showing in the track headers, it is either: the workspace setting the track control manger dropdown setting

This has nothing to do with plug-in UI. The buttons are in the standard header added by the DAW. Ignore the red box around the VST3 drop down, I lifted the first image of the standard header found in the documentation. The answer to the subject is there is no mute button in the standard header. It is a feature request. Feature request belong in https://discuss.cakewalk.com/index.php?/forum/8-feedback-loop/ Unlike mute, all the existing functions in the standard header have something to do with the open plug-in UI.

Keep in mind the desktop may be powerful but that does not necessary translate into a good DAW solution. DAWs want a processer with a lot of cores and a fast clock. Xeon processors are not a great choice for DAWs. Audio dropouts always have an accompanying message displayed at the bottom of the screen. This message contains a drop out code and a link to the help. In 2021.06 an additional parameter to ignore certain drop out conditions was added to Aud.ini.

Cakewalk.com is the old company website. The server is in read-only mode and made available as a service to customers who purchased Cakewalk products. It has been that way since the BandLab purchase in 2018 and created this forum. All the information I provided about support is from this forum. The links are from the Frequently Ask Questions area. There is also a link to support under Help on the CbB main menu

Once "Enable MIDI Input" is selected, the first step in my post above, the plug-in is added to all MIDI track output drop downs. Similar to how selecting "Enable MIDI Output" adds a plug-in to MIDI input drop downs.

There is no need to ever configure an FX as a synth. This option goes back a long way but has not been necessary since 2013. All that effectively does is automatically turn on "Enable MIDI Input" at the cost of removing the FX from the FX plug-in layouts and adding the plug-in to the synth layouts.

If there is no dump in %appdata%\Cakewalk\Cakewalk Core\MiniDumps try setting ExceptionHandlingSeverity to 7 in Preferences > File > Initialization File For more info about the setting see the Improved plug-in exception handling / crash reporting section of http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.024.html If a dump gets created see this reply in your other thread

From the Cakewalk by BandLab menu at the top of this forum https://help.cakewalk.com/hc/en-us

Contact @Jim Roseberry https://studiocat.com/opencart2/

I do not have the plug-in or hardware to test. To control any FX plug-in that accepts MIDI input. the plug-in requires Enable MIDI Input selected in the VST drop down in the standard header above the plug-in UI. A MIDI track with its input set to the device sending the MIDI data, its output set to the plug-in and input echo enabled. The plug-in may require some configuration too, such as mapping the incoming controller data to functions in the plug-in. Note: Soft synth have "Enable MIDI Input" selected by default, effects do not. Effects that cannot use MIDI data have "Enable MIDI Input" disabled.

This is just plain wrong. There is only one type of instrument track. It is a presentation of an audio+MIDI track pair. The inspector for an instrument track has two tabs. One for the audio track and one for the MIDI track that make up the instrument track. The video does not show It shows opening the MIDI tab in the instrument track inspector. The audio tab has the same FX rack that is shown in the Track View. The MIDI tab has the MIDI FX rack for the instrument track, however; it is not shown in the Track View. This is what the OP claims he meant by In the Track View, instrument tracks also hide the MIDI output so the MIDI inspector tab is handy when adding a drum map to an instrument track.

They are the full installer for 2020-11 and the update installer for 2021-01. Anything from BandLab in the downloads folder may be deleted. I like to copy them somewhere just in case, especially the full installers.

It appears the channel strip 2 and bus compressor have been updated to 1.0.55 SSL 360 is now at 1.2.15.48615

Both audio and MIDI fx racks are accessible in the inspector

review the driver mode and audio devices settings in preferences If running Win10 try the WASAPI driver modes.

The first thing I would try is force CbB to run the onboarding wizard. To do this edit the registry and set OnboardingShown to 0 in HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core Some Dell computers run a program called “Dell SupportAssist Remediation” which has been identified as a resource thief. See

Yes, the Focusrite interface should have the ASIO driver installed and the DAW should be setup to run in ASIO driver mode. That said, most of the 200ms may be due to Plug-in Delay Compensation. If see if plug-ins are the issue, bypass all plug-ins using the FX button in the Mix Module. While reading about this also review the help about PDC button.