Jonathan Sasor

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).

check your download folder for the correct file, hold the Windows key and press "r" to bring up the Run prompt. Type: %appdata%\bandlab-assistant\Downloads. If you do not see 26.08.0.100 in the installer file, delete what you currently have here. Then Exit out of BandLab Assistant, reopen/log in, then try the install again.

How a Jump in the envelope behaves is that there's no active changes to the envelope for the duration of the jump, then it immediately goes to the next node's value. this is as opposed to having either a linear or fast/slow curve. You could make the same behavior with linear curves, but you'd need to add more nodes and set everything up at right angles. It's just a different workflow option. Your project is creating jumps when using the draw too and drawing in spaces away from the existing envelope. If you for instance double-clicked the existing envelope to make a node, then dragged that, everything would stay linear. Or you could select a section of time and use the shelf tool (dragging from the top of the clip) if you wanted a straight linear "jump"... there's a few different ways to crack a nut depending on what you're trying to do in any given circumstance.

I'm not sure how else to explain what's included in the sub installers than saying they're plugins... not without just giving you a bunch of links to docs about all of these plugins which are readily available both in our documentation and many user driven tutorials docs that are out there. It's bonus content that used to be included with the paid versions of SONAR so that way you can use additional features immediately with Cakewalk by BandLab. They're broken into separate installers because that means you don't have to download and install them every time you do a Cakewalk update. Or maybe you don't like virtual instruments and want to save the hard drive space? Drum Replacer could still be handy there if you want to beef up a part though. Some people like to make custom CbB themes, you'll find a bunch of them on this forum or there's Facebook groups of people who share their own custom themes. Other people don't have an interest to make their own, in which case, you don't need to install it. Melodyne is only a trial, but we leverage features from Melodyne for functions like tempo extraction which will work, even with the demo version.

None of the add-on installers in the menu that pops up when clicking "install" for Cakewalk have anything to do with social media. You've got installers for the Studio Instruments VSTs (this installer also includes demo projects), the Drum Replacer plugin, a demo of Melodyne, and the Theme Editor if you want to customize Cakewalk's appearance. None of those are required to install/run Cakewalk, but they're all just additional free tools.

Please try the 2020.08 update which has a number of optimizations for zooming. It is available now to update through BandLab Assistant.

No, 2020.08 is now available for all:

This will get fixed for the final release of what's now the 2020.08 CbB update, so you don't have to do anything. It's simply a minor clip drawing issue that's now been addressed.

Hi Kevin, Looks like this is an issue with there being a "Jump" (the dotted line rather than solid) between the node you drew and the one where the envelope resumes. I went ahead and logged that to fix when we get a chance, but if you right-click the dotted part and switch it to "linear" or any other shape, it should draw correctly. Thanks!

In the Tempo View, the first entry cannot be deleted, however all other ones can be deleted, so if you had inserted a change at measure 1 that you wanted to remove, you need to change the tempo at measure 1, then remove any subsequent unwanted changes.

No, we don't require Melodyne updates. Earlier versions of Melodyne 4 were subject to stability issues, so we strongly recommend making sure you're on the latest version available to you.

What version of Melodyne 4 are you using? Valid licenses of Melodyne 4 should have gotten a free upgrade to v5 I believe, check with Celemony for that. Early versions of 4 had some stability issues that were subsequently addressed.

What's the audio device and the driver that you're currently using?