scook

I am guessing this still works (from http://forum.cakewalk.com/FindPost/3415475)

Have you tried renaming TTSSEQ.ini in the user directory? For CbB the user directory is %appdata%\Cakewalk\Cakewalk Core.

Yes, Cakewalk by BandLab started out with the unreleased SONAR Platinum 2017-11 code. CbB does not include all the plug-ins bundled with Platinum so, if these plug-ins were used in the project make sure Platinum is installed on the PC. CbB will use any plug-ins and content bundled with 64bit Platinum.

I checked out Wahman_x64.dll While the plug-in does not error during scanning, the VST Inventory entry in the registry is incomplete. I have seen this once before with VeeSeeVST Rack and the plug-in developer managed to fix the problem. May want to let NSP know. Maybe they can fix their plug-ins.

No, the step sequencer will not automatically load clips. It is up to the user to load the clip to edit into the step sequencer. Multiple step sequencer may be opened by locking them.

For now, create an audio track with empty clips. Use clip FX rack for a notes VST. Melda Production MNotepad and CodeFN42 VSTNotepad are free.

The thing is splitting individual notes whether MIDI or audio does not seem particularly useful except for the case where each note plays a different instrument. In the case of drums synths most kit pieces have several notes mapped to them. It makes more sense to map all the notes for a kit piece to one track. This can be done by taking the CAL script provided by Cakewalk and modifying it to create tracks based on the drum synth kit layout rather than one track for each pitch. As mentioned above, it is relatively easy to route all the notes that play different kit pieces to different synth instances. Both of these seem preferable to having multiple audio tracks for a snare or hi-hat.

When using Split Notes to Track CAL do not use instrument tracks and move the source track to the bottom of the project before running the script. Keep in mind a drum map may be used to send note ranges to different synths. This may be used to break out different kit pieces to separate instances of a plug-in. Once created, save the MIDI and audio tracks as a track template.

Here is an example of the Event Filter MFX removing all controller data

Here is a simple autohotkey script to launch the ASIO client while running CbB If autohotkey is installed on the PC this script may be launched directly from the CbB utilities menu. For this example, I created a file called test.ahk containing the script and using the ToolEditor (available on my google page) added the script to the CbB utilities menu with ALt+u+p as the keyboard accelerator like this Here is what happens when entering ALt+u+p Of course, this is a very simple example. It could be extended to include a UI for selecting different buffer settings and handle all the keystrokes necessary to deal with the ASIO client and close the CbB preference screen. For those who prefer not to install autohotkey, I could compile the script and provide the executable on my google page. The executable could be added to the utilities menu.

Probably still includes modules for the EQ and compressor

Cakewalk can do what you want. As with any software (or technical skill like music production) there is a learning curve. Plan on spending some time reviewing the documentation (it is also in pdf format) and videos. There is a tutorial section in this forum covering a variety of subjects, videos for similar products are on the old Cakewalk site (the Music Creator tutorials are gear for beginners) and Youtube. Whether it is a good fit for you is impossible for others to say. Recording will take some investment in hardware. What hardware are you planning to use?

Could be a failing mod wheel on the input device. It is possible to avoid recording CC data by unchecking Controller in MIDI record preferences. There are a variety of ways to delete unwanted MIDI data from clips. Here are three: Delete the data using the Event List or Piano Roll views. Both of these views may be used to directly access CC data. Add the MIDI Event Filter MFX to the MIDI FX Rack, filter out the unwanted data and apply effect. Convert CC data to envelopes and delete the envelope.

This type of issue is a little out of scope for the forum, it is a support issue. Here are instructions on how to handle the dump file create by this problem.

Email support@cakewalk.com or create a ticket directly using the submit a request on this page.

Melodyne Essential was bundled with SONAR X3 Producer/Studio and SONAR Platinum/Professional. Owners of those products who registered Melodyne should use their Celemony account to download the latest Melodyne installer. CbB provides a time-limited trial version of Melodyne Editor on the "Install Add-ons...." menu.

The Melodyne VST3 plug-in is what CbB uses when dragging audio to an instrument/MIDI track. It also supports other ARA2 functions such as creating a tempo map by dragging audio to the timeline and the Region FX function.

Might as well get used to clips. They are fundamental to the way CbB works. In fact, there are two different clip types that may be hosted in instrument/MIDI tracks: regular MIDI clips and step sequencer clips. They are similar in appearance and function but different in how the data is stored and edited.

In order to use plug-ins and content from Cakewalk (the Company) products requires running those installers. Old Cakewalk accounts are still active. The downloadable installers and Cakewalk Command Center still function. Some of the SONAR Platinum/Professional/Artist installers require actually installing the DAW before they will run. V-Vocal bundled with SONAR Producer through X2 also requires installing the DAW that included the plug-ins. The plug-ins bundled with Cakewalk by BandLab are detailed here. Keep in mind Cakewalk by BandLab is 64bit only so some older 32bit only DX plug-ins bundled with SONAR and other Cakewalk DAWs will not work in CbB (the same restriction applied to SONAR).

After changing drivers is the plug-in available?

The reset could have been performed after the re-install. A reset is a scan except it clears the VST Inventory and scans all plug-ins as if they were just installed. So, what is the status now? Is the plug-in available?

The Cakewalk documentation includes a section from the old SONAR documentation for an alternate method, however; the only method currently available for CbB is BandLab Assistant.

Try the Split At Selection option in the Split Clips dialog.

The log indicates a regular scan not a reset. No plug-ins were actually scanned according to the log. From the bottom of the log Instead of clicking the Scan button, click Reset

The scan log indicates the plug-in was skipped because it was previously scanned. Try running a VST reset with "Generate Scan Log" enabled. This will force a scan of all plug-ins including SSD5.