scook

The top one is used with VST3 format synths. The other is used with VST2 format synths.

Exporting at 24bit is less than the internal mix. Try with dithering and without. Try the different dithering algorithms. See if it makes a difference with your own projects. The "rule" is always dither when lowering bit depth but, it often makes no audible difference.

In addition to auto-save, set up versioning see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x20A26 File > Revert to select and load a previously saved version.

Groove Monkee includes a few in their MIDI packs.

I can't read the images but Zero Controllers When Play Stops is one potential source of CC data when the transport stops.

Freezing and Bouncing tracks - both of these apply effects and generate audio from MIDI using softsynths. Bounce can also mix down multiple tracks to a single track. Destructive edits - any time an audio clip is edited in a way causing it to be written to disk such as shortening a clip and throwing away the unused part (aka applying trimming). Destructively applying plug-ins. Normalizing a clip. Exporting files Internally, the DAW reads all the audio clips and gets all the audio data from the synths and mixes this together using 32 or 64bit math. This data is sent to the export process. By default, export uses the Render Bit Depth to write out the file; however, this may be overridden in the export dialog. If exporting a 24bit file, the extra info in the data stream has to be dealt with in some fashion. This means either truncating or dithering.

The audio engine runs at 32 or 64 bit depending on the 64bit Double Precision Engine setting in preferences. When the DAW creates files other than recording or importing, it uses the Render Bit Depth. Unlike sample rate, projects can have clips at a variety of bit depths. As mentioned before, the Render Bit Depth is used any time files are written to disk except when recording or importing. Recording and importing have their own settings on the same preference page. Use either 32 or 64 for Render Bit Depth. The default is 32. The Record Bit Depth should be set to agree with the Audio Driver Bit Depth. By default, Record Bit Depth is 16 but most ASIO drivers use 24. Some interfaces with built-in DSP are locked at 32. I leave the Import Bit Depth at "Original." Cannot think of a reason to change this. If necessary, the sample rate will be altered to the project sample rate but the DAW can handle clips at different bit depths. Dithering 32/64 floating point to 24bit may matter for some genres and listening environments but I have my doubts. That said, if this is the final export, dithering won't hurt. Try it and see. In some cases it may not even matter when going to 16bit. It really depends on the material and the final audio format. I rarely export 16bit anymore. When I do, I use dithering. Bottom line, dithering should be done at most one time. It is most often used when creating 16bit files but there is no harm using anytime the bit depth is being reduced.

Here is the section from the Adaptive Limiter documentation on its lookahead buffer The setting is on the expert menu.

Unless you plan on taking the export into another tool such as Ozone or and audio editor for additional processing, export to the bit depth you plan on using while listening. If exporting for additional processing, export at the render bit depth. Dithering, if done at all, should happen one time, when creating the final version of the file.

Record bit depth is used for ... recording new clips. Usually, this should be set the same as the audio driver bit depth. Render bit depth is used when the DAW creates clips by some type of processing such as freezing, bouncing and exporting clips. IOW, everything except recording and importing. Dithering is usually performed when going from a higher bit depth to a lower one such as 32bit to 16bit. So by this "rule" going from 32bit to 24bit one would apply dithering. That said, there is practically no audible difference creating 24bit files from 32bit (or 64bit) whether dithered or truncated. Do apply dithering when going from anything higher than 16bit down to 16bit. This often does make a noticeable difference.

No Bazille And it was updated this month

Using anything than needs an elicense? If so, this was the problem reported in this thread around on page 2

The image shows CbB with a very out of date theme.

SI is likely Studio Instruments, a suite of synths bundled with Cakewalk. Ezdrummer 2 is a considerable step up from SI-Drums. There is demo for it.

I do not have FL studio but my understanding of their product line is their plug-in are available in a proprietary format usable in their DAWs and as VST plug-ins for use in other DAWs. The VST format plug-ins are sold separately,

With tooltips enabled, hovering over the disk space meter shows drive being used.

FL Studio does not need its generic driver. They install it just in case there is no ASIO driver available. If you do not want to uninstall the FL Studio ASIO driver, if you rename it or remove the reference to it from the registry so that Cakewalk will not see it. You can always restore the file name or registry entry at a later date if necessary. The registry entry where ASIO drivers are stored is HKEY_LOCAL_MACHINE\SOFTWARE\ASIO There is one record for each driver. WASAPI exclusive has adjustable latency but will not allow any other program access to the sound chip while Cakewalk is running.

There are two generic ASIO drivers installed. They are likely conflicting with each other. Notice how the input on ASIO4All shows "Not Connected." If you must use a generic ASIO driver (not necessary for CbB) pick one and uninstall the other. Chances are ASIO4All is the better choice. That said, neither is a true driver. They both wrap Windows WDM drivers and present them to ASIO hosts as ASIO drivers. As mention above, WASAPI shared and exclusive mode may work better for Cakewalk. It does not require an ASIO driver.

This is not very helpful. Images of errors and setup screens mentioned above may be helpful

Bit depth does not matter. Sample rate does.

It's all about MIDI. Add the synth as an instrument or audio+MIDI track pair, load a preset from the synth preset browser and enter/record some MIDI data in the instrument/MIDI track.

The full expression in Using the Smart Tool om automation for Right-Click is "Drag to lasso select" This is the method I was trying to describe.

To delete selected nodes - lasso the nodes, hit the DELETE key

Maybe a slight fade in/out will help Check out these settings in preferences

I do not have the player but did install the full version of synthmaster. The only thing you will find in the plug-in list is the synthmaster plug-in itself. It is the only thing that needs to be in the VST scan path. All the other files do not need to be in the scan path. If you cannot find the dll, re-run the installer and pay attention to where the installer puts the VST plug-in. The installer should give you a way to specify where the VST plug-in is installed. Once the plug-in is scanned, add the plug-in to a project. The plug-in has its own browser to load the different sounds.