scook

If you really want to create/modify MIDI data programmatically, MIDICSV may be a good starting point. This converts MIDI data to a CSV file. It also includes a utility to convert CSV back to MIDI. The page contains worked examples in PERL but anything that can read a text file will work.

The DAW permits one sample rate per-project. Sample rate is set one of two ways. Whan a project has no audio, the sample rate is set by reading the default sample rate in preferences. The sample rate of these types of projects may be changed anytime by modifying preferences. When a project contains audio, the sample rate is read from one of the audio clip headers. Here is the documentation on how to change the sample rate of projects containing audio.

Don't have the plug-in but when I read about a problem with a synth that works OK until the transport is stopped, my first guess is the per-project Zero Controllers When Play Stops setting.

There is a free Kontakt player and a paid full version of Kontakt both work in CbB. Some sample libraries require the full version. Unless the sample library specifically says it will work with Kontakt player assume it requires the full version. The license fees developers pay for libraries that work in Kontakt player are higher than the fees paid for libraries requiring the full version.

Files with a .vst3 are DLLs. The .vst3 extension helps the scanner tell what to scan as VST3 folders may contain additional support DLLs along with the actual plug-in binary. is an FX plug-in just like the name suggests and not a synth. Part of a suite of FX plug-ins by LANDR.

This happens when re-installing without cleaning up the registry. Here are the clean install instructions https://help.cakewalk.com/hc/en-us/articles/360034066393-Clean-Install-Cakewalk-by-BandLab

WRT legacy installs nothing has changed since this post The last SONAR installer that included the Blue Tubes bundle was the Studio Mixing FX Suite for SONAR Platinum. If you don't want to deal with legacy installs pick up a license for the Blue Tubes Bundle from Don't Crack.

This may be the problem. Dial it back to 1 (the default). I only set it to 7 when troubleshooting.

I deleted the post, however; at the bottom of posts should be thumbnails of the uploaded images. There is a trashcan on the right side of the images to delete them. It is also possible to manage images by opening up My Attachments in your account.

I do not have either bx_MasterDesk True Peak or bx_rooMS but have no problems with other bx plug-ins including bx_MasterDesk. If you are not getting error messages in CbB, try setting ExceptionHandlingSeverity to 7 in Preferences > File > Initialization File

If you are using the drum map for kit piece names only, consider using the Instrument definition instead. Most of the drum map videos predate changes made to the DAW to support persistent alternate note names in the label pane next to the PRV note pane. Instrument definitions are easy to create and add to the master.ins file and one already exists for AD2. Once added, right-click the keyboard next to the PRV and load the names.

I am not sure if this requires an old Cakewalk account to access https://www.cakewalk.com/Support/Knowledge-Base/2007013364/Setting-up-a-Drum-Map-for-Addictive-Drums-2-in-SONAR I wrote an instrument definition for AD2

AFAIK, other than Cakewalk DAWs there is nothing that will open Cakewalk bundle files. @azslow3 wrote a tool to parse and load Cakewalk project files (.cwp) into Reaper. All DAWs use proprietary file layouts. Moving projects from one DAW to another usually involves exporting a MIDI file and generating audio stems for importing into the new DAW.

Keep in mind the project has only one instance of BFD 3. If CbB does not have any MIDI output devices selected, there is no way to set the PRV label pane to the keyboard. It will always display the BFD 3 drum names or names from an instrument definition. The OP needs to either enable a MIDI output device or add a softsynth that does not supply note names like BFD 3. There are only a few synths that implement the effGetMidiKeyName opcode.

Is this a fast or real-time export? If fast, try real-time or see if you can isolate the plug-in causing the problem. If real-time, bump up the ASIO buffer.

Stuttering is usually a buffering problem. Maybe a CPU load issue.

Here are a couple of posts from the old forum where Noel goes into more detail about the audio engine, bit depth and dither. From http://forum.cakewalk.com/64bit-Audio-engine-vs-double-precision-engine-and-a-dithering-question-Noel-please-m3804976.aspx and http://forum.cakewalk.com/Bits-Freezing-and-Dithering-m1204271.aspx#1204822

yes Size should not matter. It's a temporary file for mastering. Doubt it. Dither adds noise to mask any artifacts created by bit depth reduction.

When rendering at a lower integer bit depth such as 32-bit floating point to 24-bit or 24-bit to 16-bit. Going from 64-bit to 32-bit does not dither.

yes The dither setting is used only when needed. The DAW only dithers when necessary.

Put the render bit depth back to the 32-bit default and leave it there. Export using the default 32-bit. Load the file in the mastering software and dither to 16-bit when exporting.

Here are the changes needed to make an old theme current When modifying image sizes, you may need to restart the DAW to get them to display correctly. This was the problem with the archive button and the old theme. The old theme needs the 2021.12 archive button.

Don't worry about the mix of different clip bit depths. The DAW audio engine uses 32 or 64-bit floating point depending on the 64-bit Double Precision Engine setting. By default, the DAW is setup to render 32-bit. Why not let the DAW export at the default 32-bit depth?

Did you install the ASIO driver from https://www.allen-heath.com/ahproducts/zedi-10/? Here are the instructions https://www.allen-heath.com/media/ZEDi-USB-Windows-Driver-Help.pdf Once the driver is installed: reboot, run the DAW, select the ASIO driver mode in Preferences > Audio > Playback and Recording and select the zedi-10 in Preferences > Audio > Devices.

It seems you may have been using an out-of-date user theme. Either stick with the themes supplied with CbB, update the custom theme or use one of the themes published in the theme forum