Please Steinberg: Mix configuration and / or Channel visibility for Midi remote scripts!!! When??
3 Likes
At this stage my guess would be in Cubase 14.
I hope so!
1 Like
Now that Cubase 14 is out, can anyone say whether this is implemented yet?
1 Like
Yup I was asking for this feature to be implemented on the Icon V1-M/X thread topic on this forum. MIDI remote api is at ver 1.1 I believe. Much flagged up by Steinberg when it appeared in Cubase 12. So can we have ver 1.5 or .2.0 please with the SetFollowVisibility() stub fully implemented?
Thanks
I was also checking in to see if anyone knows if this is working now… I’m not upgrading anything until that functionality is available.
Ugh. Come on Steinberg. Get this done.
1 Like
@Matthias_Quellmann
@Ed_Doll
I’m copying in a couple of Steinberg Cubase staff to try and raise their awareness on the general development of the Midi Remote API and its accompanying documentation.
Some users are saying that the Midi Remote API has indeed been expanded and developed for Cubase/Nuendo 14.0.20.
BUT THERE IS NO NEW DOCUMENTATION FOR THIS. E.G on GitHub.
Have stub features now been implemented in the API code e,g. SetFollowVisibility? Several posters in this topic requesting the proper implementation of this feature - including at least one excellent third party script developer @bjoluc
For some users the full use of the DAW with the latest mixer control surfaces is inhibited if the mixer control surface cannot follow any changes in visibility of mixer tracks in the DAW on the computer monitor.
And what is happening with the updating of the Midi Remote API documentation on GitHub?
Thankyou
3 Likes
I think “setFollowVisibility()” hasn’t been addressed in 14.0.40 either, has it? CC @bjoluc @Jochen_Trappe
@bjoluc @Jochen_Trappe @isdjan
With the icon V1-M/X surfaces that I use the saving and retention of the configuration of the surface has been solved in 14.0.40 update.
setFollowVisibility() I doubt has been implemented yet in the MIDiRemote API in the way I would hope it to.
I did a bit of testing anyway to see how the Icon surface responds to visibility of channels in cubase/nuendo
If I hide a channel in Cubase mixer and then select any channel on the surface then the surface does update it’s channel visibility state - so that is good. But I’m not sure if this is the full interpretation of what setfollowvisibility should be.
I would expect a more bi-directional control of visibility i.e on the surface a button that hides a channel in cubase and immediately updates the state of the surface to reflect this. Similarly in cubase/nuendo when a channel is hidden or shown the state of the control surface immediately follows this - rather than having to wait until the user triggers another action on the desk.
But at present if I can set up various group or vca sub-mixes and the surface does at least reflect the visibility set up of individual channels then that is good - and does seem to work in practice. There also possibilities of using hotlinks on buttons in the icon surface to configure different mixconsole views in cubase - but I haven’t explored this much as yet.
I’m reliant anyway on bjoluc’s excellent script and on github he states that he could not implement setFollowVisibility() as it was just an unimplemented stub in the midiremote api.
As ever hoping for further midiremote API developments in Cubase/Nuendo 15 
Thanks for the reminder that there are workarounds and yeah, they improve the situation clearly. But after my understanding, the FULL implementation would help to leverage from all visibility features regardless of e.g. the synchronisation settings in the left visibility zone (like synchronize mixer 2/3/4 or even NOT - and synchronizing visibility of track types, as in that “=” menu next to the visibility tab. Also, I fell that the visibility agents could be way more useful with a full visibility synchronisation. and global enabling/disabling visibility of track types would be even more benificial if instantly reflected by the hardware.
I thought of it like an instant and full representation of the cubase focus. If you are in main window, you see all tracks enabled there. If you activate and focus Mixing Console 3, eg with the visibility set only to group and effect tracks, the hardware would instantly set the visibility accordingly.
Does this make sense?
My
Certainly does make sense. Instant response and updating of differently set up mix consoles is definitely the ideal. I experimented further with that goal in mind today with limited success. Currently only getting main mixer console to update - secondary consoles with different channel configurations don’t seem at present to get reflected in the control surface config. Will try further tomorrow. Best.
1 Like