Jonathan Sasor

If you run the 2020.05 rollback installer do you still see the freezes?

Mix Recall is also your friend. ?

Just to reiterate the points made already, you typically would not record the output of a plugin within the DAW like that. You can in Cakewalk if you have the output from a different track routed to an aux track as scook mentioned, but generally this is just creating additional work for yourself. The standard workflow would be to record with Bias (or any other amp sim/plugin) running on the track that you're recording to, with the audio being processed by the plugin in real time. To listen to the audio being recorded in SONAR/Cakewalk, you enable the Input Echo button on the track. This then means you're recording the dry signal, but hearing the processed one, which means you could always change the sound in the plugin if you need to too. Just watch out if you have monitoring enabled on your interface as well, otherwise you'll hear both the effected sound being routed through your track, and the dry "direct monitoring" coming through the interface.

If you go to create a new project folder, it'll use new paths. So for instance, if you did save as, then pointed the whole project directory to go to a new folder on your desktop, it'll move everything accordingly there. The issue is just related to manually editing the audio path names separately within the Save As dialog.

We generally will do localization a few times a year rather than per update. This will ultimately get translated in the next round.

As Kevin mentioned, this issue has been previously reported and is in our queue to fix as resources allow.

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.

There appears to be an intermittent issue with BandLab Assistant where it fails to actually launch the installer after download. You can either exit out of BA, and try the install again, or you can go to the downloads folder (%appdata%\bandlab-assistant\Downloads) and manually launch the Cakewalk installer.

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.

The issue with the install is related to BandLab Assistant, and is new. We're currently investigating why its failing to launch the actual Cakewalk installer, however as mentioned, launching the installer manually from the download folder will work successfully.

The thing with stretching is that it's very material dependent, so it can vary from clip to clip. Please do send us an example next time you notice something as concrete examples are the best way for us to troubleshoot issues.

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

What stretching algorithms are you using for the bounce? We added the Elastique options for CbB a couple years ago now, and actively maintain that. If your project can reliably reproduce issues with offline rendering, you can send that to us for analysis.

It would appear something is intermittently getting hung up with BandLab Assistant between downloading and actually launching the installer. As you saw, it downloads successfully, which means you can manually run the installer fine. This shouldn't have anything to do with admin privileges or not. If you don't want to manually launch the installer, generally if you quit BA and try it again a couple times, it should ultimately go through, but manually launching the installer file would be the workaround.

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