scook

See the Recycle Plug-In Windows section in http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B07

have you applied the hotfix?

More than that, the 32bit version of EZD 1 does not work in 64bit hosts. Have no info on EZD 2. If using the fefault "Sort by Category" plug-in layout, VST2 plug-ins typically show up in the Uncategorized folder. There is no need to move the dll from the original install path. Just make sure the original install path is in the Cakewalk VST scan path in preferences. While in preferences, try a manual scan with the "Generate Scan Log" option enabled. Check the log to verify the plug-in is in there.

The build is shown on the About screen

A fix was released a couple of hours ago

Before one can proceed with installing X3 producer, the installers must be available on a local drive. This has always been the case. The detailed instructions for X3 are here. Once all the 02_SONAR_X3 parts are downloaded, starting part 1 will present the 64bit and advanced install options.

The website does not have CbB indexed. Until that is done, don't expect to see any of the CbB links in search results. For many pages, changing the product in the search result urls to Cakewalk yield the current pages. For example, searching for prochannel shows the following url https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=ProChannel.01.html replacing everything after "product=" in the url to the ampersand with Cakewalk results in the CbB page https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=ProChannel.01.html Of course, the older versions have fewer pages in common with CbB. That said, when the product substitution in the url does not return the correct page, the old page may still be of value. Often the information still applies. When it does not, the location of the page (IOW, the path immediately above the navigation buttons), section headers and terms used in the page provide clues on where and what to look for in the current documentation. Finally, if a subject is not found, it may be in new features. New features are best reviewed by scanning that part of the help directly.

Like https://www.softube.com/products/harmonics?utm_source=Softube+Newsletter&utm_campaign=b3a3e4e3a9-EMAIL_CAMPAIGN_2019_11_19_02_45_COPY_03&utm_medium=email&utm_term=0_97a92143ea-b3a3e4e3a9-33320817#/ says:

Make sure to only add folders that contain VST2/3 dlls. Never duplicate folders. In this scan path the second path is a duplicate because it is already in the scan path as it is under the first path. That said, check exactly where the spicy guitar dll is located. That is the path that should be scanned. Added unnecessary paths and scanning areas that do not contain plug-in dlls can create problems. Usually VST2 plug-ins have an option in their installer for VST2 install path and display where the plug-in will be installed. You could uninstall then reinstall the plug-in and see where the plug-in dll is actually installed. It may be in one of the first two paths in the image or it could be somewhere else. As far as CbB and its scanner are concerned, it does not matter where plug-ins are installed as long as the plug-in dll is in the scan path. A scan log may help. The option is shown on the preference screen above.

50 unless it was previously set to 20 by the early release. Participants in the early release will need to change the value manually if they want to set it to the current default.

No, bit depth settings in Preferences > File - Audio Data have nothing to do with CbB internal processing. They affect the bit depth of audio clips created by the DAW.

Shouldn't this read - Record bit depth is a global setting, not a per-project setting. Projects may have clips at different bit depths.

I have not tested soft synth audio recording but my guess is any time audio is recorded, it is performed at the current record bit depth. Bounced, exported and frozen audio uses the render bit depth setting. These values may be set at any time. Unlike sample rate, projects may have audio clips at different bit depths.

The transport module shows the Record Bit Depth not the Audio Driver Bit Depth

Run BandLab Assistant Click the Apps tab Click the Cakewalk Update button According to the only setting that will change is Plug-ins and other setting will be the same as before the update.

Impulse Response files need to be loaded into an IR player. After a quick glance at the Ownhammer, it appears they only supply the IR files. CbB comes with a version TH3 which has IR Cabinet component and REmatrix Solo an IR Reverb. I don't care for either when using 3rd party IR files because both plug-ins must import the files rather than simply reading them from disk. Instead, I would use one of the IR plug-ins from MeldaProduction. MConvolution is free and the license for the MXFreeBundle is only $28. Yes, the bundle is free but purchasing a license comes with benefits, see https://www.meldaproduction.com/MFreeFXBundle Another free IR plug-in is Convolution XT. I have no experience with it but it looks pretty good. The IR plug-in goes in the audio track FX Rack. Still that just covers the cabinet IRs, still need to figure out what sound source to use for the guitar and amp. I will leave that to users that rely on plug-in tech for suggestions. When I need a guitar sound, I record it. I might go through an amp sim like TH3 which is bundled with CbB.

Make sure to save the file as a Cakewalk project instead of a MIDI file. Opening a MIDI file causes the default save to be a MIDI file. MIDI files only save MIDI data so, they cannot contain references to plug-ins used in the project. Saving as a Cakewalk project does. If you believe there is MIDI data resetting the plug-in in a Cakewalk project, check out the data in the Event List View.

Don't think it matters that much either way

Try adjusting the Buffer Size slider under Mixing Latency in preferences

Yeah, the CA-2A was part of the purchase.

I can find no reference to Toontrack releasing this in VST3 format. I usually only install VST3 when given the choice and I only have the VST2 format installed. Just ran the update to be sure. Can't say anything about the other Toontrack plug-ins, SD3 is the only one I own.

They have and the CA-2A is not the only example. All the "half-rack" series originally bundled with Project 5 and included with several versions of SONAR are 64bit plug-ins with 32bit data paths. Alternately, several releases of SONAR included a third party plug VC-64, a 32bit plug-in with a 64bit data path. When introduced in SONAR 5, both 32bit and 64bit versions of SONAR supported the 64bit DPE option.

Already drifted pretty far from the subject of this thread. May want to create your own thread. I am sure you will get a lot of good input from those who keep up with hardware.

This is a pretty good article on sample rate and bit depth

BTW, this may be something to consider