Jonathan Sasor

Yeah, I mean, simply recording multitrack audio is pretty easy on systems these days. The processing becomes more of an issue when you start loading down plugins, but that's also very dependent on what plugins and how many you're using. You could certainly accomplish a lot with the stock plugins included with Cakewalk, which are not super CPU intensive.

The gain knob on the track strip is for the playback gain in Cakewalk. For instance if you recorded something with a low signal from your interface and then want to change how hot that signal goes into your plugins in the rack, the gain knob is before the FX bin in the signal flow. As mentioned, this is distinct from the record level though. Cakewalk (or any host) receives a signal from the selected audio input driver. That level is then set from the hardware device, be it from a software mixer panel or a physical knob on the device.

Essentially this boils down to what you have set for your inputs and where your signal flow is going. Look at what you have for your inputs and how that's receiving signal. if you're using a Steinberg interface, make sure you have Cakewalk set to use the proper ASIO driver for it in the Preferences.

the percentages are based on the clip length. Make the 2 clips identical in length and they should compress size (speed up) at the same rate.

About a year ago we actually did a couple tweaks for loading older .wrk files in CbB, so that should all work just fine on a Win 10 system in x64. So either opening directly, or Mark's way to grab in newer features from the go are valid options.

Also a valid point. I can't reproduce a crash on my end, but based on how Aux tracks are designed, trying to freeze them is a somewhat odd workflow. The whole point of an aux track is to have a live input like a bus, but in the track pane. This allows recording, or you could also do a Bounce to Tracks to get a similar effect. If your CPU is starting to get eaten up, you could put TH3 on the individual tracks then freeze those separately, or you could record the aux track, then disable the input and the FX on it. You'll need to consider how the signal flow is to ultimately get what you need. The app shouldn't crash in any case, so if there's any kind of dump or reproducible scenario that we can look into, we're definitely interested in looking into that. It might be useful if you uploaded a copy of the project to that end if you can't get a dump file.

Is the .exe still visible in Task Manager when it crashes? You can generate a dump file from there if so.

I've done a bunch of testing with Spitfire's BBC Symphony Orchestra without issue, so there shouldn't be any major issues with the plug. If you're seeing a crash, please send us a dump file, and we'll take a look. Do bear in mind it is rather resource intensive plugin since it's loading a rather large library, but it works normally on my end.

We're not hiding anything. BandLab acquired the intellectual rights for Cakewalk properties, and chooses to provide it free to users. It's the same core application that was being sold as SONAR Platinum previously, no nefarious changes, just continued active development. Just because an application is free does not mean it has to be open source. We put a lot of blood, sweat, and tears into the application, and that has value, whether the app is being sold or not.

If you're crashing, please send us a dump file and we can investigate:

@Ian Miller If it's the app (as opposed to the whole PC) crashing, send us a dump file. Details here:

Showing an envelope on the track itself or in lanes has the same identical function behind the scenes. It's just a different way to display them. Having lanes makes it easier to work with multiple envelopes, but it's not required.

If you have any issues with auth after going through the link scook sent, PM me and we'll take care of it.

No worries, not everybody spends all day in front of their DAW. Just make sure you only have valid paths for your VST Scan Folders. The defaults are C:\program files\common files\vst3, and C:\program files\cakewalk\vstplugins. You can add other ones, so long as they're specifically locations for plugins. Don't have anything like just root C:\ or C:\Program Files as other .dll files will interfere with the scan.

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.

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.