Hi, I use an Arturia Minilab 3, with the script provided by Arturia. It works, BUT the issue is every time I close Cubase (14 Pro) and relaunch it, the MIDI Remote is gone. Have to set it up every time !
Looked into it on several forums and sites, can’t solve it alone
PS the Quick Controls function could be improved, I find it extremely confusing, different things may happen based on which window is activated, different parameters written in the inspector, plugin QC… I understand there is Track QC and VST QC but this is confusing !!
But maybe @Martin.Jirsak can cross-check whether it is in (planned) for the next maintenance release?!
In software development, sometimes a feature or a bug resolution is more challenging than expected, or it does not succeed the testing phase.
When the product manager in such a case is confronted with the decision to prioritze keeping the maintenance release date (with many other resolutions users are waiting for) over delaying the release in order to also add this feature, such a decision can happen. That’s still professional.
@Martin.Jirsak
Yes it would be very helpful if we could get confirmation from moderators or from Martin if he has time, as to the status on this bug. There are a fair number of users who are having trouble getting controllers to even appear when doing a fresh launch of cubase or nuendo - and this seems to,persist with ver 14.20. It is clear that all was largely ok on version 12s when the midi remote api was a new and much vaunted feature.
I tested on version 12 and 13 (admittedly Nuendo) the other day and it was clear that ver 12s are fine but ver 13s fail to show a scripted surface controller device with extenders on a fresh launch of the application (post ver 13.0.40).
Additionally the Steinberg midi remote api on Git Hub seems to be stuck at version 1.1 - although some users have said new features are added in version 14 Cubase/Nuendo but the documentation is lagging behind.
Where are detailed version history notes for recent point releases of cubase and nuendo? i.e issue by issue accounting for bug status/resolution? Are they always there within the Download assistant? I remember them being like this on cubase 10. e.g. …
I can’t check at present in download assistant as I am on iPad - but to best of my knowledge I haven’t seen version history notes for recent versions of cubase or nuendo - but do see detailed ones for products like Dorico and Halion. What we get on version 14 Cubase are release notes which are less detailed - or at least don’t have the issue by issue logging that the version 10 history does. Fair enough they are different kinds of documents but personally I would rather see a detailed version history with issue numbers listed etc as well as more general release notes. It would be easier to check a version history document to see if this midi remote bug has been solved or not.
Many thanks.
Update: Have added my post as a support request as well Plenty of users say they do not respond sometimes to support requests - and that has been my experience also recently.
Isn’t it likely that SB are waiting for windows midi 2 to land? I believe port id nomenclature changes, so Cubase code will change too? Probably problem solved then. And yes I have remote activation issues still. But it’s very random.
@Matthias_Quellmann @Ed_Doll
Well here is the late reply to my Steinberg support request
…
Excuse the very late reply!
You find the detailed Cubase Pro 14.0.20 realised version history notes for recent point releases at this link CubaseD 14 Release Notes
…
This is no use at all. As. I stated earlier in this topic release notes are just advertising promos really and are not the same as the old style issue by issue version histories which seemed to tie up better to developer buglists/database entries.
It is not clear at all from the 14.0.20 release notes whether a fix to the midi remote save state bug has been attempted or not. It is clear that there are a lot of us are experiencing the problem and it occurs even when setting up the Steinberg Example Company demo devices. So it has not been fixed
It is unacceptable to have to pay for the version updates and have the product owners claim a bug is fixed when it so clearly has not been.
Who is officially moderating on this forum. (My apologies if this is @Martin.Jirsak as I know you are trying hard to get this bug sorted out)
Who is in overall leadership role on the #14 sequencer branch?
Best wishes
Thanks Martin. Interesting that you can’t reproduce the problem. Are you using both Mac and Windows computers. I’m on a Windows 11 Pro with 13th gen Intel so a fairly standard set up.
What I just don’t understand is that the feature was fine until version 13.0.50 and then suddenly not so. And alsso that it will not work even with the Steinberg demo scripts for midi remote
Yes, I’m using a Mac with an M1 processor and an Intel processor. I’m using Windows 11 on an Intel processor and an ARM processor. Not on a daily basis all these systems, but I tried to restart Cubase at all of them multiple times with no issue.
Not really, there were some users with the issue prior to 13.0.50. But it seems that there are more users affected since the 13.0.50 update.
I think I found the reason for my problems.
it is the deviceDriver.makeDetectionUnit methods.
It will use the hard coded js values on start, not the values used when
loaded and if the hard coded values does not exist it will not load at all. And the example names sucks, since the trailing IN/OUT should not be part off the default names.
What @alexis said.
If you want to know more:
Above your selection of forum categories you will find the tab More. Click on it and open the About tab. Now, you’ll find a list of all Admins and Moderators.
