scook

May be video card/driver related. I am the last one you want to talk to when it comes to hardware but consider posting info about the video card and driver. I am sure someone can help. Also may benefit from running latencymon.

It may be easiest to Reboot Uninstall then reinstall CbB If that fails contact support@cakewalk.com

Those are plug-ins from the 32bit DX format Cakewalk Audio FX1 bundle. 64bit hosts like CbB cannot load 32bit DX plug-ins. If you want to open the project with the plug-ins included you will need to install a 32bit version of SONAR.

Review Playback and Recording settings in preferences. Aftertouch is not recorded by default.

It takes no specific tools to create a CAL script. The files are text files which may be opened in any text editor. There few guides available and the feature was deprecated over 20 years ago. Best to always use a copy of the MIDI track when working with CAL. It appears that http://www.midi-kit.nl/ has moved to http://members.ziggo.nl/odw/en/index.html. This site is a pretty good resource. There is a CAL guide pdf on http://members.ziggo.nl/odw/en/indexmidi.html which is useful. Softpedia still has the CAL Editor available for download. I don't care for the editor but it includes a CAL reference in chm format which I used a lot when working with CAL. All that said, putting a lot of effort in CAL at this time is not a wise use of time. It was abandoned in 2000 with the first release of SONAR.

There were very few monthly exclusives. They were always packaged in separate installers. It appears the original Anderton Collection was dropped from distribution. It had its own installer - AndertonCollectionSetup_1.0.0.25.exe. If you have the installer it should still work. Just run it manually. I had forgotten about that one. The 30th Anniversary Anderton Collection FX Chains, Modulator Chains and the CA-X Amps are still listed. Make sure to check the CCC settings page for any hidden products.

Add Chordz like you would any other synth. I recommend adding it using an instrument track. Set the input to your controller and enable input echo. Add the synth to control like you would any other synth. Set the input to Chordz and enable input echo. Configure Chordz and play on.

It's no older than the plug-ins and is way more compatible given it will run 32bit plug-ins natively. IMO, the best way to transition projects made in 32bit hosts. Once the plug-ins are swapped out with plug-ins that have 64bit versions, the projects are ready to run in a modern host.

If I had a bunch of old projects, I would install the most recent 32bit host available and use it to open and transition the projects to plug-ins that had 64bit versions. Creating new projects with old unsupported 32bit software is not a good idea.

BitBridge is bundled with CbB. jBridge may be purchased here.

The best was to run 32bit plug-ins is in a 32bit host. Use the 32bit host to aid in transitioning to 64bit. 32bit DX plug-ins cannot load into 64bit DAWs. That said, there is way to wrap them as VST plug-ins so the will actually load using the bridging tech for VST's but this tends to be unreliable and projects that used the plug-ins natively will not recognize them. Some 32bit DX plug-ins were ported to 64bit. These are all in the SONAR 8 installer. Use an advanced install of 64bit SONAR to get them installed. These plug-ins will work in CbB and replace any 32bit versions found in existing projects. There is bridge software to load 32bit VST plug-ins. It was intended as a stopgap measure so manufacturers could develop there 64bit replacements. Bridging is still available. CbB included BitBridge and jBridge is a low cost alternative which may offer better support for some plug-ins.

There is a CAL script to simulate strumming but I have never messed with it. When I need MIDI played like a guitar, I use a real guitar and play it through Jam Origin's MIDI Guitar.

There are several multi-channel frequency analyzers. Here is a video of MMultianalyzer showing how it displays frequency overlaps between tracks around 9:05 The plug-in occasionally goes on sale for 50% off through the year. All commercial Melda plug-ins have a full feature 15 day trial before they go into demo mode.

With the exception of the old LP-64 EQ and LP-64 Multiband everything is in the most recent installers. The last installer to include these plug-ins was Engineering FX Suite 1.0.14. Otherwise, there is no need to run any of the older installers.

Dragging an audio clip to the timeline builds a tempo map which is displayed in the Tempo view. To create a MIDI clip from an audio clip, drag the file to an instrument or MIDI track.

Most plug-ins work just fine in folders under C:\Program Files. The exceptions are plug-ins that write into the folder containing the dll. This is the case with a lot of plug-ins built with Synthedit. These plug-ins should be installed in an area where users have read/write access otherwise the DAW must be run as administrator.

Files with .vst3 extension are dlls. Regular dlls can be in the VST3 folder for a variety of support purposes. In fact, it is because of this the scanner was modified to skip files with the .dll extension in the VST3 folder.

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.

I recall some comments a while back that iZotope did very little to their VST2 plug-ins for the original VST3 versions. Don't know the current state of their stuff I have not updated in some time.

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.