@Jorge_Ruiz , I did exactly the same thing last night, and got a similar Visual C++ message when i updated Waves Central. Immediately after that i got the “very old- looking” dialog window i described a post or two above.
This is all in Cubase 11 Pro, but I believe something was changed there by Steinberg without my asking for it (my C11 Pro license description in the USB eLicenser now having new words appended to it after updating the eLicencer, something like “not upgradable”).
So i don’t know if it was a C12-driven change (i didn’t want anything to do with C12 “in my house”!), or that C++ Visual thing you mentioned.
I am trying hard to keep from moaning and whining, “Why couldn’t they just let me use my C11 Pro without introducing c12 issues??”.
In fairness those .net distribution packages are included in a lot of plugins too (in fact they are in a lot of software packages that are nothing to do with audio as well). So they could have come from ilok or waves or any number of developers. I usually do not install the .net part when I see them come up and I go and get the latest .net versions myself. Often when installing an older plugin some really old .net can get installed messing things up.
Hi. Same here. Cubase 12 - noticed when the ASIO Guard is on and I close key editor during playback I have a dropout. With ASIO Guard off everything is fine. PC - MB ASUS, CPU AMD Ryzen 7 5700G, 32 GB RAM, Windows 10 Home. Checked with my Cubase 11 installed on Windows 10 Pro on MacBook Pro 13" mid 2012. No dropout whether ASIO Guard on or off. Audio interface with both setup RME FF400. Buffer size doesn’t change anything.
My experience has been this: with ASIO guard on I was getting glitches as I shifted focus from track to track (i.e. selected different tracks). I went into preferences and under “Project & MixConsole” I disabled “Enable Record on Selected Midi Track”, “Enable Record on Selected Audio Track” and “Enable solo on Selected Track”. Now I can select different track while playing without getting those hiccups.
I can enable track monitoring or record without glitching but when I disable either it glitches. Sometimes just a minor audio pop but other times an actual hiccup in both audio and the GUI and at least once the track stopped playing back.
Yes, that’s a similar issue to what I’m experiencing as well. But, I haven’t had a track stop playing back - yet! From all the other user experiences shared here, there does seem to be some issues with C12. Let’s hope this thread helps Steinberg narrow down the causes and provides a fix on the next update!
Same thing here. Performance doesn’t only seem to be worse than CB11, but very “unstable”. It’s random to me, I can’t seem to make something out of it. Sometimes it’s decent, sometimes it’s unusable even in an empty project.
– Apple Mac Mini with M1 Chip, 16GB of RAM
– macOS Monterey 12.3 (21E230)
– Sample Rate: 44,1
– Asio Guard Level: Low, Normal, High: Normal
– Audio Buffer size: 256 Samples. That said: Changing the buffer size above 256 makes almost no difference, which is very weird.
– number of VSTi/ Audio/ Midi tracks: 32 Audio, 15 VSTi, 15 FX Channels. So not THAT much of a big project.
– VSTis in the affected project: AmpliTube 5, Serum, Diva. Some UAD stuff, some FabFilter stuff
CB12 of course running in Rosetta mode.
That same projects runs fine at 192 Samples in CB11. CB12 will not play it at 192 Samples.
Same Problem: Playback of whole project works fine. But live playing with single instrument tracks causes audio dropouts and cpu spikes. Also when switching between tracks.
Dropouts also occur when using some cubase plugins (not only external plugins), for example multi tap delay.
i7 12700K, 5Ghz, 12 cores
32 Gb ram
Windows 10 64 bit Pro
Samsung Evo Pro M2 SSD
has anyone tried the korg wavestate native or opsix native demo plugins?ive just installed them and it kicks the crap out of c12 but ok in c11 and ableton ive 11 lite.
i had one instance of it going asio meter went to max and started glitching,i opened the plugin and created a patch using only 1 lane the asio meter dropped to 75% …i then opened opsix played one sound it maxed out then crashed.
You all helped immensely to narrow the issues down, indeed! @djn14 , @Sparqee : As for your click-on-rec-disarm bug: there’s no fix yet, but a workaround. Briefly, the clicking appears, when the Asio Guard buffer has the same size as the audio interface buffer. To avoid that, you can e.g. chose AG low with anything <256; AG Normal with anything <512, and AsioGuard High with values <1024. Please let me know if this helped with your specific issue.
The stuttering/ heavy dropouts when playing record-armed VSTi tracks is a different thing. This happens on some intel CPUs and we need to readjust our audio engine to get rid of this bug. This issue is prevalent on systems with a medium number of CPUs (12 … 32), as far as I can see from your info, and is present for low latencies, like 32. 64 and 128 samples. You could try raising the buffer to 256 or 512, for now. We are working on a solution for this.