Cubase 14 midi working in frist project opened, but midi out stops working in next

Cubase
1

Win 11, cubase 14, UAD, Miditech 16x16, Motu 128 Express all updated. When opening Cubase all works fine, both new projects and resent. But if I switch (close - open another) midi out stops working on all channels, and nothing can get it working again. Have anyone had this issue? I don’t really know how long I’ve had it because I don’t switch that often between projects in the same session(just a happy amateur with too little time)

Thanks!

2

Hi and welcome to the forum,

What exactly does it mean that it stops working? Can you see the MIDI Output MIDI Ports? What does the MIDI monitor say?

3

If you fully close Cubase (every Cubase window) before going in and opening the second project, does it work?

Are you connecting or disconnecting the MIDI device at all during this process?

Pete
Microsoft

4

Thanks! Recorded midi events do not play “through” to the midi interface - out channel LEDs on the interfaces do not light up, and no sound is played on the external synts.

Cubase midi monitor and midi activity bar shows the data. And recording (in) works all the time.

If I close Cubase completely it will work again until I close down the project and open the same or another. Same things happens with templates.

I don’t mess with the interfaces in any way - no connecting or disconnecting. Also no other software is running. The computer is used almost exclusively for music.

Thanks for taking the time to help!

5

Next question. Can you run the tool found here (top of page in the big box)

Run from a Windows Terminal instance, not just double-click, and tell me if that reports you have the new MIDI stack enabled (feel free to paste in the screen shot). If you have the new MIDI stack, it may be an issue there, otherwise, it’s something else.

Pete
Microsoft

1 Like
6

Thanks!

I’ve tried to run the midicheckservice.exe in CMD but it blinks and no results are displayed. I’ve tried /k, &&pause, /k ipconfig still no results will display. I’m not sure I run it the right way - it’s more than 20 years since I last did any programming :slight_smile: I did google some solutions but no luck making it work.

7

You need to run it from a Windows Terminal instance, not just double-click it.

Easiest way

  1. Unzip the zip
  2. Go into the created folder
  3. Right-click on some empty space in the folder and choose “Open in Terminal”
  4. Type .\MidiCh and hit tab key to auto-complete the full name
  5. Hit enter

image
image367×430 16.2 KB

You’ll get something like this

image
image1424×622 22.3 KB

Pete
Microsoft

8

I’ll likely put out a version of the tool this weekend that you can just double-click. It was mostly intended for developers and for apps to run automated, so I didn’t have a pause built-in.

Pete
Microsoft

9

Thanks Pete,

Result:

-wdmaud2.drv is not present in registry in values midi-midi9. Most likely, the feature has not yet been enabled on this PC.

—-

Looking forward to understanding what this means for the issue

Thanks!

10

It means the issue is not related to the new Windows MIDI Services rollout, because that’s not yet enabled on your PC.

So there’s something in Cubase or the device.

You can’t open a port twice or by two apps in the older MIDI stack, so maybe something in Cubase isn’t closing and releasing the MIDI port when you switch between projects.

The new stack would hide any issue like that, because every port is now multi-client.

Pete
Microsoft

11

Thanks Pete!

So the ball is in the Cubase corner.

Have anyone seen this issue?