Annoying 'Analyzing audio...' message

I understand that the message probably pops up because I may have performed many actions in the offline Windows processor (I applied normalization to all vocal tracks). Or maybe due to too much automation or something else. But it’s very frustrating, especially when it takes a couple of minutes to process. I suspect it’s checking the entire track (even though I’ve split it into different events). It probably needs to be bounced, but sometimes I can’t do that because I need my configured VariAudio, which reprocesses after bouncing the track.

Recently, I had to wait about 15 minutes for it to finish analyzing the audio, and that happened because I somehow deleted all the hitpoints of the time warp (maybe accidentally with a key combination or a key command).
So the question is how to disable it? Should i bounce everything or should i do render in place or similar action to stop this message bothering me?

I have only seen the analysis message when I use VariAudio. I am not sure whether there is any other functionality in Cubase that can cause this window to appear.

The analysis always happens to the entire clip, so the event length does not matter.
(In case the relationship between event, clip, and file is not clear, please follow this link:)

It’s unclear how to make Cubase stop analyzing audio.

зображення

It’s just super annoying, after every couple of actions, it analyzes the audio for 15-20 seconds (in the best case).

It’s like Pringles. Once you plop you can’t stop. Sorry. Only bouncing/rendering the events to new files will shorten the required time.

Furthermore, when you do perform VariAudio on an event, Cubase by default asks you whether it should create a new version. The only reason not to chose “New Version” is if you use the event elsewhere and want the same changes to be applied everywhere in the project.
If you chose New Version that will create a new, small file just for that particular event.

I don’t need to stop it but i need to prevent it.

Only bouncing/rendering the events to new files will shorten the required time.

Okay, that makes sense