Jonathan Sasor

As Dave Said, by default Cakewalk shows the driver pairs however the driver lists them in Windows, so in this case, as opposed to see 1/2, you're seeing "Left" and "right" for input "1". You can change the Preferences to show a "Friendly Name" as 1/2 if that helps, but functionally it's the same.

You just need to change the track filter:

Please try and capture a dump file for the crash and we can take a better look into what's going on. Details can be found here:

It appends what the name of the arrangement is after what you type for the file name. This is by design. That way if you export more than one arrangement at a time, you can tell them apart.

If clips select envelopes with clips is enabled, the normal drag/drop behavior should copy the clips and envelopes together correctly. Duplicate also works if the Edit Filter is set to Clips or you expand automation lanes. Both the clips and automation envelopes will be duplicated. In any case it should ultimately be duplicating the clips as well in that context, so it's a logged issue on our end.

The stack for the dump file is all within the plugin, you should try sending it to Sonivox. If there's anything on our end that needs to be tweaked, they can reach out and we'd be happy to look into it, but it seems like a plugin issue.

Plugin Layouts won't be affected by the update or rollback as they're user data. Those files are saved separately, and unfortunately if you saved over an existing layout, it's overwritten. You'll just want to be careful when naming your layout presets.

MIDI tracks can only have one output. You'd want to copy and paste the data onto another track for them to play the same parts.

2020.04 is not fully localized yet, which is why it's missing in Japanese. These options will be there in the final public release.

I'm just catching up to this thread now. If you've seen the 2020.04 Early Access threads you could tell things have been busy in the Bakery of late getting ready for the formal drop. @Mark Withers what you need should be right here: https://www.cakewalk.com/Support/Knowledge-Base/2007013201/V-Studio-700-Control-Surface-Plug-in-version-1-2-update# If you're running a VS-700 you should likely have a single sign on account to grab that link, but otherwise let me know and I can get you a link otherwise.

2020.04 builds have Ctrl + Alt + Space bound to Preview Play Arrangement From Now Time as a Global Binding. This is overriding your existing binding which is view-specific to the Event List. If you unbind the global one the Preferences, it should return to the 2020.01 behavior.

It's worth checking out (or at least reading the release notes) as we go through updates. We're certainly striving to increase stability with updates. Maybe if you've got a deadline "on Monday" you might want to hold off, but if you've got a couple months to go, it could be worth it to check out an EA. Maybe we fixed something that's been bugging you, or optimized performance on something. I actually used the early iterations of the Arranger to help write a song on a record I put out last month. The rollback is simply there just in case.

If you kept the previous releases' rollbacks, then this would theoretically work. There might be some minor differences related to content (presets and the like) by successively rolling back than if you had never installed the later updates, but the actual Cakewalk app will work per that given update after rolling back. The primary goal of having a rollback installer is that if we release an Early Access or other update that if you run into a blocking issue, there's a simple way to go back until we've been able to address the issue. In general we recommend sticking with the current version though. ?

This looks like you're using a custom theme. User themes will need to be updated to work with 2020.04.

The CTRL + wheel scroll direction got reversed as a side effect of another change. It's logged and on the list to fix before the final 2020.04 release

UPDATE: If you're not seeing the presets, the link for the EA installer has been updated on the original post. You can run the rollback installer, then grab the updated Early Access installer.

As you can see, it's been a fairly large bun in the oven! ?

We primarily test with Windows 10 (which is what the the large majority of users are on), but we still 100% support Windows 8.1 We stopped officially supporting 7 because Microsoft stopped supporting Windows 7. It drains resources when you have to work around functions that are not available in older versions of Windows. As is, we still do not prevent you from installing on Win 7. We just flag that to let users know that we're not going out of our way to fix any bugs that are specific to Windows 7. I mean, you could install CbB on Vista with the same message if you really wanted to, we just give you the heads up.

It's very much ongoing! We're just working on something that requires a little extra time in the oven right now.

Depending on which SONAR install you're talking about, generally speaking, yes, running the uninstaller(s) for SONAR and the relevant plugin or sub-installers from Command Center will remove all the bundled content. If you just uninstall SONAR Platinum though, the content isn't tied directly to that uninstaller because much of that content has their own installers/uninstallers that you'd need to run. Yes you can continue to reinstall SONAR and/or it's previous content at any point via Command Center prior to installing Cakewalk by BandLab. The content is the primary reason to keep SONAR installed at this point. The main reason to install 32-bit plugins on a 64-bit system now would be more for previous project compatibility. Cakewalk by BandLab is a 64-bit application that can run most plugins through BitBridge. Some older plugins don't play well with BitBridge, and a 32-bit install of SONAR might work better in those cases. Generally though it's best to stick with everything in 64-bit. If you have both VST2 and VST3 versions of the same plugin, the only real reason to install the VST2 version would be again for previous project compatibility (although CbB can replace VST2 plugins with their VST3 equivalents when possible). The actual location of the VST2 is not that important so long as you pay attention to where that is with your plugin installers and make sure it's in the Preferences in Cakewalk. VST3 plugins have a universal global location, C:\Program Files\Common files\VST3.

ProChannel modules install to the global Shared Utilities for Cakewalk. The full core installers for Cakewalk (or SONAR) should always replace the stock modules which include the PC76 and PC4K compressors as well as the Tube Saturation. The actual .dll files for the modules are not obviously named though. The VST Scanner should automatically scan the folder for these behind the scenes without it listed in Preferences, although you can see the path listed if you look in the Options via the Plugin Manager.

The UI is working normally on my side for everything (tried a few different installs/configurations), which would lead me to believe that something is weird locally on your system that would cause that to happen. You could maybe do a rescan/reset for plugins and see if that helps first.

Aside from the GUI, it should not be possible in the current build to have both the PC76 and PC4K compressors inserted in the ProChannel at the same time. This seems like there's something with your overall installation that is not working properly. You might need to try a clean install.

It should be fine on Windows 7. We haven't made any change that would adversely affect it, the only change for 2020.01 was popping the notification in the installer.

The .VST3 files should already be where they need to be. The VST3 spec added a common global VST3 folder to ease the confusion that can happen with VST2 plugins that do not have a common shared folder among vendors. All .VST3 files install to C:\Program Files\Common Files\VST3. The VST 2 .dll files need to install to their separate common folder (the default for CbB being C:\program files\cakewalk\vstplugins). If your VST2 .dll files are located in the VST3 common folder, you should reinstall those and set them to a common path for VST 2 plugins (that's not inside the VST3 folder).