We’ve released Cubase 14.0.32, which addresses an issue with the MIDI Remote scripts included in version 14.0.31.
Unfortunately, the scripts in the previous update were faulty, and we had to re-release them with this new version. This is the only fix included in 14.0.32.
We apologize for the inconvenience and appreciate your understanding.
Wow, back-to-back hot fixes!
Am I dreaming?
Is this the dawn of a new era of responsive service?
Fingers crossed…
A post was split to a new topic: Problem with the Transport mode
Even though the bugs are still there
, we appreciate that you are changing your attitude to address them as soon as possible.
My Novation Impulse 61 Midi Remote Script is broken with this update.
A post was split to a new topic: Double-click is not reliable
Still skipped Novation’s flagship midi board, the SLmk3.
Checked this already? Novation SL MkIII (MK3) MIDI Remote Script
Crashes on initializing ARA, can´t even open Cubase now, no crashdumps, any suggestions?
C14.0.32 Pro
I haven’t as yet checked to see if it fixes the regression bug highlited by the post I quote below and other posts on the subject of failure to save state of mideremote set up for some devices. I’ll be delighted and thankful if it does but from what others are saying on this thread it sounds unlikely. On the subject of the midiremote editor what is the point of papering over a few cracks with the system without addressing other longsstanding bugs OR looking at the API, expanding it, enhancing documentation - and giving it a new version number (2.0) to underline that constructive holistic development work has taken place rather than just patching it. Best wishes all.
So you don’t want Steinberg to fix bugs or what?
Fair point I agree and I don’t like to sound grumpy about it, but this midiremote bug is a regression bug that has been around since ver 13.050. In version 12 all was fine. It has been acknowledged as a bug by Steinberg for quite some time and was promised as a fix in both 14.020 and then 14.030. So it is long overdue - and yes I do accept that bugs are not always so easy to fix without having knock on effects on other features. I was a software designer for around 5 years back in the heady 90s so I understand that. And the bug affects a number of users - it is not just myself.
It’s good as others have said that the concept of a hotfix has returned so I hope that will continue. And I hope the midiremote API will get moved on further too. It was touted as a great new feature at version 12 and I believe it would really be even better with further development.
And I’m glad for those users whose issues have been resolved by the latest 2 hot fixes. Best wishes.
The latest update is STILL corrupt. I just updated yesterday (6.24.25). I had huge issues. I spent hours trying to figure out what was wrong with my MIDI. I had no idea that there was an issue with any updates until I downloaded the update. I finally googled to see if there was an issue, sure enough, there was… and still is! I double checked my keyboard on my other workstation that did not have the 14.0.31 or 14.0.32 update… everything worked great. I had to restore my pc back to yesterday, before the .32 update… everything works great now. In summary, the 14.0.32 update is still corrupt.
Still broken. had to restore my computer back before the update. Now even my new Native S88 works. The tape stopped working, bend wheel was the “play” button, a big mess. I have been dealing with this for hours… The 14.0.32 update still needs fixed.
FYI: I have replied a couple of times. But wanted you to know that even in Cubase 14.0.10, my pitchwheel starts the play command. But I go back to Cubase 12, it doesn’t do that. But my keyboard works great in Dorico 5 also,
Cubase 14.0.32 (Intel) on MacOS Sequoia 15.5 crashes upon opening every time without fail , i tried opening other daws and they work just fine without having to update them.
It scans everything smoothly , until the last second before loading it shows the microphone icon in yellow up top on mac and then closes - i updated everything else media bay included.
Is anyone else having this specific problem? Can it be fixed soon? Attaching crash file under this.
Thank you for your time
Cubase 14-2025-07-05-031157.ips (137.1 KB)
There are some things that slows down the workflow.
cutting a section and pressing x, doesnt make a crossfade on each end of the section.
would be nice to fix that bcs in cubase its possible without selecting that section again.
the second thing i found is that you cant close the help-screen(main screen) of cubase after eyporting and closing everything. you have to press the close button on the buttom right corner