Is there a method we can use to do this?
Is there a method we can use to do this?
I haven’t found anything related, using the MIDI Remote graphical UI. So, I guess that, if it’s possible, scripting is involved and at this point, I can’t help you : I gave up trying to script, confused by the .js vs .json vs .midiremote files created at a point or another when using the MIDI Remote feature.
So, I’m staying strictly with the graphical UI : rather limiting, I know, but life is short…
I don’t think that such an option exists, but I’m not the most experienced user around obviously
What you’re asking CAN be done partially and externally, by sniffing the active window’s title and then send the corresponding “select” midi message for the channel having this name. If, now, it’s out of your bankZone, you’re doomed unless you have a large bankzone already containing all of your tracks (not suggested). Another problem with this approach is if two or more tracks share the same name.
Out of curiosity, what do you want to achieve by that?
EDIT: I have an idea, I’ll get back to you in the evening.
I know, but spring is coming, so I feel somewhat immortal in this intoxicating endless cycle of life and death. After all, why? Why shouldn’t I dabble in scripting? [Insert Bilbo meme here]
Of course, we have Focus Quick Controls for this job I’m describing. But Quick Controls are just 8. So, let me explain a bit further in the vein of:
What I would like to achieve.
Have a page “Plug-in Control.” In this page, 16 encoders would control 16 parameters, and the 16 pushes would control another 16 parameters (switches), and my 9 faders another 9 parameters, for the plug-in currently in focus.
For this to happen, I need two things in advance.
Both are fairly easy to achieve manually, but I think it would be very convenient if they could be automated. I mean, the plug-in window has both clues in the header: Track name - Insert slot. (as MChantzi says)
Now, I know this not an exclusive responsibility of the MIDI Remote, but why not explore if some “core” Cubase function could ease the work expected of the MIDI remote.
For example, I love the preference: “Project & MixConsole - Select Channel/Track on Edit Settings” I have this ticked permanently. Instead of select track buttons, I have Edit Channel Settings buttons, because when I’m “selecting” a channel, I usually want to do something TO IT. So I need to see the Channel Settings window. And this little preference works like a charm for me!
Similarly, if there was a “Auto-Select Channel/Track, Auto-Follow Insert Viewer Bank on Plug-in Focus”, I would run with this preference “on” all the time, because that’s how I’m used to working. Have something on screen, tweak, dismiss. Go to another thing, do the same.
I need to be able to control a plug-in in both situations:
It’s sort of “what you see (in focus) is what you control”.
I’m still using the Generic Remote for manipulating Audio Insert plugins of the selected track by position (1 through 16), since the Midi Remote can’t do it that way for Inserts.
Not even with some trickery?
Like, for slot 1, reset bank
For slot 2, reset bank, Next bank
For slot 3, reset bank, Next bank, next bank…
And if reset bank doesn’t do what I think it does, wouldn’t
for slot 1, previous bank x16 times
for slot 2, previous bank x16 times, next bank.
It’s mReset (mResetBank resets the bank of the selected slot).
It can easily be done, BUT only with scripting, so @Nico5 is most probably right to stay with the GR as long as it has the 1-16 assignments already and doesn’t require a script to do it.
That gets you the bank, but then you’d still need to turn a dial - so always 2 actions, rather than just a single action with the Generic Remote. With on/off buttons you might be able to bring it down to one action via writing an insane number of macros.
yes, with scripting, one can work around a lot of the current limitations of the Midi Remote - but it seems silly to have to resort to that for what should be pretty straightforward stuff.
Ok, back to the topic.
Here’s an algorithm (algorithm in this case means the laziness to write down a snippet, however it might be educational as well):
Setup your mixerBankZone, and read the titles (track names) of your channels upon their change event
Engage the page.mHostAccess.mFocusedQuickControls
Inside the event quickControl.mOnTitleChange (where quickControl in this case is the byIndex Focused Quick Control)
Now that I see it, perhaps I should write a snippet instead, not sure this was lazy enough
Oh and don’t forget the problem that if you have two or more tracks with identical names, this won’t work as expected. A solution would be exposing not just the track name but also its unique ID but I guess that’s too much to ask from an API at least while there are other features with higher priority to add.