I hadn’t been encountering this for a little while, as I was avoiding use of local instances of VEPro and only using the satellite computer for that - I was guessing that somehow it was local instances causing it; but I was wrong. Evaluating Synchron Strings on my remote mac, and the same issue appears. The noise burst happened this time on an effects return - for QL Spaces - and didn’t go away until I disconnected and reconnected the IO hardware in System Setup. Since I have been cowed into working at low volume in Cubase now, it didn’t wreck my nervous system.
BUT: What I was able to verify this time was that its onset is signaled by a dropout when selecting something like record enable of a track - not audio tracks, just VI’s - or showing the channel window of VEPro, or muting/soloing a midi rack that was pointed at VEPro. So when that muting behavior occurs, the burst is soon to follow. I’ll be starting that support ticket now.
And to be more specific: it wasn’t happening when I selected or record-enabled another VI that was not VEPro - I could be in play and enable/disable ANA2, say, with zero problem. It’s only VEPro - as if the way it buffers means that any query to the plugin at all requires a refresh of the buffer, and most often that will result in full-scale noise. So I’ll be asking about this over at VSL too. But the reason I feel that it’s related to Cubase in particular is that often it’s not the VEPro channel that redlines - it’s an effects return and the stereo master buss. Sometimes it’s also the VEPro channel. And sometimes the VEPro channel then stops playing out of the right side. It’s just weird. And also makes the Cubase experience a lot less appealing.
Solution - never change anything in play. Yeah, no. It’s 2021.
UPDATED: When I turn off AsioGuard for VEPro the problem goes away. So it has to do with switching between the different buffers when Cubase is in play - it causes a little meltdown.