scook

Yes, the process has not changed in years.

It requires modifying the registry.

To make it easier, I wrote Tools Editor to add almost any type of file to the tools section of the utility menu.

The main thread for this is

A link to Tools Editor and other utilities are in the original post.

If you have any questions about its use please post in that thread.

I don't bother with the PDF.

Instead use a web browser to search the index of the web-based help. This is usually enough to find the appropriate page.

While the keyword search returns all the SONAR documentation, using the "SONAR Platinum, Professional and Artist Documentation" filter often returns a usable page albeit for an older product. Often the current page can be brought up by swapping the product in the url from SONAR to Cakewalk.

32 minutes ago, Jack Hawk said:

is this something that changed in CbB?

no

To monitor though the DAW, recording tracks must have input echo enabled. The button to the right of the track record button.

The hot spot is the flag at the top of the marker. Notice the change from the magnifier to the marker cursor

The Arranger is a pretty big feature and will probably result in a pdf update.

You are welcome. The recording/mix quality will be fine, the problem with MME is the  time it takes from plucking a string or pressing a key and hearing sound from the DAW.

The last Reference Guide PDF update was made for 2019.09. The online help is current http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.02.html

AFAIK, this is the default behavior.

It may be altered by setting SendLocalOff to 0 in %AppData%\Cakewalk\Cakewalk Core\TTSseq.ini

For more info see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=INI_Files.5.html

2 hours ago, Ian O Donnell said:

There are no audio devices for the current driver model on your system please go to edit preferences etc to choose a different driver model. Thats the issue its not giving me any.

The driver mode in the error message refers to the screen below. With the internal audio chip try the WASAPI modes if running Win10, WDM for older OSes and MME as a last resort.

Key+ is in the track inspector "Q" in the image below.

1. support@cakewalk.com

 2. The audio driver bit depth may be disabled if the driver supports only one bit depth. That said, the audio driver bit depth has nothing to do with the clips recorded in the project. The record bit depth is set elsewhere in preferences.

While all clips in a project must have the same sample rate, there is no similar requirement for bit depth. A project may have a mix of clips at different bit depths.

Is driver mode set the same in SONAR and CbB?

Add an available shortcut to the Notes | Show Velocity on Selected Notes only function in the Piano Roll View area in Edit > Preferences > Keyboard Shortcuts

There is a link in the help menu for keyboard shortcuts http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x18324

The direct link for PRV shortcuts is http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=KeyboardShortcuts.html#1886440

Keyboard shortcuts may be modified in preferences. Make sure to have a project loaded when using this screen. Change the Area to Piano Roll View to access PRV specific functions.

Are the Studio Instruments installed?

They have a separate installer.

To download and install

• click the menu next to the Open button in BA
• click Install Add-ons... for the optional installers
• select the item(s) to install from the dialog
• click Install

If they are installed, run a VST Reset from preferences.

BTW "C:\Cakewalk Content" and "C:\Program Files\Cakewalk" should not be in the scan path. Scan paths should be restricted to folders containing VST2 and VST3 plug-ins.

Typically "C:\Cakewalk Content" does not contain any plug-ins at all.

Having both "C:\Program Files\Cakewalk" and "C:\Program Files\Cakewalk\Vstplugins" cause the plug-ins in "C:\Program Files\Cakewalk\Vstplugins" to be scanned twice because the scanner recursively traverses the scan path entries and there are a lot of dlls in the "C:\Program Files\Cakewalk" directory tree that are not VST plug-ins.

No amount of changing audio drivers or interfaces is going to matter.

If you have not changed the Record Bit Depth don't expect the program to record at a different bit depth.

Understood, as the link above mentions, projects record using the record bit depth setting NOT the audio driver bit depth setting.

26 minutes ago, gstring said:

he Audio Driver Bit Depth setting is grayed out in CBL Audio Driver Settings so I can't make any change there to the setting, but it displays as being 24.

Many ASIO drivers work at one bit depth. Most often 24 bit.

2 hours ago, zaquria said:

Another issue moving Clips, If there are Envelopes at the start of a Track, I cannot move Clips Back towards the start because the Envelope prevents this happening.

After select all

• move the Now marker to be beginning of the earliest clip on the timeline
• Select From Now
• Click-Drag clips as far left as 0.

Or select the blank measures on the timeline to remove, enable ripple edit all then delete

1 minute ago, TheSteven said:

All Eventide stuff is iLok

dongle optional also supports  computer-based iLok

Required installers

• BandLab Assistant 55 MB
• Core CbB installer 566 MB

Optional installers (these are estimates based on previous installers although they should be close to the CbB versions)

• Melodyne 177 MB (Based on regular M4 installer)
• DrumReplacer 252 MB (Based on version bundled with SONAR)
• Studio Instruments 621 MB (Based on version bundled with SONAR)
• Theme Editor 19 MB (Based on version bundled with SONAR)

The documentation in PDF format is 42 MB.

Updates to the program are much smaller. For example the current early release is 21 MB. Updates happen around every 2 months.

Only support@cakewalk.com can reset passwords for user accounts on the old Cakewalk site.

Never known CbB or any prior version of SONAR to add CC events on their own.

If it is not coming from outside of the DAW, something MIDI-OX could determine, then it might be from a plug-in. By default, synths capable of generating or passing MIDI data thought them have "Enable MIDI Output" turned on.

This in combination with a recording track input set to Omni will pick up unexpected data.

The "Enable MIDI Output" option in on the Insert Soft Synth Options dialog and in the VST2/3 drop down above the plug-in UI