scook

If the plug-in is just a dll, it should go in a VST2 path. Dlls in "C:\Program Files\Common Files\VST3" are not scanned. Of course, there may be more to it than simply putting the file in the scan path but not knowing anything about the plug-in other than its extension makes it difficult to discuss.

Sure, they have the code and the ability to do it, but it has been this way since its introduction. The knobs are visible when view is floated OR in the multidock.

in-app updating was added in 2020.09 in-app activation was added in 2020.11 BandLab Assistant is still needed to activate machines not connected to the internet.

For some time, the release announcements include a link to a rollback installer. Running the rollback installer reverts to the previous release.

To suppress all startup messages by disable Show Project Load Notifications in Preferences > Customize > Display To suppress the inspirational messages only create an empty ProjectOpenNotification.txt file in "%APPDATA%\Cakewalk\Cakewalk Core\". This feature was added in 2018.09. Links for new features change, the current link for this feature is http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.110.html

There is no performance advantage using either synth or instrument tracks. The only difference between freezing an instrument track and freezing an audio+MIDI track pair is where the audio is written. Instrument tracks display MIDI when unfrozen and audio when frozen. Audio+MIDI track pairs always display MIDI in the MIDI track and audio in the audio track. The audio track is the target for freezing, synth audio recording and waveform preview. The last two features are unique to synth tracks. Instrument tracks cannot perform synth audio recording or waveform preview, however; it is possible to split instrument tracks to reveal the underlying audio and MIDI track. Also, an audio+MIDI track pair may be merged into an instrument track. The split and merge options are in the track header context menu.

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.