Cubase 12 Upgrade ASIO-Guard Issue

Exactly. Technically, I’ve always believed manually disabling ALL modes of power-saving is much better than just enabling Steinberg power scheme. Yet somehow…hmmm. Weird. Oh well.

Still looking for some settings you have in common, and I don’t use. This led me to the Midi Controller section in the Studio Setup.
Could you post your Midi Port Setup? I’m especially interested in the your settings regarding “DirectMusic” and “WinRT MIDI”:

Thank you all for your great support here!

Here is my midi setup. Thanks again for your continued help!

midi setup1

1 Like

I did post earlier in this thread that I had the dropout overload issue with C12 on macOS Monterey

Apple Intel
macOS 12.2.1
Mac mini 2018 3.2 GHz 6-Core Intel Core i7
Intel UHD Graphics 630 1536 MB

1 Like

SD3=Superior Drummer 3

I think you got me wrong, I did try the Steinberg Power Schmeme. Actually I’m using it currently. It just doesn’t do anything for me and the performance problem of C12.

These are my settings. All MIDI-ports are USB, except for the MIDI port of the Multiface. That is not in use currently.


Just a quick update.

There is still an occasional CPU spike and audio ‘pop’ even on a very light project of just a few plugins. This seems to be more likely if a track is record enabled.

The problem is not nearly as bad as it was however. I can at least work around this in most instances whereas before I could not. (I have not tried exporting a mix down yet however.)


1 Like

Hi Chris , sorry but what is MidiRT anyway? Google did not bring me an answer.

@vinark : I have no clue what WinRT MIDI exactly stands for, sorry. But I guess it’s got to do with Real Time (?) Midi on Windows.

Last idea for today: could this Asio Guard issue have to do with audio warp/ tempo editing ?

As I understand it, this is the new MIDI over bluetooth feature of C12.

Not in my case, sorry. While I did have a couple of audio warp edits in some of the audio files, I just tested it with bouncing all edits to new files, but nothing changed.

And then: I made those edits in C11 and since everything works there, it is most likely something else.

1 Like

Yeah that’s it, MIDIoBT, but hey let’s call it WinRT and confuse everyone huh. :face_with_symbols_over_mouth:

WinRT is “Windows Runtime”. It’s a newer set of APIs that Microsoft exposes for creating software for Windows. It has new APIs for many things, including MIDI IO. The older MIDI IO APIs were notoriously problematic. The WinRT MIDI system has its own set of problems, though.

Even their own page on the subject doesn’t explain why it’s called WinRT.

Just a completely unhelpful name made up by some non-public-facing developer, and which will confuse many for years to come. You know… like…

MIDI - Musical Instrument Digital Interface
WinRT - Musical Instrument Digital Interface over Bluetooth.

It even explains that " WinRT is not a runtime in a traditional sense"

Just DOH! Let’s make it completely unnecessarily incomprehensible - or VGYQP for short. :grinning:

See my post above.

I did see that.

And would you like to explain how this ever helps the end user?

I’ll try: there are two main ways to create MIDI IO software on Windows. The older way and the newer way. Microsoft calls the newer way WinRT. (Note, WinRT is much more than MIDI, and MIDI in WinRT is much more than Bluetooth support.) Cubase allows the user to choose which they want Cubase to use. This is good because both ways have unique issues.

Since WinRT is the name given by Microsoft, I’m not sure what else Cubase would call it. “Old-style” vs “New-style”? WinRT is probably the most accurate name for Cubase to use.

For the record, Cubase crashes when I use WinRT MIDI, so I suppose I’m glad they offer both.

1 Like

Thanks for that. Very useful.

Considering in the thread above users are already confused, surely in the user interface it would be much better to use something like:


than just


and leave lots of people not understanding what they are seeing?

User interface is supposed to help people, not confuse them.

To be clear, MIDI via Bluetooth is just one feature of WinRT MIDI. So calling it MIDIOverBluetooth would be very confusing. One can use WinRT MIDI without using Bluetooth at all.

OK, but WinRT seems to be about as unhelpful as they could have made it.