Cubase 16 forgets Yamaha CC1 in W11

To illustrate, I had my clanker do a couple quick very high-level diagrams to show how this works.

And without Windows MIDI Services available (Windows 10, or a PC using Legacy MIDI API Mode)

Pete
Microsoft

Sorry but not sure because, evidently from our Triple Play experience, in MME Steinberg has changed the way Cubase deal with midi.
Have you read the paragraph concerning what I discovered using Waves Illugen extension and the routing of cc1 midi to the keyboard input of Illugen, a clear handling bug, see the video/picture?
Concerning AI, sorry but I fear we are on a clear hallucination.

I have no idea what Waves is using to get the data.

But I also don’t understand how that factors in, or what point it is making. I watched the video, and it shows some letters come into Cubase. Are those MIDI or are they HID? I have no idea.

But again, if it’s working in Cubase 15, it’s not in the Yamaha CC Virtual MIDI Driver or its handling, and not in the MIDI stack in Windows.

Your Triple Play experience was completely different. Cubase 15 makes the same calls. If you do exactly the same thing in Cubase 15 as you did in 16, you will get the same result. Ensure Cubase 15 is set up to send SysEx Id requests, not MIDI-CI, start it with your USB dongle plugged in, but the guitar pickup turned off. You may need to start Cubase 15 in a safe mode or something as I don’t recall if it caches the SysEx Id results for MIDI ports it has seen in the past.

I’m only going by what Jim reported. Naming differences are a very common reason for MIDI Remote failures in Cubase. But those names would be the same on Cubase 15 and 16, at least on the device side, because that’s all set in Windows.

Pete
Microsoft

Well, I have been doing dozen of project with triple play usb pluged and not connected to the TP master on guitar, and none of these projects has frozen when initializing midi on load.
I certify.

Certainly, I have been working on C++, C#, Javascript devs for dozens of years, I know.
But here CC1 uses no javascript, and no midi remote, all built with Qt (from hundred of logs left on disk and with very strange things but it’s another subject)…

As I mentioned above, I have the exact same problem with the CC1 controller.

After installing Cubase 16, my CC1 was no longer recognized.
All my other MIDI controllers work without any issues with Cubase 16.

My system: Win11 26H1, latest updates,
Cubase Pro 16.0.5, Yamaha Tools for CC1: V121

I haven’t installed Microsoft’s new MIDI 2.0 tools yet and as mentioned above all other MIDI controllers are working fine.
So, I guess this is not a Microsoft problem.

Maybe someone can help

Regards, Gottfried

I think you missed what I was saying.

If Cubase does a MIDI port name match 1- Foo is not the same as 1 - Foo is not the same as Foo or Foo(1)

That has nothing to do with language or UI toolkit used. It’s also nothing specific to the CC1. But it’s a common reason why some MIDI Remotes stay “grayed out”, which is what Jim ran into. I’ve helped folks with that with Cubase 14/15 in the past and also with scripts used with StreamDecks which all have the name match failures. It’s part of why you can rename ports in Windows now.

Usually that comes from migrating an older project or configuration from last year before the MIDI updates were in Windows, because port names did change in some cases.

But I wouldn’t have expected them to change right now, between Cubase 15 and Cubase 16 installs on the same PC.

And after the first time, it stopped happening on Cubase 16. Is that still the case? Different thread, so please follow up there if it is continuing to fail. Again, it does not seem at all related to the issue discussed here, and the same or meaningfully similar things have been happening with Cubase for years. Once I found out what the root cause was, I was able to find forum posts here going back a ways with Cubase locking up on initializing MIDI, due to the same call. But back then, it only locked up Cubase because there was no MIDI Service. In any case, if this is still having issues in C16 on the same PC as C15, where both were previously working, that will be good to add to the other thread.

Pete
Microsoft

Ok, may be I misunderstood.
But this cc1 code have not changed, so where could be the pb ?
It works for C15 and not for C16 ?

Here’s the complete AI analysis of the CC1 connection problem:

"Yamaha CC1 not working with Cubase 16: executable name has a space

Symptom: With Cubase 16, the lower section of the CC1 (faders, transport) did nothing, while the Stream Deck section on top still worked.

Cause: Yamaha Control Center uses a bridge plug-in (com.yamaha.cubase.ypPlugin). It only connects to the Cubase executables listed under applicationsToMonitor in its manifest.json. Earlier versions are called Cubase13.exe, Cubase14.exe and Cubase15.exe, without a space. Cubase 16’s executable is called Cubase 16.exe, with a space. Even after updating to Control Center 1.3.1 / Remote Control Extension 1.0.3, the manifest only listed Cubase16.exe (no space). The bridge therefore never recognised that Cubase 16 was running.

Fix:

  1. Back up ...\Plugins\com.yamaha.cubase.ypPlugin\manifest.json (inside the Yamaha Control Center plug-in folder).
  2. In the applicationsToMonitor list, add the line "Cubase 16.exe", (keep the existing Cubase16.exe entry).
  3. Restart Yamaha Control Center, then restart the Elgato Stream Deck software (StreamDeck.exe). Otherwise the Stream Deck section goes dark.

After that, the CC1 worked with Cubase 16 again. Note: a Control Center update overwrites the manifest, so check the entry again after every update.

You need Control Center 1.3.1 with Extension 1.0.3 or later. With the older Extension 1.0.1, Cubase 16 did not open the connection port (TCP 49345) even with the corrected manifest. You can check whether Cubase is listening with this PowerShell command:
Get-NetTCPConnection -LocalPort 49345 -State Listen"

@Pete I do not envy your job - this looks really complicated. All the best!

P.S. AI note for Pete:
this issue is not MIDI-related. The Yamaha bridge talks to Cubase via a local TCP connection (port 49345), so Windows MIDI Services are not involved. The cause is only the missing "Cubase 16.exe" entry in Yamaha’s manifest.

Not exactly, the upper, Elgato like, section do not totally works.
But what you say could be the solution, thanks.

csurieux:
try closing Streamdeck and restarting it.

So it could be this plus the firewall issue in your case?

Tell your agent “Thanks”. And also thanks to you for the updated info. This is making much more sense now.

Just verified on my PC that the exe name has a space now:

image

Pete
Microsoft

What I don’t understand is that you are saying that in this manifest, yamaha has written all the futur cubase versions ??
Cubase15, cubase16, cubasexx ?
Or they used some generic ?
I am not in front of my PC now and can’t check.
Crazy.

I was already knowing that CC1 starts a background process unfortunately named cubase (name in the control center for Cubase dedicated pages) . And this name blocks Arturia and Waves plugin update because they check for an existing process starting by ‘cubase’, so they ask to quit cubase… when it is CC1 Control Center which is running
Poor Yamaha software not tested in real situation.

But it has no firewall pb with cubase 15. Strange.

I downloaded the Yamaha Control Center and let it install everything, but this folder doesn’t exist. Is it supposed to be located under C:\Users\Pete\AppData\Local\Yamaha\ControlCenter on my PC?

I also checked the VST plugin folders etc.

The only plugins folder in the ControlCenter folder looks to be Qt plugins, not Cubase or similar VST plugins.

Is another app install needed?

Pete
Microsoft

Maybe this is the real problem?

I installed the tools and drivers

image

But the Yamaha “bridge” plugin doesn’t exist anywhere on this PC. Agents seem to think it should be named “Cubase.YpPlugin.dll” and installed in one of a few different places.

I have Cubase 14, 15, and 16 installed.

I don’t have an actual CC1, so will only be able to get so far, regardless.

Pete
Microsoft

JFC on a crutch. Finally found where the plugin is installed. Yamaha should know better, but so many companies do this now. Binaries do not belong in the roaming appdata folder, FFS.

On my PC, the plugin is here
C:\Users\Pete\AppData\Roaming\Yamaha\ControlCenter\Plugins\com.yamaha.cubase.ypPlugin

And there is the incorrect exe name, exactly as @jim_knopf said.

Pete
Microsoft

It’s working now!
THANK YOU VERY MUCH for your help!
All the best, Gottfried

@Matthias_Quellmann

FYI on this CC1 problem. Short of it: Cubase16.exe is in the CC1 Control Center manifest, but Cubase 16.exe is what you shipped.

I assume the fix needs to come from Yamaha. @jim_knopf 's clankers found the workaround.

Pete
Microsoft

For Cubase 17 they will need to extend the list. What a poor dev.

Strange idea from Steinberg to add this non usual space.
May be should they publish a fix without this space in the process name.
Yamaha is the owner :wink: