Noel Borthwick

Its a percentage of the total audio processing load of 100%. The core is irrelevant because processing is never on a single core. It flips between buffer to buffer to any available core.

The other most common cause is signing in with a different user ID. Ensure that you are signed in within Sonar with the same ID that you purchased your membership with.

I'm not able to reproduce this here. Attach a specific project where it happens.

We have some plans for enhancing this feature next year with smarter/deeper integration.

IF it freezes can you capture a dump file from task manager please?

Not sure what you are referring to. The title bar is highlit to show the current window. Standard windows MDI behavior. Also project windows cannot leave the application frame. Also standard behavior.

@mefodia please check if you have access to free loops when you sign in to the BandLab Studio web application. You should sign with the same user id that you are using with Sonar.

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.