Jonathan Sasor

I'm not aware of any issues with Focusrite interfaces right now. We did some testing with them a little while back, so they should be okay. If you're in a state where you can find a difference between the two apps, if you could provide a video showing the difference and your audio preferences per each app, that would be helpful.

Try seeing if you can run the installers manually from the Downloads folder. Click Install in BA, and when you see that the download completes but the installer hasn't popped up, you can navigate to the folder by holding the Windows key and pressing R to bring up the Run prompt. Type: %appdata%\bandlab-assistant\Downloads and click OK. Then if the installers have fully downloaded, they should run by manually clicking to launch the files.

The default project location for Cakewalk by BandLab (and older versions of SONAR) is C:\Cakewalk Projects as shown in your screenshot.

I run a VS-700 on Windows 10 every day, it should play back correctly. Do you get any metering when the tracks co silent or no? Also try seeing if it will play in WASAPI shared mode. See if you can hear anything if you toggle the global FX bypass in the Control Bar in case it is a plugin in demo mode.

The 2020.05 Rollback installer can be found here, however as I mentioned the other thread, there shouldn't be any compatibility issues with older projects. If you can provide more details on what you're seeing, we can troubleshoot what's going on.

You can also go to Edit | Preferences, VST Settings tab to change your scan folders.

There is a rollback installer listed with the product info page on this forum, but there shouldn't be any issues with opening previous projects. What exactly are you seeing? Do new projects create successfully?

That message is not coming directly from Cakewalk. I'd check what you have set for your VST scan paths, as it seems like it might be trying to load invalid plugins. That said, you should be able to click OK and continue to any project in Cakewalk because that's not a Cakewalk error.

If you can provide a dump file, we can check if there's any problems on our end or if the plugin is at fault

Plugin derived latency should behave no differently between SONAR Artist and Cakewalk by BandLab. As mentioned various plugins will introduce different levels of additional latency on top of what your overall hardware latency is set at. I'd be careful of making sure your configurations are set 1:1 between SONAR and Cakewalk by BandLab. We've done a significant number of optimizations that make the app a lot more streamlined. If you can provide a reproducible example where the latency handling is different between the two versions, we can investigate, but most latency problems I've seen boil down to either the project (plugins) or something the audio card is doing.

The Loop Construction View is not a Wave Editor as such. It's only going to show the selected clip when opening. If you want everything to be part of the same clip, you have to select all of the audio in that track and go Clips | Bounce to Clips. The real question is what exactly is the edit you're looking to do? That's going to dictate what's ultimately the best way to go about it. The Loop Construction View is geared towards tweaking a couple bars of something and then acidizing it where you can crop the clip for a number of repeats that are tied to the project tempo.

Piggybacking on what @scook said, Cakewalk by BandLab is the successor to SONAR Platinum, and will open your .wrk and .cwp from previous versions of Cakewalk products. You can download Cakewalk by BandLab via BandLab Assistant.

Actually, valid point, the files aren't being installed because the original FX installer did not have a provision for Portuguese or Russian. @Milton Sica and @Patrick Wichrowski, safe assumption your installs are Portuguese? We'll update this for BA shortly, but you can go ahead and grab this 2020.08 Update Installer. You can run it on top of your existing 2020.08 installation. I verified the problem and fix on my end, but please confirm. Thanks!

Assuming the .dll files are installed, you run the regsvr32 function on them. Go to Start/Run (or hold the windows key and press "r" and type: regsvr32 “C:\Program Files\Cakewalk\Shared Plugins\pluginname.dll” and click OK Each one would need to be registered manually. You shouldn't necessarily need to do a clean install either, if something was blocking the files from registering (sometimes pending windows updates or antivirus programs will block this). Re-running the same installer may succeed as well.

Are you sure you've got the right installer version? I just verified that a clean install process will install those plugins on Windows 7 (even though its not officially supported). If your Help | About page shows 2020.08, 0ne thing you could try is running the Rollback Installer to go to version 2020.05 and then use the update installer and verify it is the 2020.08 version by checking the file in C:\Users\Your User Name\AppData\Roaming\bandlab-assistant\Downloads as you download/run the installer via BandLab Assistant

It might be a logical conclusion if you're looking from only one perspective. I'm looking at Cakewalk every day across a few different machines both physical and virtual, and there is definitely no global issue with how the app or the installer writes things to the registry. If there were, I think this thread would be a lot more busy. You'd be amazed at weird behaviors that are manifestations of odd system behaviors/components. Hard drives fail. RAM goes bad. Drivers stop working. The CbB (or any DAW) is reliant on the platform on which its run. If something behind the scenes isn't right, it's going to impact the app. If there were a fundamental issue with how Cakewalk was handling something, you'd see a lot more than the handful of people who have said they're having an issue with any given update. When we identify issues in the app, we fix them as soon as we can. If there's a system-specific problem, it's literally out of our hands.

As these are not VSTs, they install to C:\Program Files\Cakewalk\Shared Plugins and then require being registered in Windows to appear. Were there any errors during the install process?

If you use the 2020.05 Rollback Installer does it launch normally?

There have not been any changes to plugin scanning in the past few updates. If the restore fixed it, something likely changed with your 3rd party installs that got corrected.

If you don't see either the progress bar (for updates) or the installer menu for Cakewalk popping up, you're not actually in the Cakewalk installer yet. It seems like a few people are seeing some issues with BA being able to launch the installer initially. Typically closing and restarting BA should resolve this, but otherwise you can manually launch the installer as @HIBI mentioned.

I'm not sure I understand exactly where your problem is, in trying your steps, when I go to Undo, I see the clip go back to its original length. Can you provide a screenshot or a gif showing your issue?

If you check the Plugin Manager, they should appear as DirectX Audio FX. If you had a previous SONAR install, you likely already have these plugins, but as mentioned, check your plugin layouts if you need to adjust those as well.

The standard VX-64 and PX-64 Vocal/Percussion strips are not (and were not previously) included with the installer. There are versions of these plugins that are leveraged by some of the Style Dials that do get installed. These versions are disabled on install.

You can do the Project | Insert method, or turn on Ripple Edit All and drag everything over by a measure. Both equally valid.

As Noel, said, the way the installer works is that it looks if those FX Chains are installed. If they are, it doesn't do anything. If they're not, it then adds them to the folder. Likewise it will not modify anything else that's already in that folder, which in this case would be the previous other FX Chains (or any user created ones).