Between WinRT and Checking licenses as tracked using Task Manager, I am experiencing SLOW (5 minutes plus) load times for Cubase 13. I have seen posts from other users trying to hack their own machines to find out how to get around this very big annoyance, but no definitive information on how to fix. Please, Steinberg Engineers - please give us a clue as to how to shorten the load time – I am just about to start regretting upgrading to v13. Thanks. JMS
Win 10 Pro 22H2, 64 GB RAM I9-10900K@3.70 GHz
Hi,
How is the WinRT, mentioned in the title, involved, please?
And then “Steinberg Hub” goes “not responding” as seen in Task Manager. Very, very slow to resolve. Steinberg Engineers, please advise. Thanks
Hi,
Does it help, if you remove the WinRT driver option in the Studio > Studio Setup > MIDI Ports Setup, please?
I had exactly the same issue, nothing helped, disabling/enabling the WinRT MIDI did not change anything (also I opened a ticket, no solution so far). Even when the WinRT MIDI message disappears, Cubase still hangs, the hub does start as usual as jms4th described
Maybe interesting to know: I switched to Nuendo, though both DAWs are basically identical in terms of the platform, Nuendo starts within seconds (identical PC)
1 Like
Hi,
This is interesting. There must be something different in the systems, which makes the change.
Could you install Cubase or Nuendo to the other system, just to be able to test, if the difference is in Cubase/Nuendo or in the system, please?
What me really makes wonder, the issue did not happen with earlier Cubase 13 versions, AFAIR from one day to another it happened, maybe after an update or so.
On my notebook Cubase 13 started flawlessly. Unfortunately I cannot longer start Cubase as the license was deactivated for reselling (already approved by Steinberg as far as I can see).
Hi Martin,
Good question – I looked at the MIDI ports setup and the WinRT box is NOT checked.
Did this get solved? I’ve got really long load times - it hangs on winRT MIDI for ages - like 15mins.
I’ve got quite a few virtual midi ports I wonder if that’s anything to do with it?
For information. I’m on Nuendo 13 and it stays long time (2-3 mn) on WinRT checking licenses. WinRt is not selected on Midi ports setup. Any other ideas ?
I have an open ticket on this one - still working through the potential fixes but I’m still stuck with very long start time for cubase
have you tried running the MMCSS fix?
It solved issues for me with windows midi . I had no error messages but tried this on suggestion of a system builder. It worked for me.
just run the file and set it to maximum threads. It won’t do ant harm either way.
M
Thanks - I already looked at that but I have already disabled winRT so windows shouldn’t be creating any MMCSS threads and I can’t reduce my midi devices
Also I have midi devices that can’t use winRT, I’m worried that if I run the file or enable winRT I will lose all my configuration. It’s taken years to get to this point on my rig and goodness knows what tweaking and patching all stuff in my template over that time. If I broke it I would never remember everything I did!!!
“Also I have midi devices that can’t use winRT”
Out of curiosity, because this could impact the new API as well, what devices do you have which work with the old winmm MIDI API (the cubase default) but not with the WinRT MIDI API?
Do they just not appear, or is something else happening?
Pete
Still wrestling with this problem and still have an open ticket on this.
I’ve disabled pretty much all my MIDI equipment to the point when I only have a single device and yet still have very very long startup times (15mins+ !) but it gets there in the end!
Ive tried running the whole thing with no midi devices. I’ve had winRT activated, and deactivated. Removed all my virtual midi ports and cut out or reinstalled a lot of my plugins.
Getting to the point now where I’m looking at a full system rebuild as I can’t keep waiting ages for my primary software to star.
Anyone managed so sort this out???
I was mistaken on a not being able to use winRT to be honest, I was worried as my touch panel software didn’t support it directly, but it’s ok on that one as it just needed the midi input signal so that still functions.
Done that, no difference really other than I don’t now get the occasional priority message error.