Has there anything being updated/fixed in the .30 release concerning MIDI Remote?
The release notes don’t mention a single word about it!
3 Likes
I tested this morning with it and it appears to be no diffrerent i.e still not saving state. (version 12 still works fine). Steinberg have acknowledged it is a bug and said it would be fixed for 14.0.30. Grrr
Better luck next time … 
1 Like
You have no idea what plans they may or may not have. This is a point release. Your problem here is your expectations.
@RichardTownsend MIDI Remote was released over 3 years ago along with promises of future updates and improvements. But here we are. Still waiting.
Sure, I appreciate the need, but this is not likely to be fixed in a point release.
The issue is a degrade. It used to work, they fucked-up without any note in release notes, and they have not been able to revert the bug.
1 Like
@Martin.Jirsak @Matthias_Quellmann @Markus_Staudt
Hmm it’s a bug that Steinberg have previously acknowledged to be a regression bug and have indicated they were originally fixing for the 14.0.20 release. I guess it’s possible that for some devices that might have worked for that update and it may differ according to platform. But there are still a number trying workarounds by trying to tweak code in scripts etc to get a result.
The maintenance updates seem more infrequent these days. What happened to hot fixes? They happen fast enough if it’s a showstopper bug affecting thousands of users.
Plus the new midi remote was wheeled out at ver 12 as being a new dawn and the best thing since sliced bread. Which it could still be but there has been little development of it since ver 1.1. The API has some features still unimplemented and the documentation and media support could do with expansion. So if they do have plans it might be good if they gave a hint of them given that midi remote has been pretty much undeveloped since 1.1 - and if it has been they should change the version number on Github.
2 Likes
very disappointing and frustrating to add the script every time I open Cubase
2 Likes
If you tried to fix the bug due to some problem and couldn’t, I don’t blame you (humans are not perfect).
It would be a little less stressful for the user if you could at least disclose that information.
I’m sorry, we’re working on fixing the problem, but we can’t figure out what caused it and will bring it up next time.
Like this.
Hi Richard you are wrong on this point, it was indicated this issue would be solved in the .20 release. Martin mentioned it in a post I made about the issue many months ago.
Luckily my REMOTE problem got solved and it is stable on .30 but I empathise with others and wish for a remote + QC + automation overhaul.
I hope we can all enjoy using Cubase !
1 Like
I thought it was clear that the scripts need to be changed in the way that they need to address midi ports correctly. No? Is it something else?
No, it is not clear. It is not documented in the API reference, release notes or anything from Steinberg. It is a workaround practise found out by forum people, and it only work in special cases by circumvent the faulty cubendo GUI.
4 Likes
I suppose no one fixed these bugs
why was it necessary to break something that worked? Since the release of the 12th cube, they have only added useless touch support, which was already implemented quite well and the idle state, but they broke such an important thing as insert parameters
1 Like
Agreed and I’m sorry for all still experiencing issues (please everyone remember not to denigrate other’s issues even if you don’t experience them, thanks)
And here is a link to a potential solution by Christos in the post I made, worth a try :
Good luck !
Your problem is to face the truth about the midi-remote itself. IMHO the midi-remote comes very close to a fraud case on the customer:
How do you prove a fraud case?
What three elements are required to prove fraud?
- False representation of fact. The first element involves a false representation of a material fact, and this means that one party knowingly made a false statement about something significant. …
- Knowledge and intent. The second element is intent. …
- Harm or damages.
All three points are true for midi-remote. Your expectation on this might vary, but for me it is very clear, that the midi-remote should have never been released and advertised this way. Everyone here should also be aware, that the midi-remote editor and midi-remote API stuff are two totally different things with the biggest issue being not compatible. So absolutely nothing is working what you did on one side, if you try it on the other side and vice versa. While the midi-remote API did receive at least some fixes, nothing was done for the midi-remote editor, which is the part that every user could use and does not require to be a Javascript expert.
And what is this “This is a point release. Your problem here is your expectations.” ???
Promises where made and nothing happened in three years. It did get worse, that is the one and only thing.
Kind of curious to see when/if we will get a response on this from a moderator. Apart from @Martin.Jirsak indicating that the bug had been registered again with developers - noone from the Steinberg team appears to have contributed on the midi remote issues whether in this thread or on the numerous other threads raised on midi remote around this and the Nuendo forum. (If this was the Dorico forum the moderator team response would be within hours not years).
Apologies, I wasn’t aware of that.
1 Like
Will we live to see that amazing time when at least some of this will be implemented?