CMC-PD stops working again in Cubase 15 after latest update (was working in previous version)

In Cubase 15, my Steinberg CMC-PD behavior has been inconsistent across updates.

  • In the initial release, the device did not respond at all.

  • After a certain update, it started working again without any changes in my setup.

  • However, in the most recent update, it has stopped responding once more.

This is all under the exact same hardware and system configuration.

Standard PC keyboard shortcuts continue to work normally, so the issue seems specific to external input handling.

Given that it once worked in Cubase 15, I would like to understand:
Why was this functionality effectively removed again?
Was there a change in input handling, MIDI Remote implementation, or legacy device support?

Any clarification from Steinberg would be greatly appreciated.

Hi,
please, stick to one thread per topic. You have already posted the exact same content here 4 days ago:

Are the latest firmware and drivers installed?

Thank you for your reply.

I reposted the topic because my new thread did not appear anywhere on my side, so I became worried that the post had not been submitted correctly.

Since I do not speak English well, I may not fully understand the rules and behavior of this forum yet.

If I create a new topic and nobody replies to it, will the topic remain hidden indefinitely?
Or does it normally become visible even without replies?

I apologize if I caused any confusion.

Reco29, thank you very much.

As you instructed, I reinstalled both the firmware and the driver.

However, as you can see in the screenshot, the CMC-PD is recognized in the MIDI Port Setup (it was also recognized before reinstalling the firmware and driver), but when I try to add it under Devices, it does not appear as a Remote Device.

In the previous version, everything was recognized correctly.

Is there a site where I can download the previous version?

I have 3 CMC controllers - CH, AI, and TP.

They’ve all worked perfectly for years.

But today I noticed that although all three show up perfectly in CB Pro 15 MIDI port manager, only CH is working. The other two have a power light, but don’t work at all.

I believe this problem has been caused by the huge MIDI updates which are currently taking place to move us all from 1980s MIDI to modern MIDI2 and class compliancy - that is, no additional drivers required to be installed by the user - true MIDI plug and play, and a lot of other really good stuff.

However, it seems that there are currently problems as the developers deal with incompatible devices. I have tried with and without the traditional Yamaha Steinberg USB drivers and currently nothing works without these drivers, and only the CH works with them.

It seems that at this time the CMC series just isn’t compatible and this is why you see your problems. Each month the dev team is addressing more and more devices to bring them to work with the new and much better situation.

It’s important to note that this problem isn’t a Steinberg bug, but an industry problem while the new MIDI2 reaches maturity. I believe the development work is being done on behalf of Microsoft.

Fundamentally, some of these problems have been caused by devs of the traditional drivers over the years not keeping to all the rules of port handling etc in their coding and this has caused many problems for many people using traditional drivers since about February 2026.

We can only hope the devs continue to do speedy improvements to the MIDI2 code to include many more hardware devices. Once you do eventually get your stuff working under the new regime you will have a much more robust system than before.

I too find the current situation frustrating, but I also believe the wait for the final solution is worthwhile. We just need to keep a dialogue going so the devs include our products in the agenda for compatibility testing sooner rather than later.

I expect your current experience of the CMC controllers working one day and not the next is related to Microsoft updates which include new updates to the MIDI2 code. These updates have been pushed out without warning users, which to me is a problem, yet on the other hand, this is so complex I’m not sure how they could have explained what was happening to end users at the time. I just hope the current holes in the code get patched quickly and we can move on with our lives and use out MIDI gear without fear it won’t work apparently randomly.

I do not want to see my CMC controllers die a death just because of MIDI2. They may be a few years old now, but they are good controllers and fit my usage profile perfectly, and I have no desire to have to go out and buy new controllers.

SIedDriver, thank you very much for your detailed explanation.
This is very valuable information for me.

Of course, I also hope that the current issues in the code will be resolved quickly so that we can use our MIDI devices without worrying that they may suddenly stop working.

At the same time, before users decide to give up and dispose of hardware that temporarily stops working during this transition period, I would sincerely appreciate some kind of comment or guidance from the manufacturers regarding compatibility and future support.

I truly hope these excellent CMC controllers will continue to have a place in the new MIDI environment.

@SledDriver so far my CMC units are working - is there a way that I can tell whether that’s because I’m on an old system update, and if so, how do I prevent new ones before they fix the issue?

Many thanks!

A class compliant device running under MIDI2 will show as having a Microsoft driver, and not a driver from the original manufacturer of the hardware. For example this M-Audio Midisport 4x4 Anniversary Edition (note not the earlier version which is not class compliant).

Well, I booted up this evening and I must have agreed to a windows update when I last powered off, because it ran (slowly) today…

Anyway my 8 working devices are now down to one - the AI.

Are we confident at this point that this will be resolved? If not, is it possible to roll back?

Although I’ve seen spurious reports here, I’m not tracking anything specific to the CMC, and so we’re not currently fixing anything specific to the CMC.

If someone wants to walk me through what you see vs what you expect, and maybe also take some repro captures, I can see if it turns up anything useful. Easiest to do this on the Discord server so I can leverage what’s already there. Windows MIDI / Audio

Pete
Microsoft

Psychlist1972, thank you very much for your reply.

Here is the information from my current environment regarding the CMC-PD issue.

  • Windows edition: Windows 11 Home

  • Version: 25H2

  • Installed on: April 24, 2025

  • Cubase version: Cubase 15.0.20

Unfortunately, I do not know exactly when the issue started.

The affected device is:

  • Steinberg CMC-PD

Current MIDI port status:

  • The CMC-PD appears correctly in the MIDI Port Setup window in Cubase.

  • The device is also visible in Windows Device Manager.

  • However, it does not appear in the Remote Device / MIDI Remote device list, so it cannot be assigned or used as a controller.

I also tried going back to Cubase 14, but the behavior remained the same.

Thank you again for your willingness to investigate this issue.

Hello @Psychlist1972, I’ve posted in the Discord chat here: Discord

I’m not really familiar with Discord, feel free to reply to me here or over there if I can provide any more information.

Thanks, JP.

I’m delighted to say that I have all 8 of my CMC units working again, check out the Discord thread for full details. Thanks to @Psychlist1972 for your help over there.

@touchup1954 @SledDriver CMCs are all working for me again, give me a shout if you get stuck.

Can you summarize the necessary steps here for those who don’t have a discord account, please?

Glad you got them all up and running again :+1:

Same issue here, 3 CMCs only one show up or allow it to be added. I have many other controllers (5ssl + others) that work fine.

Here’s the process I went through to get my CMC units working again.

Step 1: prep

  1. Is one of your CMC units recognised by Cubase under the Remote Devices (Legacy) section? For me it was the QC:

  2. Make a note of how that unit is named in the MIDI ports section:


    For me, it didn’t have a number at the start, whereas the other units did

  3. Click the monitor button next to one of the non-working devices and then press buttons, turn knobs, etc, do you see MIDI data? If yes (just needs to be on one port if there are multiple showing for the same unit) then the unit is live and visible, so hopefully the next steps will work.

Step 2: changing the names of the MIDI ports

  1. Go to this link and download the MS MIDI settings app: About Windows MIDI Services - Windows MIDI Services .
    The actual download button appears near the top of the screen for me:

  2. Run the MIDI settings app (start typing MIDI settings in the Windows search box and it should appear)

  3. The next step is to follow the on-screen prompt to complete MIDI setup and create a configuration file. The configuration file is where the MIDI port name settings, loopbacks, etc. are all stored. I can’t screenshot this as I’ve already done it so that option isn’t showing any more. If someone else can screenshot I’ll edit this post and add.

  4. Go to the MIDI Devices and Endpoints option on the left:

  5. Select one of the CMC units that aren’t working - this is how the PD shows up for me (three MIDI instances):

  6. Select Personalise from near the top of the next screen:

  7. There are three options for renaming the ports in a dropdown. IGNORE THEM ALL! Instead, go to the custom Name section and type in the format that was working at prep step 2 in the post above


    Please note, if you have multiple instances of the same device, you have to rename all of them (just renaming the first one didn’t work for me)

  8. Final step! Well done if you’ve got this far :slight_smile: If you have more than one CMC-FD unit, unit 1 works using the method above but you need to name units 2+ differently. Here’s my second FD:

I hope this process works for everyone else, good luck and let me know if I’ve mis-explained any of the steps.

Here’s part of the end result showing the additional FD units in Studio Setup after renaming the ports.

Hello jpspoons1,

I just wanted to let you know that everything has now been completely resolved.

Your explanation about Windows MIDI Services, endpoint names, and the Custom Name settings pointed me in the right direction.
After a lot of troubleshooting, I discovered that the issue was not hardware failure, but Cubase’s MIDI configuration/cache becoming corrupted after the Windows MIDI Services changes.

Thanks to your detailed post, I was finally able to understand what was happening and recover the system.

I really appreciate the time and effort you put into documenting the process so carefully.
Your information was extremely valuable.

Thank you very much!

You’re very welcome, I’m glad it helped - and it sounds like you understood it better than I did! :grin: