scook

Yes, CbB 2020.01 works on Win7. As you have seen there is notice when installing on Win7. This is more effective than an email because delivery is guaranteed. Development on Win7 stopped well before CbB and most testing has been on Win10 for about as long.

When trying to resolve scan issues, consider enabling "Generate Scan Log" before a manual scan or reset. The log may be useful if the recommended action does not solve the problem.

Sounds like a workspace is active. Then try something else.... Really this makes it tough to suggest a resolution. I have the impression that when the workspace menu is set to None, CbB handles views like Platinum (with lenses set to None) or the rest of the X series.

Clips like tracks have their own FX Racks The image shows an effect in a clip FX rack. Never had a plug-in work in a track FX Rack but not work in a clip FX Rack. The only difference is the clip FX rack only works on the associated clip; the track FX rack operates on all clips in the track.

Working online is not CbB, its is the browser based DAW called BandLab. Step by step instructions on installing CbB using BandLab Assistant are here

Clicking the UI is intended for auditioning audio. It is possible to record the audio though using synth audio recording. Instead of recording the audio directly, try using the virtual MIDI controller to record MIDI.

Have you made the appropriate manual offset to the reported ASIO for your interface?

I see no "Global Screensets" or "Screensets" entry in the worlspace drop down. Could these be something you created? The Screensets checkbox in the Workspace manager controls the availability of the screenset feature in the workspace NOT a method to create screensets that span projects.

If you created a Single Sign On account on the Cakewalk site in late 2014 though 2017, support@cakewalk.com should be able to help you regain access to your account. Since you may have product registration info, try running SONAR 7 as administrator to register.

One thing that may help is getting in the habit of closing all projects before shutting down CbB.

If you are sharing the same audio device for Windows and CbB, make sure the sample rate in Windows and CbB are the same.

Bounce to track(s) with Channel Format set to "Split Mono" gets the same result without the need to re-import the clips. That said, if mono processing is the goal, recording the two channels on separate tracks is best. Should the need arise to process the two tracks together route them to an aux track or bus.

I scanned the registry for presets like the ones mentioned in the OP. There were a few vocal presets but nothing useful. Maybe you are thinking of the Nomad Blue Tubes series. Since you have an image in your mind about what the plug-in looks like maybe reviewing images of the plug-ins bundled with Platinum may help. There are also pages containing images of the plug-ins bundled with X2 Producer and X3 Producer on the same site.

Aside from waiting on the audio driver, plug-ins may stay in memory. Most often caused by 32 bit plug-ins but not always.

There is no public facing bug tracker. Bug fixes are in the release notes.

How many plug-ins do you have?

This is a completely different question than the maximum number of plug-ins. Pretty sure I have seen threads about this graphics glitch before but have never experienced it myself. Consider reporting it to support@cakewalk.com. Include hardware and software details in the report. In the meantime try the plug-in browser.

Both the original 64bit Addictive Drums and 64bit Additive Drums 2 work fine in CbB, After validating the plug-in is in the scan path. click the Reset button in VST preferences with "Generate Scan Log" enabled. If the plug-in still does not show in in the synth plug-in list (make sure to use one of the "Sort By" lists supplied with the DAW), look for it in the scan log.

When a plug-ins has an installer, it is best to run the installer. This will insure the plug-in, its supporting files and registry entries are correct. I found the registry entries in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\SessionDrummer3 There is no space between Drummer and 3 The default Content Folder entry is C:\Program Files\Cakewalk\Vstplugins\Session Drummer 3 This entry causes the plug-in to look into C:\Program Files\Cakewalk\VstPlugins\Session Drummer 3\Contents The default Resources Folder is C:\Program Files\Cakewalk\Vstplugins\Session Drummer 3\Resources

Workspaces are global. They are stored in %appdata%\Cakewalk\Cakewalk Core\Lenses Screensets are stored in project and project template files.

That's how it's done. But work safe until you are sure about what you are doing. Move the folder to a different location. Usually a project folder contains: one or more related project files an Auto-save copy of each project (if auto save is enabled) versions of the projects (if versioning is enabled) an Audio folder containing the project audio a Melodyne folder containing RFX Melodyne data a MixScenes folder containing mix recall files The project will still show up in the Start Screen and recent file list until it gets bumped off the lists.

Cakewalk does not have a delete project function. It is pretty easy to use the OS to delete projects as long as they are created one per-folder.

Use paste special with only Track/Bus automation enabled

OK, I spot checked playback from Platinum 2016-12 through current and it works the same. It appears that playback does merge stereo signals to mono, record does not. I have filed a bug report for this. Currently to get playback split takes two sends, one panned hard left and the other panned hard right. This will not merge the channels on playback. Rather than mess with patch points, I would use bounce to trackss) on the original track to create mono tracks or record the two channels as mono tracks from the start.

After creating a track with two completely different sounds on each channel I changed the track output to a patch point Added new tracks w/ with one with input set to left patch point, the other with right patch point Recorded the new tracks. Each track recorded the appropriate channel from the original track. Here is an image of the result of recording the mono patch points into two new tracks.