I don´t think that an I9 or in my case a Ryzen 7 can be considered old CPU to have such low performance…
Not quite sure how to do that. When I try to upload the report it says file not supported. Maybe I’m not sure how to PM
Hi @plcpaul1 ,
the remote settings losing the assignement has an easy explanation: when Cubase 12 is crashing each time you close it, the preferences (assignments among them) are not being written to their destination files. So the remote issue should be gone when we fix the crashes.
Could you please send me as PM:
- your plugin report (see Matthias’ post for how to retrieve it)
- your crash dumps (Win: Documents → Steinberg → CrashDumps)
Are you on Windows? And are you running on an administrator account? Just an idea: could you try to run Cubase as administrator?
Thanks for your support!
Chriss
Hi @Scrummy ,
you’ll have to zip the file, unless will not be attached here.
Cheers
Chriss
Most of my projects (created in Cubase 11) hit 100% on the CPU meter every time I press play, which means the red light is constantly illuminated. I can reset this, but once I press play again we’re back to 100% and more red light clicking. M1 MacBook Pro running under Rosetta.
Hi @G-row12 ,
there’s an issue reported for the 175% scaling setting (Windows Display settings). Could this be the case on your system? We are working on a fix and hope to include it in the upcoming update.
Cheers
Chriss
Hey Chriss,
I sent it to Matthias, but I thought I would send it to you as well. Thanks.
Blessings,
Steve Cummings
Plug-in report.zip (10.3 KB)
Hi @J_Shizzle ,
happy to hear you mostly enjoy Cubase 12.
Regarding Halion Sonic SE: does the same synth also smash your CPU, when running in Cubase 11 (in case you are on a M1: please enable Rosetta mode for both, to be able to compare C11 and C12)?
Thanks for letting me know.
Chriss
Hey there,
I don’t own cubase 11. But the same Projekt with the same synths in cubase 10 is totally fine
Hi Chriss. Thank you for replying. I’m using 100% scaling in my display settings. I hope good news in the next fix. Thanks Chriss.
1 Like
Personally, I think it’s a really good idea… I think a lot of people would buy this equipment and at the same time many of the problems raised on this forum would disappear… In fact there would have to be strict guidelines for the hardware itself and all software settings i.e. drivers, BIOS, Cubase but I think this is not a problem for Steinberg… Maybe we will see such a solution in the near future…
Could you please sent me your plug-in report from the project you are mentioning?
Hi @Tony_ST ,
you described an issue where you experience a short pause on an added Midi track. It is probably a known issue, where disableing Monitoring/ Rec-Arm on VSTi + Midi tracks leads to a short interruption, if your buffer size is the same as the Asio guard latency.
A fix is scheduled for one of the next updates. As workaround, you can make sure to keep your audio buffers like this (for 44 & 48 k, if you are on 96k, just double):
Asio Guard Low: buffer size < 256
Asio Guard Normal: buffer size < 512
Asio Guard High: buffer size < 1024
I hope this helps for the moment.
Cheers
Chriss
1 Like
Thank you very much Chriss.
Same for me! C12 performs bad and strange, C11 works fine.
2 Likes
Some re-sizable VST3 plugins still produce some internal errors and can even show error messages within Cubase when we resize them.
It does that mainly on plugins that can be resized by a factor scale from within the plugin itself, for example a slider or anything that you can scroll with the mouse.
I really believe that the VST3 resize handling/communication between the plugins and Cubase has been broken with the C12 release.
Here’s the Crash Dump I just got :
Cubase 12.0.20.263 64bit 2022.5.7 19.38.31.791.dmp (888.9 KB)
Also here are two other Crash Dumps which I didn’t remember what I’ve done to get them :
Edit : These are from an Audio Alignment bug, and this has already been reported to Steinberg.
Cubase 12.0.20.263 64bit 2022.5.1 20.23.30.670.dmp (769.7 KB)
Cubase 12.0.20.263 64bit 2022.5.2 12.34.01.691.dmp (681.3 KB)
Hi. I got here by googling ‘cubase 12 dropouts’ which I’m experiencing, which lead me to the thread for v12.0.10 which I read in its entirety. I realized I was using 12.0.20 so I’ve read this. I’m still experiencing significant dropouts in a simple project with a single track using Halion acoustic piano bright. The dropouts make it unusable. I’ve run 11 on this same setup with no issues. I’ve tried to make the adjustments I’ve read about and nothing helps.
What’s particularly interesting to me is that the issue is definitely cumulative. I play, it sounds great, after a few bars it starts to clip. I sit down and read the forum, make an adjustment, it gets better I think ‘great I solved it’ - and it comes back. I finally realized that if I just let it sit for 30 seconds, it’s gets better, for about 30 seconds.
I’m running 12.0.20, I’ve got an R16 interface, the computer has in i7 @3.6 gig with 4 physical (8 virtual) processors. 32 gig of memory and only SSD. I have this issue with two different MIDI - USB interfaces.
Way back when I first got into this, I remember resolving by getting a better midi-usb interface from Yamaha, but I don’t remember the cumulative effect. Let me know what I’m missing here, thanks,
Gian
Would be interested to know if it’s just me, or has anyone else observed this?:
Once glitching kicks in, CLOSE Cubase (12) and switch to any YouTube video (already opened but not playing) which has background music in the video (I use a FireFox browser), Even though C12 is closed, YouTube audio glitches in exactly the same way as it did previously in, the now closed, C12.
Context: I have only one audio interface running on the Laptop (ThinkPad through a Yamaha THR30), all other audio interfaces (inputs and outputs) are disabled within WIN 10 settings, including the built-in laptop audio.
Reboot WIN 10 and audio is glitch-free again within YouTube and C12 playing the same project.
So is this a single, initialising, unrecoverable, (unknown) event within C12 LATCHING the (Yamaha THR ASIO) audio into a semi-permanent glitched state, that only a reboot of (up-to-date) WIN10 can resolve?
Anyone else observed this? Or is this to be expected, and I’m reading too much into this?
Please add some more details to your reports. Unfortunately „bad and strange“ isn’t helpful. Please describe how the performance has changed and add a plug-in report to let us know about the specs of your system. It‘s not a general issue. Cubase 12 is performing very well on the majority of systems. That’s is why it is so important to understand the context on which system the issues occur. Thank you!
Could you please sent me your plug-in report? We would like to know the exact specifications of your CPU and that’s in the report.