TBH I’m not sure either but as I said I’ve seen this in the past so thought it worth mentioning to the OP.
I’ve not had issues with opening old projects ever… appart from mising plugins……and I’m not a big user of templates so haven;t had issues on that front either.
The slow export problem was introduced when Cubase added Apple Silicon support. I did a few experiments that showed the same project exported much faster on an Intel Mac than an Apple Silicon Mac. There were many reports of the problem at the time, but AFAIK, there has never been any progress on this.
As for the buffer size, asio-guard is irrelevant for the buffer size during export. You can have asio-guard on or off and that will make no difference to the processing buffer size during export.
Sorry, I haven’t seen the crash you’ve reported (I’m using a M4 Pro Mac Studio), so I can’t confirm that problem.
TECHNICAL STATUS: Native Instruments & Kontakt 8 (via Plug-in Report)
1. Architecture & Compatibility:
Format: All NI plugins, including Kontakt 8, are running as VST 3.7.x (Native ARM-64).
Vst2 usage: There are zero (0) VST2 instances or paths active, ensuring a clean Silicon-native environment without Rosetta bridging.
2. ASIO-Guard & Performance:
Status: ASIO-Guard is Enabled for all NI instances.
Potential Conflict: Despite being native, the project exhibits a “Real-Time Lock” (1:1 export speed). This suggests a potential priority conflict between Cubase 15’s BAIOS thread and Kontakt 8’s internal engine during offline rendering transitions.
3. Observed Anomalies:
Instance Count: Even with minimal active instances, the ASIO-Guard Prefetch remains locked to the hardware buffer size (1024 samples). This indicates that Kontakt 8 might be triggering a “safety sync” mode within Cubase’s scheduler, preventing high-speed offline export.
Crash Context: The previously reported SIGSEGV 0x8 crash in the BAIOS thread occurred while processing Kontakt-heavy tracks (Studio Drummer), pointing towards a memory pointer error during the buffer handoff between the VST3 host and the NI engine.
Summary for Developers:
The NI environment is technically up-to-date and correctly installed. The failure to achieve offline export speeds on an M2 Max suggests a deep-level communication issue between the Cubase 15.0.6 audio engine and NI’s VST3 SDK implementation, specifically regarding thread synchronization.
I’ve seen some exports with AS that are very close to real time.
The obvious question if he suspects Kontakt is the problem is: does this happen in projects without Kontakt? Exports with Kontakt work fine for me, albeit slower than on an Intel Mac.