![]() ![]() Thread 0:: Dispatch queue: -threadĠ libsystem_kernel.dylib 0x00007fff67e5bdfa mach_msg_trap + 10ġ libsystem_kernel.dylib 0x00007fff67e5c170 mach_msg + 60Ģ 0x00007fff2debabf7 _CFRunLoopServiceMachPort + 247ģ com.apple. Termination Reason: Namespace SIGNAL, Code 0xb I’m a professional music producer and I use Cubase 11.0.20 literally everyday through different session of recording, composing or mixing. I’m dealing with serious issues for month with Cubase on my MacBook pro 16 (Catalina, i9 2,4 Ghz, 64 Go Ram, 4to ssd). Termination Signal: Segmentation fault: 11 Hi, First of all, I apologize for my english, I may do some writing mistakes. It’s not simply a corrupted project because it does it on more than one, unless the template I wrote months ago is the issue.Ĭrashed Thread: 605 at.co. Don’t ask why I was thinking that, it’s just about the only other common factor I can think of. I wondered if it might be connected to Quicktime - and if I could run a different video player / engine instead. I also re-installed VEPro7 latest version and for good measure all my NI stuff (which really just amounted to Kontakt 5 latest update. Thanks in advance Floris ps: could not add the full report, i added al link where you can. ![]() Can someone help me out and check out the crash report Thread 64 seams to cause the issue but im not sure what that means or even if that causes the problem. unfortunately Cubase 10.5 is crashing on startup all the time (9.5 starts ok). _No issues this time with VSTs having been through them all the other day. Hi guys, Just installed a fresh version of Catalina 10.15.16. I have today erased my entire Cubase 10.5.12 including all the prefs - then re-installed 10.5 again (without the update) The probable crucial part of the VEPro crash log is copied below… If I’m supposed to be able to find the crash logs in Console, then they’re not there. Mostly things go OK - but frequently when I stop the transport (just using the space bar) everything crashes - meaning Cubase instantly evaporates - and so does VEPro 7.Ĭubase does not give me a crash log (at least not that I can find) but VEPro does. I could only find the 0.5 and 0.6, but I’d like to try with 10.0.3 and 10.0.4 too, on win10.Īlso, if anyone has any other suggestions to solve this problem, I’d be very grateful.This is pretty infuriating. I’ve been using the 10.0.06 since it was available, and I think the situation has been worsening since then, I didn’t notice it immediately, it seems to have been gradual, but I’m not sure… Anyone knows where on the Steinberg site I can download these previous versions?. I wanted to roll back to 10.0.03 on win10, but I can’t find that update installer anymore. I’m not sure if it was the last Microsoft updates or if the difference is due to something on the 10.0.06 cubase update (or both!). I booted to win7 and loaded the same song in Cubase 10.0.03 that I still had there and the difference was abismal! Everything played smoothly as it should and without any CPU spikes and with the average CPU consumption about 1/4 of the one showed in the 10.0.06 cubase at Windows 10 !. Everything went well until lately I began to notice a gradually worsening performance, CPU spikes, high CPU consumption, even when Cubase was not playing at all and even with very few (3 or 4) and light VSTis. ![]() All the later cubase10 updates (from 10.0.04 to 10.0.06) were only installed on win10. At a certain point, after comparing Cubase 10.0.03 on win7 with the same 10.0.03 version in win10 I came to the conclusion that the performance was identical and stopped using cubase on win7 (but kept it there). Hi, I was thinking of starting a new thread about a related issue, but then I found this thread, sorry for “ressurrecting” it as it is now 3 months old… Anyway, I have Cubase Artist 10 installed both in Windows 10 and Windows7 (dual boot PC). Since Steinberg do not plan any more updates for 10.0 I am stopping the updating there. Every update after that seem to have caused unusually many serious bug reports on serious issues such as CPU and GPU performance. Glitchy graphics on my second monitor as if my GFX Card isn’t being used which may well be related to the issue i posted earlier today below My keyboard and Panorama P1 are suddenly not being recognised randomly when i launch a project. I have to End process Tree for each one and they are stacking maybe 4/5 times)Ĭubase crashes almost everytime i shutdown Cubase (which happened before but much less frequently) Ram is stacking (instances of Cubase aren’t terminating according to Task Manager and Ram isn’t being released. I think i may have missed an update so think i was using 0.40 previously, possibly 0.50 (Whichever it was was running perfectly).įirstly the update installer that i downloaded from the Steinberg Assistant brought up an error, but it has done that before so i chose to ignore the error and let it continue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |