scook

5 minutes ago, msmcleod said:

My recommendation would be to always use CbB's Preferences page to do your scans

Noel has been recommending this for years

It may be time to disable the scanner in the PIM when running CbB.

C:\Cakewalk Content\SONAR Themes

Probably no need to physically move the plug-ins. A directory junction in the 64bit path pointing to the 32bit path should work.

Running as administrators open a command shell and type

mklink /j "C:\Program Files\Cakewalk\Vstplugins\32bitPath" <enter the real 32bit path here>

Name "C:\Program Files\Cakewalk\Vstplugins\32bitPath" what ever you want in the current 64 bit path

Uninstalling will likely removed the shared folders used by SONAR and CbB. These include PC modules, all the DX plug-ins and utilities such as the plug-in manager and vst scanner.

As mentioned above removing the DAW itself does not free up much space but if you installed the Platinum tutorials run the Cakewalk Command Center, right-click SONAR Tutorials and delete them. It will free up almost a 900MB.

If you never archived and purged the Cakewalk Command Center download cache, now would be a good time. Click the Gear in the upper-right of Cakewalk Command Center to open its settings, click the Paths tab then click the folder to the far right of the Download Path. This opens the folder containing all the installers downloaded by the Command Center. Back them up, then delete the files. Depending on the last time this was done, this could free up a lot of space.

Check out the Matrix View

Several drum plug-ins has this feature.

53 minutes ago, jude77 said:

The first computer I ever bought used floppies that held 1.44 megs. 

fixed

Another thing to try is adding the 32bit plug-ins to the 64bit folder that is getting scanned.

or

C- created a project without a master bus. This happens when a user starts a project without using a factory supplied project template or their own template where they failed to add a master bus.

7 hours ago, Robert Bone said:

I TRULY do not understand why this has suddenly gone belly-up like this - for the approximately 10 32-bit plugins I need to be properly detected.

Did you try  copying the records from the Platinum VST Inventory to CbB? May want to export the Platinum registry as a backup.

Email service for the old Cakewalk site was shut down when Gibson closed the company.

CbB supports mp3 export.

I do not know if support@cakewalk.com can send out the old Cakewalk mp3 unlock program.

The track volume fader is after the FX Rack and Prochannel so, lowering the volume fader does not affect the signal going into the plug-ins on the track. Refer to the signal flow diagram.

5 minutes ago, Colin Nicholls said:

Is there a way to customize the list of controllers in the PRV controller drop-down list?

Don't believe so but you may enter the number directly into value field.

Use this page in preferences for all VST scans and settings.

Only use the plug-in manager for exclude list and layout management.

FYI CbB and SONAR use the SAME scanner and plug-in manager on the same PC. Their VST inventories are in different places in the registry.

Make sure to do everything from preferences NOT the plug-in manager (except for exclude list and layout management).

Worst case you could copy the registry entries for the missing plug-ins from Platinum into CbB.

I don't use jBridge.

I ran a reset a couple of days ago and the few 32bit plugins that I have scanned OK.

Running a VST reset from preferences can't hurt. Make sure to create a scan log. There may be a clue about what is going on in the log.

The only recent change I know that happened to the scanner is it no longer scans dll in the VST3 folders.

May have to experiment with different driver modes in preferences. In Win10 the WASAPI modes are the first choice for class compliant devices.

That's right. When documented features seem to be unavailable check the Workspace setting.

It is a limitation of the Media Foundation engine. Switching to the old DirectShow engine enables the feature.

To switch the video engine, see https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Troubleshooting.08.html

Could be the algorithm Melodyne is using. Melodyne Essential and Assistant only work with monophonic audio. Editor and Studio can work with polyphonic audio. May need to open the clip as a Region FX and determine the best algorithm.

Here is a link to the old SONAR hardware setup guide. The instructions for SONAR Platinum work for CbB. Select the device you have or the closest model if yours is not listed.

For devices where the guide recommends MME, if you are running Win10 try the WASAPI modes first.

Often toggling the transport will also get past the error. I believe it is an unspecified write error coming from Windows. The subject occasionally came up on the old forum. For more reading on the subject Google site:forum.cakewalk.com General Error

Assuming you have the tracks already routed to the master bus, solo the two mono tracks track to bounce with the master bus as the source