Cubase 16 forgets Yamaha CC1 in W11

My Yamaha CC1 is not seen and no more usable by Cubase 16 as it was in Cubase 15.
I can open The w11 CC1 control center version 1.3.0 installed with CC1 tools v 1.2.1 from 07/2026. The CC1 is connected, but no more seen by Cubase 16 as it was with Cubase 15.
Any fix welcome.

Annoying especialy because Yamaha is the owner of Steinberg.
I hope this issue will be fixed ASAP.

i really wanted to buy the cc1 but it seems yamaha/steinberg havent got a clue what to do with it..you never see or hear anyone talk about it on the official steinberg youtube channel..all the steinberg shills no longer have it on there desks or mention it..

it seems as though they made it ,had some idea what too do with it then someone has come in from high up and said your not getting any resorces or funding too work on it.

i bet when black friday comes along yamaha will dump aload of these for blow out prices just like they have with lots of there products.

Not sure, it is a very nice piece of hardware.
The problems seems more political between Steinberg and Yamaha.
Yamaha is a huge mastodont with very slow movments, I still hope they have not published the new CC1 Tools adapted to Cubase 16 changes and will release it asap.

Thanks for the heads up. I’ll hold off on cubase 16 for now.

My CC1 didn’t work when I first launched Cubase 16, but it’s now working flawlessly on second launch and beyond.

CC1 firmware v1.0.1
ControlCenter app v1.3.0
Cubase v16.0.5.174
macOS Tahoe v26.7.2

I am on W11, last 26H2.
I will fix my title, thanks.

I just notice that you are in firmware 1.01 where I am in 1.0.0 , are you sure ?

I believe so!

CC Tools v1.2.1 includes CC1 firmware update v1.0.1: TOOLS for CC1 V1.2.1 for Windows 11/10 (64-bit) - Yamaha USA

And for Mac just search google (worked fine after install): TOOLS_for_CC1_V121_Mac

I am stiil without CC1, it seems to be Ok for Apple, not for W11.
I opened a ticket at Steinberg.

This is ,what I used Tools for CC1
Should I uninstall and reinstall these Tools for CC1 ???

Did you note this?..Only administrator users can install TOOLS, and only the user who installs it can use Control Center.

Also, maybe contact Yamaha support first.
https://usa.yamaha.com/support/contacts/form.html?page=product

I installed it in May and applied udates until 1.2.1 in July, and it worked with Cubase 15, but not on Cubase 16.

It seems to be a Steinberg problem first, because Yamaha changed nothing, even if we all expect some fix and were disapointed seeing the one update by month stopping in July.

@DosWasBest, are you owning Yamaha CC1 and on Windows ?

Gave it a shot. Not working for me- Win11.

I’m starting to suspect that my problems are also due to the rewriting of the internal MIDI stack in Cubase 16 to properly use the new MIDI services. Even though the Yamaha CC1 doesn’t use these services in the same way as a standard USB controller, contrary to what I told Pete Brown, @Psychlist1972 , at Microsoft. I hope he can shed some light on this new problem given his extensive knowledge of the Cubase-Windows MIDI Services ecosystem.

Here’s what I’ve done to try and find a solution, and I think I’ve made some progress with my latest attempts:

1 - Uninstalled Tools for CC1 1.2.1 and then installed versions 1.2.0 and 1.2.1. This is for two reasons: I’m not sure I have the correct firmware on my CC1 (see my previous post) because I installed version 1.2.1, skipping version 1.2.0, which was responsible for updating the firmware to 1.0.0.1. Version 1.2.0 should have provided that update.
2 - I verified that the CC1 still works under Cubase 15.
3 - I verified that my project, migrated from Cubase 15 to Cubase 16, was working.
4 - I created an empty Cubase 16 project and added an instrument track to check if my CC1 was working. And there were some surprises, but I still didn’t get it to work.

I’ll go over these points again. For uninstallation, I used the standard uninstaller, searching for the installed Yamaha applications. It turns out that the Tools for CC1 visibly install three types of applications:

  • Yamaha CC Virtual MIDI Driver
  • Yamaha CC1 Control Center
  • Yamaha RemoteControlExtension

And it’s precisely this presence of a ‘Yamaha CC Virtual MIDI Driver’ service that makes me think the modifications in Cubase 16 for MIDI also affect the CC1, even though they aren’t related to Cubase MIDI Remote (even in C15, the CC1 never appeared in Cubase’s ‘Remote Devices’).
Note that installing version 1.2.0 of the Tools installs all three apps, while version 1.2.1 doesn’t reinstall this ‘Yamaha CC Virtual MIDI Driver’ service, which, for me, is therefore working correctly in its previous version.
After installation, Control Center version 1.3 still doesn’t allow me to see my firmware version, simply displaying a “Firmware update” line followed by an icon that seems to represent a… Clock (???). So there’s no way to know if I’m actually on firmware 1.0.0.1 :frowning:

However, when I open Cubase 15 and my projects, I see that everything works as before: the transport controls, the infinite scroll wheels, the Elgato-style buttons, and the various track-specific buttons.

The next step is opening Cubase 16 with my migrated project. And that’s where the disappointment comes in—nothing. Reinstalling Tools for CC1 in version 1.2.1 didn’t save any potential add-ons for Cubase 16.

I then had the idea to start a new project from the ‘New Empty Project’ button in the Cubase 16 hub. I added two instrument tracks. And surprisingly, the track volume fader works on the selected track, as do some of the ‘Elgato’ buttons, like the zoom controls. However, there’s no transport control and none of the track-related buttons, like Record and Monitor, or Track Switching, work. etc.

Following this partial failure, I abandoned the CC1 problem and reopened my old migrated project. There, I decided to test Waves’ new subscription-based Illugen plugin, which Steinberg is promoting as they did for Tonalic (another topic of discussion on Cubase vs. Artificial Intelligence…). So I subscribed for two months and installed the plugin with the Waves installer (a bit long), then opened its window in Cubase. Why mention all this? Well, curiously, while Illugen was offering its text input window to generate a sound, I pressed one of the Elgato buttons on my CC1 (one of the Zoom buttons on the Projects page). And I saw letters appear in the Illugen input window! When I switched to another button, they were different letters. So, the communication regarding these buttons is working correctly from CC1 to Cubase, but then Cubase 16 handles it poorly. The transport controls and the track buttons are stubbornly inoperative, as are the input area buttons. Is this related to the focus issue mentioned in other Cubase 16 threads? Is it related to accelerators that changed after the settings were reformatted?

I also think that all these elements might help @Psychlist1972 understand the origins of the problem and find a workaround or a fix.

I add some screenshots from my various steps.

Cubase16-Illugen-CC1.mp4

I just add that Steinberg support asked me to recreate my settings by hidding their folder (and any older version) and running Cubase, which recreates clean settings.
As expected nothing solved, so if you are in same situation with non working Yamaha CC1 and Cubase 16, do not waste your time trying this. :slight_smile:

I’m having the same problem.
@csurieux Thanks for the helpful information!

I’m not in any rush, though; I’m fairly confident that Steinberg—or rather, Yamaha—will resolve the issue.
Yamaha has announced an update for the end of the year regarding CC1 and the new MGX mixers.

Thanks.

If you are using “Windows MIDI” in the Settings for Cubase, then there are no MIDI stack updates in Cubase that I am aware of. Are you using that, or Windows MIDI Services?

Is it telling you a firmware update is in progress, or that one is needed?

Apparently the CC1 app requires you let it through the firewall.

You can manually do that in Windows by searching for “Allow an app through Windows firewall”, assuming you’re not using a third-party firewall product.

Pete
Microsoft

Pete, I needed AI to get CC1 back to work. The AI claimed a naming scheme mismatch from Cubase15.exe to Cubase 16.exe (empty space broke the connection?).

Can’t verify or falsify, but this would really be a stupid kind of bug if true.

I also had no firewall problem with CC1 before updating it to the latest version. Now I have one again and have to program my firewall to let it through.

Yamaha is really sloppy and bad at making CC1 work as it should, and Cubase 16 seems to add a connection problem on top.

I also had to delete and re-establish ALL of my midi controller connections in Cubase 16 Midi Remote. They were simply greyed out and could not even be clicked for editing. Not smart. And what the heck have all the beta testers been sleeping on durig the last months???

Just to be clear: I have a lot of respect for you and your work and only adress you, because I regard you as very competent partner able to analyze and discuss issues with Steinberg staff.

Pete,it is working quite perfectly on Cubase 15.
Problem is in midi (Yamaha CC Virtual MIDI Driver and its handling) and cubase16 from my previous post to be read in details (see the Illugen paragraph).
My Cubase midi setting has not changed from Cubase 15 : MME.

Just to be clear:

If it works on Cubase 15 on the same PC that it fails with Cubase 16, the problem is not Windows MIDI or the driver. It’s something else. Steinberg has adopted the new API as an option. However, Windows MIDI Services on your PC is what is running behind MME/WinMM, WinRT MIDI 1.0, and also the new API. They all point to the same service, naming, etc.

Jim said AI claimed a naming mismatch. @jim_knopf can your agent be more specific about the problem? I’m looking to see if there’s anything at all I need to look at in Windows, or if this was inside Cubase.

Port/Device naming kills me. It’ll never be 100% right because so many devices have wonky implementations :frowning:

Pete
Microsoft