Noel Borthwick

The question is whether the same issue is present in the prior shipping release 2025.11 not whether it's reproducible in the EA

Is this issue specific to this early access release or are you reporting an issue that you see in prior releases? This thread is to discuss issues that are specific to this release alone.

Clipped meters like that is a symptom of a plugin internally "crashed" in its DSP. Its most likely generating bad floating point data. This isn't originating from Sonar and has nothing to do with large projects. You can troubleshoot further by bypassing the plugins till you find which one is generating the noise.

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?