I have been religiously pressing the button to send the dump files to Steinberg on startups in hopes that this might provide some clues. Other virtual instruments that are on tracks include one additional instance of Kontakt 6 (on a frozen instrument track and 4 instances of UJAM VG-AMBER (on tracks that were disabled after rendering to audio. Virtual instruments active on the project at present include 2 instances of Toontrack Superior Drummer 3, IK MODO Bass, NI Kontakt 6, MusicLab RealStrat 5, and UVI Workstation.
#CUBASE 10 PRO FREEZES THEN PRODUCES A HIGH PITCH NOISE UPDATE#
To try to whittle things down a little further, in the event this still relates to plugins at all (which I’m now wondering if is even the case), I even removed iZotope Tonal Balance 2 from my Control Room (I always keep it disabled when not actually using it anyway), and the only insert plugins I have at this point are NI Guitar Rig 6 (fully up-to-date) and Overloud TH3 (I think also up to date, but this is an older plugin, and I don’t recall when the last update was). In particular, I’d removed any Waves plugins from my current project (easy enough to do since I’m still in the tracking/editing phase, not mixing), including not having the any Nx plugins in Control Room, and I’ve still been getting those startup messages (referencing Freeze) every time I start Cubase Pro 12. if it at least has to register WaveShell and what plugins that makes available, even when there have been no Waves plugin updates). So, one more update on my situation with this freeze report on startup: It is now looking like it may not have anything to do with Waves plugins at all, unless perhaps Cubase 12’s simply scanning plugins when it starts (and having Waves plugins installed) creates some such dependency – e.g. But that is pure speculation, not something based on knowing what Cubase actually does when shutting down. Cubase not waiting long enough for a sub-process to shut down), perhaps that might make sense as my system is not exactly state-of-the art at this point, and I also have loads of plugins, and maybe some (like the Waves Nx stuff) take longer to close down than others. If this wild speculation were actually what is going on (i.e. I know that I’ve also seen one or more other processes showing up, both in the past and at least once with C12, but I don’t recall now what that was. Two are named Cubase, one of which says “not responding” in Task Manager, and another is some sort of licensing process (I don’t recall the name off the top of my head). where it is still there and not responsive) is that there are multiple Cubase when you expand the Cubase entry in Task Manager. The one thing I have noticed when Cubase has actually hung (i.e. But most of the Cubase warnings on startup that occur mention “Freeze”, which may mean something hung, rather than crashing, though there has been no visible hang in most cases.Ĭould this perhaps mean Cubase has some process somewhere that is monitoring the time taken to close itself down then kill another process if it’s taken too long? That seems unlikely to me, but I don’t know how things work here. In my case, most of these supposed crashes aren’t putting events in the event logs at all – last one was on March 6th – and the ones that have gotten there have not mentioned Waves, or any other plugins. My main suspicion, though, especially after seeing the different behavior in Cubase 11.0.41 and Cubase 12, is that it is a Cubase problem, perhaps relating to some bad assumption on dealing with external processes, especially on startup or shutdown. If it were actually a Waves bug, I’d think they’d have reason to want to address it since it could also affect other platforms. But it’s also been very stable for me when doing actual work in it, and I’m often in Cubase 8-12 hours a day when working on recordings.Īs for the Waves thing, assuming it actually is a Waves thing, I’d think it will depend on where the bug (or bad assumption or whatever it is lies). That said, I have only been using Cubase 12 on my own recording projects at this point (and that is true most of the time anyway), so I can tend to take more risks than many. Any crashes or hangs that existed were either totally unnoticed by me (like whatever was the case from last night) or were hangs right upon loading a project (one of the demo projects had that issue a few times) or on closing Cubase at the end of a long session (similar to what happened a fair bit in Cubase 10.5 and 11 that had made me suspect the Waves Nx plugins, especially prior to Waves V13 when the head tracking window was unavoidable). This week I’m back to tracking (virtual instruments, but I needed to use amp simulators with virtual guitars, thus trying the Waves plugins of that sort yesterday). Just to be clear, I haven’t experienced actual crashes while using Cubase Pro 12, and I spent upwards of 2 days using it on a mix late last week and weekend, including using lots of Waves plugins.
0 kommentar(er)
