Help!
I suffered a momentary Cubase crash seconds after it loaded an arrangement (which is not resource heavy), and ever since, all my external physical synths are getting triggered about 1/32 early.
Cubase 10 Pro
Windows 10 Pro.
Focusrite Scarlett 18i20 interface with Midi
DeepMind6 synth
Korg Monologue synth
Crash dump file retained.
If I examine the midi note events, they are all bang on the line in the grid. They match other audio events exactly, so this issue is not about where the note events are in the grid. They are snapped correctly. But any synth on a midi-out gets its note events early and so it triggers early. As a test, I removed snap and offset note events by about 1/32 forward from their correct placings in the grid. Then they sounded in time.
So I have established that the events are correctly placed and I have checked that audio wavs and soft synths are triggering correctly. The only issue is the early midi-out signal from Cubase to external synths.
I would be very grateful for any help with this, I can’t be without my externals!
Thanks for reading.
Ziaone
Try to activate the constrain latency delay compensation…just in case it’s a dodgy plug misreporting latency after the crash that’s causing all audio to be late rather than the midi being early.
Can you upload the crash dump or did you analyse it already and what did it tell you??
And to be sure…you did reboot your computer since it crashed??
Hey Grim , thanks for replying.
Many restarts of all devices so we can rule that out.
I have no idea how to analyse a crash dump file so I’ve attached it to this reply.
Thanks for the tip about “constrain latency delay compensation”. I need to delve to find that in the menus next, any pointers gratefully received. Never had a serious problem with C10 before. Cubase 10.0.60.396 64bit 2025.5.7 21.28.29.713.dmp (489.2 KB)
So I activated constrain latency delay compensation but no change I’m afraid, activated or unactivated.
Just looked up baios.dll, “for finding and loading various audio devices, and configuring their inputs/outputs.” Also found a site that purports to give downloads of it (called DLLme). I don’t want to make things worse with a 3rd party unless its a trusted source for users, of course.
Hey Grim, it suddenly started working for a short while with latency delay compensation activated. I did nothing at all, stuck a spud in the oven and came back and the external synths were in time again.
For a few replays of the tune with click going it was sounding in and then it reverted. Unstable. I guess I’m still looking for a solution because baking spuds to get through the album is not ideal.
Yeah…so it does suggest that the audio latency or pdc specifically is perhaps where you need to look rather than anything with midi.
Maybe start a new project, use import tracks from project and do a few at a time and keep testing till it breaks??
Thanks a lot for your guidance. I will need some time to do that and it might not be tonight.
I’ll be keeping an eye on this thread and will post any development. Cheers Grim
Hi Grim, I seem to have sorted it!
So, as a test, I removed my focusrite from the chain and replaced it with a little focusrite 4i4. I ran it through a test arrangement first and then the track I’m working on. Everything was in time. So evidence points to my original interface having the seizure, not Cubase.
However, when I put the original interface back in the chain is was reliably playing everything in time again. I shut everything down and restarted, and it still kept time.
My hunch is that when the 4i4 was introduced to my PC (same family) it loaded drivers and whatnot fresh and that reset the status for the other interface to work off again.
It cleaned the issue. It’s consistent with the crash dump info, but baios.dll crashed because of the interface crashing, not Cubase.
Thanks again as your info helped narrow down my investigation, saving weeks of tearing hair.