I was using presonus studiolive 16 4 2 ai desk firewire but no support anymore foe firewire , but swapped it to quantum 2626thunderbolt 3, but I’m getting a lot of audio interference in the computer so I’ve gone back to the audiobox 2 in 2 out.
None have given me any problems, but the jury is out on that one.
The audiobox has been the one that’s given no trouble ? on that (the desk was 100% fantastic but no more support)
These problems have only just (mass) showing with C13 getting worse with each version and update.
C11 was ok, very few problems until it’s final update. C13 started off really good but with more and more continuous use C13 been shutting down now 99 times out of 100.
I’ve run, today, an old project, with one vst2 plug in, C13 shut down 4 times, all at different places. It’s just run now for 3 run throughs absolutely perfect, now just shut down again three times.
I’m tempted to get another interface, but the outlay is too much at present, considering I’ve got the quantum 2626 (when it’s audio interference problem is sorted).
All of my other DAWs work fine (Ableton and Reason) but my projects have been built in Cubase for many years. And obviously won’t open in the other DAWs.
Just hope my problems sort themselves out very soon. At least then any info can be passed on to others - who I know are having similar problems.
But besides the “interference in the computer” issue, which kinda sounds weird to me (how does that show up?), Cubase still crashes with the quantum that much, or is it more stable?
My suggestion would be to get a free SSD and install fresh windows on it.
Then install Cubase, all your updated plugins and everyhting you need for your DAW work on it, boot from it and test it and see if the crashes happen again.
That way you don’t have to touch your actual system and can be sure it is not another totally unrelated issue on your system.
No the quantum never had any stability issues with C12. Not run the quantum with C13. We’ve narrowed the interference down to the thunderbolt cable. But these things are not cheap.
The audibox is fine for the time being.
The system is brand new last year (scan audio) been back in for drive replacement, everything is 100% (well 99% nothings perfect).
It’s definitely a C13 based issue. It’s just how to diagnose it.
It just feels and behaves very unstable. Don’t have this problem with any other software what so ever.
(just waiting for a noise suppressor for the quantum 2626 - should solve that issue. Still got C13 shutting down randomly using the quantum. the audio interference is between the main out of the quantum and my desk/amp input - so that’s not the issue)
That doesn’t help anyone’s feelings. This crashing is happening right when I need the software. I’ve been with Cubase since $ and the last three releases have all crashed constantly. I wish Cubase would fix itself before shoving any more releases at us. They are about to send me to Pro Tools.
I only have stock plugins/ ones that came with it, and mine is doing the same thing. Crash Crash Crash. Indecipherable dump files. Steinberg needs to fix this.
Hi somehow there’s likely memory corruption happening somewhere. We think this might have to do with 3rd-party plugins. In order to move further with your crash we need a deterministic way of reproducing the crash. Is there anything that comes up to your mind that you might be doing and that leads to this crash? Or is there a project where this happens rather often right now, and if yes in which context (playbacking, MIDI editing, etc.?) then you could send us the project to us and we could try to reproduce the crash.
hi,
I tried it with only Kontakt 7 loaded and it was still doing it, i also tried with Kontakt 6, and same issue I was using a NI guitar library , but i tried a different library (NI one) and it did the same. I also was able to make it crash by trying to use Melodyne as an extension, so I don’t think it’s only a NI problem
I thpought about going reverting to Cubase 12, but it does not appear to support Sonoma so i didn’t want to make it worse
Lucky you get ARA extensions to show up. The dev team thought it would be a lovely idea to just code Autotune pro out of ARA integration in 13.0.20. Truly the kings of breaking things lol. oh and the fix is due…first quarter. So they say…
It would be good to try to see if you can make it crash within a project not relying on any 3rd party plugin but I understand this is an overhead. Unfortunately we cannot make much sense of the crashlogs you have given to us, there is memory corruption happening somewhere at some point. Our advise would be to identify a very deterministic way of reproducing, or not reproducing it. If it randomly crashes only in projects relying on NI plug-ins that there might have to do with NI, at least we would like to know how we can reproduce it quickly here to rule out the real root cause, that it’s due to us or NI.
That could also be due to a totally different root cause. Was this crash also part of the ones you gave us?
hi, sorry missed your reply somehow. No i don’t think that one was part of it. Is there any update? I don’t use melodyne much, but not being able to use Kontakt is a real issue. Have been back on Logic for the last couple weeks. I can’t be the only one having this issue. Unfortunately to really fully test in the way you suggest I would have to have a second system where I only instal cubase and Kontakt, but I don’t have a duplicate system (my other machines are all Intel and don’t run Cubase on them), and don’t really have the time to do such extensive testing unfortunately
I noticed also, the bigger the project file gets, the logarithmically slower it responds to edits, scrolling around, etc.
Already a project file of about 500mb lags heavily, so that saving and editing takes seconds.