scook

So does Arturia, AAS, Cakewalk, Plugin Alliance, Softube, u-he and Valhalla to name a few. And since the path is part of the spec, most of these manufacturers don't provide a way to override the default path.

Yeah, it is surprising how many dump their plug-ins in the VST3 root. I am a fan of dedicated manufacturer folders.

trying to cut down on duplicate posts

Yeah, it appears that somehow Toontrack is putting their plug-ins in the VST3 path. This is wrong. A change was made to CbB 2020.01 to skip dlls in the VST3. This change was made because manufacturers have taken to adding support dlls in the path. There is an ongoing discussion about this here I believe it was started in reaction the the thread I linked above.

AFAIK, ALL files with vst3 and dll extensions in the scan path will get scanned EXCEPT in the dedicated VST3 folder where dlls are skipped as of 2020.01. The iZotope VST3 plug-ins all scan and load using the vst3 extension. The dlls are called from the vst3 files. For true VST2 plug-ins in the VST3 folder, it is possible to force them to scan in 2020.01 by adding a directory junction in the VST2 scan path. I would advise against adding the entire VST3 folder but adding specific folders like C:\Program Files\Common Files\VST3\Toontrack should be OK. IOW, running a command shell as administrator in C:\Program Files\Cakewalk\Vstplugins and typing mklink /j Toontrack "C:\Program Files\Common Files\VST3\Toontrack" I tested this by moving my Toontrack folder under the VST3 folder and it scanned OK. Still think it would be better to move/re-install VST2 dlls to a path outside of the VST3 folder though.

As long as a VST reset is not run existing VST2 in the VST3 folder should work. If a VST reset is run, the registry entries will be removed and the plug-ins will be skipped during the scan.

I have seen a couple reports of Toontrack plug-ins in the VST3 folder. Have not determined how they get there but Toontrack does not make VST3 plug-ins so their stuff should be installed elsewhere.

similar thread

ACIDized wavs refers to a type of audio file with embedded pitch and tempo information named after a DAW called ACID. In CbB they are also called Groove Clips. Here is some info about them http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Looping.01.html

Rather than use an EQ for its spectrum analyzer grab one of the excellent free spectrum analyzers analyzers. Span is a good one. So is MAnalyzer one of the plug-ins in MFreeFXBundle a free collection of useful tools and effects.

free plug-in https://www.codefn42.com/chordz/

CbB ALWAYS records the data at a track's input. The Transpose MFX can map MIDI notes to a scale. When added prior to recording a track with input echo enabled the effect of the plug-in may be monitored. After recording, applying the effect will alter the data in the track. Alternately, using a virtual MIDI cable can directly record the output from the Transpose MFX in realtime to another MIDI (or instrument) track.

I noticed in a post in the 2020.01 feedback thread someone has Toontrack plug-ins installed in the VST3 folder. This is a problem, see

I noticed in a post in the 2020.01 feedback thread someone has Toontrack plug-ins installed in the VST3 folder. This is a problem, see

Better still, archive the track. Audio tracks that are muted or routed nowhere still must stream their clips from disk into memory. Archived tracks take no resources at all except for the space they consume on disk.

Yes, the 32bit EZD does not work in 64bit hosts. IIRC, this was documented by Toontrack when they released the first round of 64bit versions of their software. At a minimum make sure the 64bit plug-ins are installed and the 32bit version are not in the CbB scan path.

This is why I said it was not an option in this case. Even though it is not a true ASIO driver, it looks like one to programs that work with ASIO like DAWs and this is a problem if there are devices with true ASIO drivers. There should only be one ASIO driver installed for any device.

If a device appears in Windows as an audio device but does not appear in CbB audio device preferences it is likely due to the choice of CbB driver mode in preferences.

Historically when Toontrack supplied 32 and 64bit plug-ins, the 32bit plug-ins do not work in 64bit hosts. Make sure the latest 64bit versions are installed and do not put the 32bit plug-ins in the CbB scan path.

For a device to use ASIO driver mode, it must have an ASIO driver or a wrapper like ASIO4All which presents WDM drivers to the host as ASIO. The manufacturer has chosen not to supply an ASIO driver so ASIO mode is not an option. You really don't want to add ASIO4All if you have another device with an ASIO driver as this can cause problems. Sounds like a plan. Pick the one that works best for the device/project.

Staying current is a good idea There is always a learning curve when working with a new DAW WRT auditioning audio, if the loops are not acidized wavs or rex files, make sure Preview At Host Tempo is turned off. The option in on the Media Browser Menu "B" in the image below.

Was the initial CbB release 2018.04 The duplicate clips feature referenced in the link above was introduced in 2019.09 VbB was a typo. Should have been CbB - Cakewalk by BandLanb.

IDK http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.14.html all works for me in CbB 2020.01 What version of CbB are you running? The version is shown in the About screen.

Instead of trying to configure any FX as a synth use the Enable MIDI Input in the VST3 drop down. This will cause the plug-in to appear in the output drop down in MIDI tracks

Change the driver mode