My Steinberg CC121 was working fine and then suddenly stopped working. I’m not sure if a Windows update caused it, or updating Cubase 15 to the latest version caused it, or something else caused it. I have disconnected all devices from my computer except for the cc121, I have uninstalled and downloaded and installed the latest driver for the CC121, and nothing works. I tested the cc121 on another PC computer using the same USB cable, and it worked fine. I have spent days trying to fix this and I still cant find the problem. Help!
Have you plugged it in and powered it on (I don’t recall if it has a power button) before starting Cubase?
Pete
Microsoft
1 Like
Hi @Christopher_Mexas . I went to the archive and resurrected an old CC121. I installed the drivers from here. I’m on Windows 11 at a current state and was testing with Cubase 15.0.10. I made sure that CC121 was connected and powered on before starting Cubase. It worked right away for me. I didn’t notice anything not working. I’ve checked both “Windows MIDI” and “WinRT MIDI” setting in Cubase (Studio Setup… / MIDI Port Setup). Changing MIDI Port Setup may require restarting Cubase for CC121 to be recognized correctly.
Just for info
Latest Cubase pro and latest windows 11.
CC121 working fine.
1 Like
Mine did’nt connect anymore after I got the new MIDI service about 2 weeks ago. Got it back working by changing it to the classic API, I don’t know what the difference is. It does need Pete’s MIDI tools, but first you should check if the new MIDI is enabled on your pc.
Release App SDK and Tools Release Candidate 3 + Basic MIDI 1.0 Loopbacks · microsoft/MIDI · GitHub
I have tried all possible varieties. Powering on after or before doesn’t make a difference. Thanks for your suggestion!
This solution might work, I didn’t even know there was a windows setting. I have never seen that screen that you sent. Is that part of what you called Pete’s MIDI tools? If not, could you please guide me so that I can find my way to that screen?
@Hurmpie , it looks like the tool you show in your screen shot is from an application that is mentioned in the link you sent. I will try that. Sorry, I didn’t see the link until after I sent my previous reply.
@JRoeper , I have not looked into the “Windows MIDI” and “WinRT MIDI” settings in Cubase (Studio Setup… / MIDI Port Setup). I will take a look tonight and see what I have in that particular location of the Studio Setup. Thanks for the advice!
1 Like
I insalled Windows.MIDI.Services.Basic.MIDI.1.0.Loopback.Preview.1.0.0-preview.1.2-x64.exe and I installed Windows.MIDI.Services.SDK.Runtime.and.Tools.1.0.16-rc.3.3-x64.exe. I also installed midicheckservice_x64
I ran midicheckservice_X64 after installing the first two, but I still get:
Looking for wdmaud2.drv in registry
- wdmaud2.drv is not present in registry in values midi-midi9. Most likely, the feature has not yet been enabled on this PC.
- The new Windows MIDI Services stack is not functional on this PC.
Im not sure if I did something wrong or if this simply doesn’t work on my PC
The new MIDI services for 25H2 has been known to cause all MIDI devices to not be recognized. I’d stay away from this for awhile until everything has been sorted.
https://www.pgmusic.com/forums/ubbthreads.php?ubb=showflat&Number=882303
Won’t detail it all again, but I had to roll back to Win 24/10 and trash prefs to regain stability. I am no tech but my gut is telling me that data is arriving fractionally late at ports, which is sometimes OK and sometimes not, according to the receiving apps whims. This is only my meme, I can’t see any code. There are definitely port issues. I am sure this will work out. Really looking forward to a world of MIDI 2, plug and play hardware, AI interaction with CUbase Interface.
I think maybe it’s wise to hold back a little, maybe use system restore before changes.
There is a Discord thread with Pete from MS. Here you find the latest advice.
Z
Which version of Windows 11 are you using?
Is the MIDI service already running as a service on your system?
Do you use any other controllers or keyboards that require a manufacturer-provided driver?
Drivers from the manufacturer Korg, for example, cause errors in the registry. There is a tool from Pete/Microsoft that fixes this error. It is important to completely remove the Korg drivers beforehand and use the Microsoft drivers.
M-Audio drivers must also be removed, as these can cause the MIDI Service to crash.
As far as I know, the tool for Loopback 1.0 can only be activated in Developer Mode.
For my part, there are still many unanswered questions as to why the controller isn’t working yet, as all the points mentioned could be contributing factors.
I did (or do, im not sure) have a Korg Driver installed for my Korg SV-1 keyboard. I have unplugged this device and all other devices from my computer, hoping that this would help it recognize the CC121. I think that this may be related to the problem but I just don’t know if unplugging the korg and the other synth (Yamaha MOX6) is enough
I did set windows to Developer mode. I tried turning this off after i ran the Loopback application, but nothing changed. I now have it turned back on. Now when I go to the loopback installer, the onl option i see is to uninstall it, which leads me to believe that it is installed. The same thing happens with MIDI.Services.SDK.Runtime.and.Tools.1.0.16-rc.3.3-x64.exe. They both seem to be installed, because if I run the exe’s again, the only option I see is to uninstall. Could it be that I installed these in the wrong order? I think I installed “Midi Services” first and “loopback preview” second, but I don’t remember.
Im not sure if I went to 25H2 version of windows and then went back to 24H2. The last 3 entries of my windows update log look like this:
From what I have been reading, the update on the bottom of this list is the one that should have taken me to 25H2, and I believe that’s where the MIDI service updates should have started and that’s when my problems with CC121 started. I really don’t know that much about this so maybe Im talking nonsense. If there is any extra information I can share with this forum to try to get to the bottom of this, please let me know.
If a Korg driver is installed, unfortunately your approach won’t work.Here are instructions on how to completely remove the Korg driver.The manufacturer’s Korg driver negatively affects your registry.
Your registry must look exactly as shown in my screenshot. The name ‘Korg’ must not appear anywhere.
1 Like
In the registry, the values “midi” and “midi1” are important.
“midi1” must contain “wdmaud2.drv”.
This is the new Windows MIDI service.
I woud uninstall the SDKs for now. Until the registry has been fixed, this is another factor that could be causing errors.
Loopback 1.0 is also something that requires some experience to install.