Midi Remote API: SetFollowVisibility

[doctorlaz]

There have been a lot of posts mentioning the SetFollowVisibility() function, buried among various threads. This is a feature that many users are requesting, so I thought I’d start a dedicated thread to it.

As I understand, it’s available in the Midi Remote API, but not yet implemented. It would allow the visible channels on the Cubase mixer to be reflected in our control surfaces (mine is the Behringer X-Touch), which currently show all channels, visible or not.

So I want to put my name down as one who’d love to see this feature implemented, and also ask if anyone on the Midi Remote team could give us any idea when we might expect to see this happen. Even if the answer is ‘not for the foreseeable future’, it would still help me plan accordingly.

I want to make it quite expicit that I’m not moaning at the team about this. I’m delighted so far with Midi Remote, and together with @bjoluc’s script, it’s really improved my workflow. I know these things take time.

All the best, Paul

[jpspoons1]

Liked and voted.

[Danix78]

Yes,
SetFollowVisibility is required here too.

Highly Rated!

[Crincy]

Same Here

[matthieu_guihot]

My workflow really need this update too.

[Danix78]

Here is another topic with the same request. Let’s not despair votes!

MIDI Remote Needs to Support Mixer Visibility Configs!

Softube announced today that their new Fader Mk3 unit will ship with a Midi Remote script to allow for plugin-less usage of the unit, but due to API limitations I wonder if it will support visibility configurations. Anyone know about this? I’ve even heard ICON is looking into supporting midi remote with its series of control surfaces too, and we’re also seeing devices by Nektar and Novation ship with them too, but without mixer visibility config support it really limits the usefullness of these…

[jpspoons1]

I went to read the other one and discovered I’d already voted for it… short memory.

Is there any way to combine the topics? (I think you can fork, not sure about the opposite)

[doctorlaz]

I wasn’t aware of the other thread when I started this one, despite several searches. Unfortunately the other one never mentions the SetFollowVisibility() function. I accept the end goal of both threads is the same. In any case, I would really appreciate any sort of update from the Midi Remote team.

[isdjan]

Here’s another post where I firstly read about the SetFollowVisibility() function:

MidiRemote Quirks

I’ve been deep diving into the midi-remote api the last few weeks, and I’ve found couple of quirks/issues - they MAY be bugs, perhaps stuff that’s not implemented yet, or just me misunderstanding how things are supposed to work… OnColorChange for Input channels: It appears that input channels always have a colour of 0,0,0 and are marked as inActive. I appreciate that input channels don’t have tracks so don’t have a colour, but if they sent the default colour instead then they’d “just work”. Ot…

I’d really love (or badly need) to have this function available soon. Many thanks!

[blissdrums]

I also have been waiting patiently for this functionality. I was hopeful that Cubase 14 would solve this problem, but apparently not… Add me to the list of people that need this for their workflow. We need this, PLEASE

[m.c]

I think in the latest CB14.0.10 setFollowVisibility works, the mixConsole actually defaults it to true

There is one thing though, that the API is not updated directly when a change is performed, we need to do first something, for example, select a track, in order to get the updated track titles/volume/etc with our sysex.
For now (I think an auto-refresh may follow), I have added a “refresh” button in one of my test scripts, it literally does nothing since it just “selects” the already selected track, but then the API gets updated. With scripting we can actually make auto-refresh periodically by making use of the mOnIdle event or custom variables timers.

var refreshButton=surface.makeCustomValueVariable("refreshButton")

page.makeValueBinding(refreshButton,page.mHostAccess.mTrackSelection.mMixerChannel.mValue.mSelected)

[doctorlaz]

@m.c

I think in the latest CB14.0.10 setFollowVisibility works

So API directly updating aside, have you managed to get setFollowVisibility to work in your scripts? If so, that’s epic news.

[m.c]

@doctorlaz

have you managed to get setFollowVisibility to work in your scripts?

Exactly. And I know that most scripts in this forum already have the setFollowVisibility to true, so they won’t need to update. With the limitation I mentioned obviously, at least for now.

[doctorlaz]

Wow. Time to brush up on my javascript to see if I can get bjoluc’s script to support this. I know it already has setFollowVisibility to true, so hopefully it’s just a case of inserting your refreshbutton snippet…

[m.c]

@doctorlaz

so hopefully it’s just a case of inserting your refreshbutton snippet

Yeah, give it a try and let us know

By the way, since I know that this script syncs upon a change, perhaps you can begin by simply selecting a track after you change the visibility configuration and check if the displays are updated.

[doctorlaz]

OMG it’s alive! Works perfectly on my X-touch + extender! Just select a track afterwards and all those invisible tracks just go away. Thank you @m.c and thank you Steinberg!

[Danix78]

This is great news!

I’m calling @bjoluc, who probably already knows.

[skijumptoes]

@Danix78

I’m calling @bjoluc, who probably already knows.

As @m.c mentioned above, most people would’ve had it enabled and ready in their scripts already, difference is it actually does something now!

[m.c]

@skijumptoes

most people would’ve had it enabled and ready in their scripts already

Sure, but note also that

@m.c

the mixConsole actually defaults it to true

This means that if someone hasn’t set it to false explicitly, it should work too

[Joshua_Reiners]

var MixerBank = page.mHostAccess.mMixConsole.makeMixerBankZone()
MixerBank.setFollowVisibility(true)

just this is supposed to make it work on C14.0.10 right? Cause it doesn’t work for me, am I missing something?