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 
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