Steinberg - MIDI Remote Editor roadmap? Critical issues and bugs

Maybe they’re implementing MIDI 2.0, so maybe next next November? :wink:

It’s here , check your Download manager , all though i’m waiting for the PDF for the version history

1 Like

Nothing great here :frowning: .

Meeeeehhhhhh , im staying on .52 , still nothing to say the issues that were caused by .60 have been fixed , it’s too dicey , ive noticed over the last months since the .60 the amount of Graphics issues people were having was quite scary so unless Steinberg admit to addressing an issue it’s not worth the risk and .70 really doesn’t look like it addresses anything

The release notes are there now :tada:

MIDI Remote

Mappings for Device Surfaces which have “Label Fields” assigned for the “Piano Keys” item are now persistent.

I didn’t know this was a thing. Congratulations, I guess :melting_face:
I’ll try .70 when I get a chance and check if anything MR is broken or was fixed silently.

Ok so these issues are still just being ignored? It would be good with some kind of answer here.

I don’t think they’re being ignored, there’s just more pressing issues that they are concentrating, such as:


ahem :joy:

2 Likes

So now we are hoping for Cubase 13 to address this I guess?
Maybe I should’ve invested some time instead to just build a usb adapter of sorts that handles all these problems…well summer holidays coming up…

Free bump for user Shor, who has been carrying this thread up the mountain for a while now.

1 Like

@Shor is just an alias identity for well known Cubase user Sisyphus

2 Likes

Well here’s hoping for Cubase 13 announcement soon.

Can someone confirm if this was fixed in Cubase 13?
I’d prefer not buying it to try out of the bugs are fixed, and then try to get a refund :slight_smile:

This seems to behave just as before. You can still find these midi values that will just bounce back due to incorrectly rounding values. (Midi value going from 79 to 80 while controlling volume on a track being a particular one that still shows this problem).
This is disappointing. Moreover slightly frustrating looking to get a refund, which I’m sure will go well.

Is there a proper change log for Cubase 13? I’m trying to find out if anything was done to MIDI Remote.

1 Like

Get a trial key when those are ready?

I already bought the upgrade and verified that it is still broken. So zero attention was put to this, which I do still consider a critical bug.

One good thing about Steinbergs attention is that they were incredibly quick to start the refund-process for me, so I got my Cubase 12 Pro license back now.

Does 13 still have the legacy remote stuff?

I believe someone said it did, but I can’t confirm myself as I am back to my Cubase 12 license.
Unfortunately it’s not as featured with some key features (for me) such as the value at mouse cursor, as well as the really nice interface for setting up controllers.
The midi remote editor was supposed to be a big feature in Cubase 12, but it’s a buggy mess from day one, and through an entire major release bugs like the ones specified with reproduction steps in the linked threads above…
Quite frankly I find it a bit embarrassing for it to still not be fixed by now, especially as it has very clear reproduction steps and the issue is quite pinpointed.

I hear ya. I’m interested in Sketch, and some of the new MIDI editing features 13 promises. If legacy remotes are broken that might or might not be a deal breaker in me actually using v13…but I’m thinking the new sounds/libraries alone might be worth the upgrade price. Maybe…

That’s why they provide demo keys. I’ll get around to checking it out :slight_smile:

I laughed at the beginning of the thread when you mentioned about this being a priority , It’s a shame , it was Steinberg new selling point for Cubase , i believe they will get there BUT i think Steinberg’s realised the old code has come to an end and are stuck between leaving things as they are because they can’t go on with the old code or break things along the way to rework and reintroduce Hopefully later . Steinberg has always been this way with removing or breaking stuff But not without reason .
I believe you will see this fixed . There’s been a lot of work going on under the hood , C13’s a lot snappier , loads of graphical stuff that needs sorting But at least they are admitting that this time unlike C12 . Things are moving forward , sit tight and im sure it will be sorted