Between every release cycle software gets new features and (yes, even that) bug fixes. There is always a chance of introducing new problems with extending software.
Reaper or Studio one is not Cubase. They all have different codebases.
I don’t have access to the sourcecode so I can’t says for sure what the reason is. It is just a guess based on the identical effect with different Interfaces.
I would do another test with a different Windows machine, if that shows the identical crashes you have a real case.
I’d say where we’re at now definitely yes. As I said i used Reaper for 18 months without a single crash , the forum is very active there and updates are regular and TBH I can’t remember when an update actually broke things . There are lots of niggles, the odd bug but nothing like I’ve seen here where between updates major things like the mix console meter bridge suddenly starts hard crashing Cubase or the AXR extensions now crashing cubase .
I can work around niggles and things that perhaps don’t work as planned but not crashing . Stability is really important if you have clients with you when you work, it makes YOU look bad if sessions have to keep being stopped etc. I had the head of Warners sat next to me a few years ago when we were recording an album that ended up at number 1 for a week over christmas , that’s pressure. I need my DAW to not let me down in those conditions.
Thank you for that @Norbury_Brook (and for the help you’ve given over the years ).
Anyone with experience on other large sequencers besides Reaper (e.g., Pro Tools, Studio One, etc.) … is it clearly more stable without new “bugs” being reported etc. than Cubase is in your experience?
@Martin.Jirsak@Chriss
Ok so updated and have continued constant freezes…latest one attached here Crash24thJuly2024.zip (858.2 KB)
I’m suspecting it’s related with the realtime engine / possibly VEP plugin…as often when I come back and everything has frozen the audio performance is blank but there is a red overloaded indicated on…sometimes also I’m getting total audio dropout from the return inputs from VEP even though the midi is triggering it fine / instruments playing in the server/instance and also the internal cubase instruments/audio still play
OK so it’s been over 2 months since I started this thread and still no response or even a suggestion as to what could be causing it…The mystery remains
@Martin.Jirsak@Chriss
Ok so another one to report Crash3rd August2024.zip (1.3 MB)
This was a session with only a handful (6 odd) of audio tracks and 4x instrument tracks with Kontakt7 each hosting a single Heavyocity instrument with only 80mB…and the realtime engine was still being pushed/struggling into the red…12/24 core, 128GB RAM… what a joke!..there’s a big problem, and it’s def not my hardware or config…just sayin
I’ve just upgraded to Cubase Pro 13 From 8 Artiste. My 13 is freezing on play back of drum tracks. I have to reboot and then get a repeat performance. The old 8 is working well.
Hi. Just had a look at the system requirements and it seems I’m a bit behind. It’s a PC with Windows 10 Pro. Intel CPU G6400 @4.0 Ghz, 2 core. 16 GB ram. The harddrive has suddenly become quite full, so I need to do something there. The Cubase 13 Pro 41 version is the latest I think, built in June 2024.
).