OK, So Cubase is running very well once opened but I’m stilll getting Hub freezes every couple of days that require a reboot as Cubase will not quit from task manager when this happens, it’s holding on to something for a LONG time as it will eventually quit after 10=15 minutes.
PLEASE DO NOT ASK ME TO USE WINDOWS RT …why?
becasue… I’ve now changed out my AXR4 for an RME ufx III, and also my CC121 for an X-Touch one in an attempt to stop the freezes and the RME midi does NOT work at all with windows RT neither does my Nektar keyboard…both new products.
In an attempt to get a stable system I’ve now just spent a few thousand euros and expcept for this HUB freeze it’s working brilliantly, surely there’s a workaround or something elese so this doesn’t happen, none of my midi/audio hardware has ANY issues at all with Studio One or Reaper.
Any ideas?
this is the freeze dump error. What exactly is causing this when the hub opens? I’ve replaced my hardware and it’s still happening? is it a EUCON thing perhaps? can I stop the HUB somehow? It’s saying ‘Midi OUT device’ which one? I replaced the CC121 becasue of this is it was the only thing connected with midi in and OUT . Or is it MIDI OUT from a device NOT Cubase?
here’s my Midi devices. I’m not sure why there seem to be double of things. For example the UFX only has 2 midi IO and it’s showing 4… all devices have 2 entries . The Arduino is the Crumar Drawbars .
Well this seems to be a well known problem in the Microsoft MIDI API. There is a long known article on the Microsoft site that recommends to use the WinRT interface instead.
The problem seems to be in some kind of plug-and-play functionality, as Microsoft says after a Removal event.
So you can either try to switch to WinRT in the Studio Settings, or try to connect all your devices, restart the computer and then start Cubase. This should (in theory) not have a removal event and allow to proceed.
Just a wild guess, but more is not really visible.
I spoke to Pete brown at Microsoft and he said there’s no issue with windows WDM midi.
Is there a specific way to get windows RT to work? I’ve tried so many times and despite it re scanning and things shoing up, there’s no actual data being received from the devices when i chose this option
However there is NO midi data going into cubase at all. I can see on the UFX that midi data is being recdeived but it’s NOT getting to Cubase from ANY device connected.
Just rebooted again and despite everything showing as active Cubase is getting zero midi information from any of my connected hardware with the midi RT set.
Only thing that is midi related is my x touch one is receiving midi from cubase as it’s lighting up the tansport start stop buttons , but there’s no midi activity GOING to Cubase at all.
I’d read it that way:
2 x MIDI In via 5-pin DIN jacks
2 x MIDI In via MADI
= 4 MIDI Ins
2 x MIDI Out via 5-pin DIN jacks
2 x MIDI Out via MADI
= 4 MIDI Outs
Errors in
wdmaud!CMIDIOutDevice::WriteEvent+0x9c
wdmaud!CMIDIOutDevice::PlaySysEx+0x6d
At startup, Cubase tries to find the MIDI SysEx ID of any connected device. It sends the MIDI SysEx message F0 7E 7F 06 01 F7 (System Exclusive Identity Request) to the device (Note: Cannot be suppressed by Cubase MIDI Filter). If the device supports SysEx ID, it responds with a string of digits that can be used by Cubase to uniquely identify it.
So it seems that in this initial sequence an error occurs in the communication between Cubase and a connected device. It would be of interest if the error also happens when no device is connected via MIDI.
Thanks @ASM yes, after re reading your reply I realised the MADI inputs also had MIDI.
yes it would be good to know what’s causing this. Unfortunately i cannot replicate a scenario to make this happen, I worked all day yesterday and had zero issues but today openning and closing a few projects i had the deaded freeze on the hub.
As i said above Studio One and Reaper have been rock solid on this same machine so it’s definitely somethign Cubase related NOT hardware.
I have new clients in the studio next week so I’m slightly worried about this coming up again mid session…
cleaned out all midi /audio devices from Device manager including hidden. let windows reinstall from scratch.
Removed Midex 8 , it’s just frozen on the HUB again in between opening and closing projects.
I wasn’t familiar with the issue, but now I see It says that it may happen after a disconnect because the old API doesn’t handle disconnects gracefully. That I do know.
If you’re not unplugging USB devices, I would think it’s possibly a virtual device connection, like VEP, that is being released before Cubase tries to send the closing SysEx to it.
For WinRT MIDI, it may be you’re out of MMCSS threads (incoming MIDI data uses them in the WinRT API). Steinberg has an app to apply the registry change to increase the number of threads.
WinRT MIDI and the new Windows MIDI Services (Overview | Windows MIDI Services ) both provide device disconnect notifications, so this will eventually go away when apps move to the new APIs.
Thanks for checking. I’ll try the MMCSS and see if i can get windows RT to work, perhaps that was why i was having issues. It’s been a PIA trying to chase this down, and I wonder why it’s ONLY Cubase/Nuendo that shows this issue??? no other DAW app has any kind of choice in what ‘type’ of MIDI API to use in it’s midi settings and they just seem to work, you’d have thought if this was a general Windows issue I’d have come across this in the past.
Anyway, Thanks again, I’ll get at it again tomorrow and see if i can narrow things down. I think if it was a VE pro port that was causing this then there’d be a lot of others with the same problem as Cubase/VE pro is a popular choice with many film composers.
It’s a shame the crash logs don’t show which device is causing the issue, that would make this so much easier rather than trial and error, but if the MMCSS doesn’t fix the winRT not working for me, then I’ll have to just remove a device at a time and take it from there.
I’ve been chasing this since at least Nov last year… so 8 months!!!
In that time I’ve had a few helpful suggestions but no one has been able to tell my why cubase is freezing with WDAUDIO crashes, just that I should use windows RT.
For 8 months I’ve been trying windows RT and could NOT get it to work. Again no one, and more importantly no one from Steinberg has had any ideas as to why or how to help.
So again in frustration about this I reached out to Pete Brown at Microsoft @Psychlist1972 and my friend Vin (TAFKAT) who is the dev of DAW bench and a system builder in Australia.
Within a few hours I had the answer.
it was infact the MMCSS issue that was causing this. After i downloaded the ‘tool’ and extended the threads to maximum everything ran perfectly and windows RT has been running fine for all my devices.
So, on one hand I’m glad it’s fixed but…
why did NO one from Steinberg know about this and help me in 8 months? Is this becasue they all are Mac users now, and they don’t know about this issue on windows/Cubase? After watching Dom Sigales recently bashing Windows it does seem like Cubase is becoming more Mac centric
Cubase is the only DAW I have that has this MMCSS limitation that’s why I saw no issues with Studio One or Reaper with the same hardware.
Why is the MMCSS thread limit neutered in Cubase if it can cause this?
@Martin.Jirsak I’ve a feeling this has been going on for quite some time, so I’m genuinley surprised it’s taken me contacting Microsoft to get a solution.
So for anyone else who has a problem like this it’s a simple fix, see @Psychlist1972 post above with the download link for the little application that will remove the thread limit.
p.s. In this time I’ve bought an AXR4 to try and solve it, when it didn’t I bought an RME UFX III. I replced the CC121 with a behringer X Touch One. I’ve replaced both my MIDI keyboards in an attemt to fix it…
Please allow me a few words . I can well understand your anger and disappointment on your path of suffering. However, I’d ask you to distinguish between the possibilities of this Forum and the official Steinberg Support. Here in the forum, the vast majority of posts are written by dedicated but ordinary users. In any case, it’s not the place to expect absolutely professional help, but a platform for the exchange of knowledge and opinions of Steinberg users. Despite, it’s amazing how many problems can be solved or at least clarified here, even if not all of them. As someone who is familiar with the challenges of the Steinberg Jungle myself, I’d like to wish you a more relaxed working environment for the future. Cheers!
Did you rise a support ticket? Here we are on the user forum, not official Steinberg support.
Because the driver (which is written by Microsoft) crashes and kills the application with it.
Now, when you wrote it, it rings the bell on my side. I’m sorry, it didn’t came to my mind. Yes, there is some settings like this in Windows, what you can optimize. Again, it’s on Windows side, not on Cubase side.
. I can well understand your anger and disappointment on your path of suffering. However, I’d ask you to distinguish between the possibilities of this Forum and the official Steinberg Support. Here in the forum, the vast majority of posts are written by dedicated but ordinary users. In any case, it’s not the place to expect absolutely professional help, but a platform for the exchange of knowledge and opinions of Steinberg users. Despite, it’s amazing how many problems can be solved or at least clarified here, even if not all of them. As someone who is familiar with the challenges of the Steinberg Jungle myself, I’d like to wish you a more relaxed working environment for the future. Cheers! 