Noel Borthwick

Right, if the plug-in is bypassed, the pdc is eliminated once you restart playback.

If you have poor internet and are unable to sign on as a result of that use offline activation to sign in by creating the activation response from a different computer that has a good internet connection.

Is this project specific? Not seeing anything abnormal here. Post a link to the specific project file since that's the only way to check it. Also try this on other project files and also try David Baay's suggestion of pre-creating the target track and check if that resolves it.

Then you need to attach or send the specific project that has the issue. Otherwise there is no way to diagnose further.

Not seeing any of these symptoms here. Are you running the latest build 36?

@Adam A test build was sent to you via PM yesterday that should resolve a potential crash. Please test it ASAP and report back. Regarding lag we're not sure why you are seeing that since there have been no changes in MIDI groove clip rendering itself. However, the crash scenario could have exposed some side effects so please report back if it's working correctly with the build. Otherwise send a simple representative test project that exhibits the lag.

Its a known issue that BReverb has problems rendering some automation with fast bounce. You could possibly get around it by doing a realtime bounce or by using an Aux track to record the rendered output.

Bounce to track is working as expected here with virtual instruments in build 36. Without more specifics its hard to follow what you are attempting to do. What is "drum machine"? There are no changes to bounce as such in this release.

This sound like a bug in BReverb rather than a Sonar issue. Try a different reverb.

Note that while saving from a crash dialog generally works, it's not guaranteed, since if the app state is already compromised, it may crash while saving itself.

Spacial panner or the old (badly named) sonitus surround are unrelated to surround sound. You can use either on a surround bus if you so choose using surround bridge.

Please read "Why do I sometimes get an Application Expired message?" in this FAQ.

The message is telling you that the current build you are running has been superseded by another build that has important fixes. As Jon mentioned, we updated the build on Friday due to a new version, due to a problem that could potentially cause data loss. Updating to build 36 should work fine. Please check your internet connection/reboot PC etc. It's probably a temporary internet issue that's preventing you from reaching the download server. Also go to help | check for updates to retry the check.

You can reinstall a prior downloaded installer if you haven't deleted it (assuming that that version hasn't expired). It takes infrastructure to provide rollback. We may provide rollback to the last supported version for paid members in the future.

There should be a notification prior to the expiration of the lease. However if Sonar is infrequently used you may not have seen the notification. Note that it will never go inactive mid session so you can't lose edits that way. Also expired builds are a different thing from the normal activation lease. We expire builds that are very old or when there is a known problem that can cause customer data loss for example. I'll look into the UI sluggishness when it's offline. That shouldn't be happening. Possibly what's happening is that it's trying to do an internet check and that's timing out and blocking the UI.

This is fixed in the update related today.

Yes this wasn't intentional. We'll investigate and fix it soon.

We're going to make the core plugins available to demo soon. Note that if you turn off migration it won't replace the older plugins on your project. It also warns you when it replaced the plugins. In the next release we're also migrating any old plug-in presets you may have saved to make the process painless. But it's fairly easy to save a copy of your project with the new plugins.

See my post above for a resolution until the next update is released.

Interesting. Sonars optimizations that allow better low latency performance also implicitly means its using your CPU more efficiently, by keeping it busy. So its not impossible that it creates more heat on a loaded project.

Have you looked into background processes? Your symptoms sound like some background progress either consuming excess CPU or interfering with your audio driver. If it's only in this project it could also be a plug-in. Sonar cannot excess cpu when it's not playing.

This is most likely related to this issue which has been fixed for the next release. BTW the number keys change screensets, which are a different thing from workspaces.

@Jim Stamper this has been addressed for the next release.

@Max Arwood this was indeed a regression and it's been fixed for the next update.

I'll look when I get time but AFIK those names are not being explicitly managed by us but some middleware.