scook

ASIO uses one driver at a time. Some manufacturers supply ASIO drivers that can work with several of their interfaces at a time. AFAIK, there is no ASIO driver that works with multiple interfaces from different manufacturers. There are generic ASIO drivers that will aggregate interfaces. These drivers are nothing more than wrappers for native Windows drivers (WDM and WASAPI). These drivers were written to use with products that only support ASIO. In addition to ASIO, CbB supports native Windows drivers so there is no need to use a generic ASIO driver. Generally, these drivers should be avoided especially if a manufacturer supplied driver is available. Generic drivers are known to conflict with manufacturer supplied ASIO drivers. The Realtek ASIO driver has never worked well. When using onboard audio, WASAPI is the best choice for Win10 and Win11. Old OSes should use WDM.

There are two basic types of tracks in CbB - audio and MIDI. An instrument track is a simplified presentation of an audio+MIDI track pair. The term "synth track" refers to an audio track with a synth plug-in as its input.

Aim Assists line

Is the folder compressed?

no I fixed the link to http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.05.html thanks

The sample rate in preferences is used for new projects and any projects that contain MIDI data only Remove all the audio clips from the project and it will read the sample rate from preferences.

That does not matter if there are no plug-ins using the feature. By default, no plug-ins have upsampling enabled.

That's not the DAW, that is a driver issue. What version of Windows?

Yeah, upsampling won't matter. By default, no plug-ins are set to use upsampling. The user has to configure plug-ins to take advantage of this feature. So, you are using the native ASIO driver with the VST3 format of Waves Abby Road Reverb and no generic ASIO drivers are installed What version of Windows?

Projects without any audio use the sample rate from preferences. If the project has any audio clips, the sample rate is read from a clip header. If the clips are frozen synths tracks, unfreeze the track, close and re-open the project. If the clips are not frozen synths tracks, here is the process for changing project sample rate.

It may help to know the audio interface, driver mode and mixing latency setting.

If there are any audio clips in the project, the project sample rate is read from one of the clip headers otherwise the "Default Setting for New Projects" "Sampling Rate" is used. The transport module shows the Record Bit Depth NOT the Audio Driver Bit Depth

Download and install the driver for the insterface and set the drive mode to ASIO in Preferences > Audio > Playback and Recording

Not natively in CbB but autohotkey can do the job Here is the ahk script bound to WINDOWS+r

No problems here with X-Echo. Did you try both the VST2 and VST3? FWIW, they both work on my PC. Did you check the exclude lists for VST2 and VST3 in the plug-in manager? If they are in the exclude lists, in Preferences > File > VST Settings Enable "Rescan Failed Plug-ins" Enable "Generate Scan Log" Run a manual scan Disable "Rescan Failed Plug-ins" Reset the scan frequency drop down (assuming manual scan is not your normal setting) If they are not in the exclude lists, try either a VST reset from Preferences > File > VST Settings with "Generate Scan Log" enabled or if you prefer not to run a reset here is a method that will generate a much smaller scan log and avoid scanning everything Move "SSL Native X-Echo.vst3" and "SSL Native X-Echo.dll" out of the scan path Run a manual scan Return "SSL Native X-Echo.vst3" and "SSL Native X-Echo.dll" to the scan path Enable "Generate Scan Log" Run a manual scan Reset the scan frequency drop down (assuming manual scan is not your normal setting) Given the plug-in fails to appear in multiple DAWs, I don't hold much hope re-scanning will make a difference but doing so with "General Scan Log" enabled will at least provide some information about why the plug-in is failing.

The drivers shown in devices in preferences depends on the driver mode set in preferences.

TTS-1 is a DX format plug-in. DX plug-ins only work in a host that has the same bitness. IOW, 64-bit SONAR will not recognize, load or run 32-bit DX plug-ins. Unlike 32-bit plug-ins, there is no bridge available for DX plug-ins. The TTS-1 loaded in 64-bit SONAR must be a 64-bit plug-in.

The Sonitus plug-ins installed with 64-bit SONAR are 64-bit versions.

Glad it worked for you. Remember there is no one standard for mapping MIDI note numbers to pitches. There is a setting in CbB to adjust the pitch display called Base Octave for Pitches Usually, I just toggle the label frame (keyboard display) next to the notes pane in the PRV between note numbers and pitches Right-click the keyboard to display the Note Names dialog Select the "Use these Note Names Instead" radio button then Select 0..127 to display note numbers or Select Diatonic to revert to the keyboard

Here are a couple of CAL resources CAL Editor - I am not a fan of dedicated tools like this but it comes with a very useful CAL reference in Windows help format (chm). CAL Programming Guide.pdf

The scripting language looks like LISP but is very limited in what it can do. I use LISP mode in EMACS to handle syntax highlighting and paren matching. Yeah, it's a typo I'll fix it along with making the IF condition a little safer. BTW, once the scripts are created, it is possible to save some typing by binding the scripts to keyboard shortcuts. To bind CAL scripts to shortcuts use Preferences > Customization > Keyboard Shortcuts. The CAL scripts are near the bottom of the Global Bindings area functions list.

is a driver optionally installed by Cubase intended for users without an ASIO driver. Just like ASIO4All, it should not be installed when a factory supplied ASIO driver is available. Uninstall it or rename the dll or remove the Generic Low Lantency ASIO driver entry from HKEY_LOCAL_MACHINE\SOFTWARE\ASIO

AFAIK, there is no disconnect all function But it may go faster if the synth rack is docked in the multidock or floating because the power buttons are visible and may be used to disconnect synths instead of using the menu.

NoteMapper may not be the solution. Since this is not about using the data in the DAW, I might use a different approach. If I had a bunch of MIDI files that I wanted to delete notes from I might create a CAL script for each filter then Load a MIDI file Select All using CTRL+A Process > Run CAL and select the CAL script filter to run Use "Save Copy As" to rename the filtered file If I had more than one CAL script, hit CTRL+Z to undo the first script then repeat steps 3,4 and 5 using the different CAL scripts until done with the MIDI file Close the MIDI file Repeat all steps until all the MIDI files are processed. Here is a sample CAL script that deletes all notes values above 77 deletes all notes value below 60 deletes all note values 61, 70 and 75 deletes all non-note events Copy the script and paste it into notepad or any text editor Adjust the high, low values (values in green) and add as many notes to delete in the switch statement (lines in blue) as necessary Save to "C:\Cakewalk Content\Cakewalk Core\CAL Scripts" with a meaningful name such as organFilter1.CAL The name can be anything but the ".CAL" extension is important Create as many scripts as needed adjusting the values for each organ.