Independent track selection by two different control surfaces

[guild12]

Moved, by suggestion, from main Bitwig forum:

Hi there.
I have two control surfaces.  The Nektar Panorama P61 and the Push 2.  I am using the Driven by Moss script for the push and Nektar's script for the P61.

Is there away to, without pinning, have the controllers not follow each other when selecting tracks?  I'd like to, if possible, be able to select Track 1 on the Push and then select Track 2 on the P61 without the Push moving to track 2...but without having to pin the push to track 1.  I understand the function of pinning but in this case I'd just like the controllers to not follow each other without needing to lock one controller to one track.

Alternatively if I could make it so one of the controllers automatically pins itself to whatever track it selects...that would work too.

I hope this makes sense.

Follow up...if neither of these can be done...is there a hotkey to pin a controller to a track?
​​​​

[hydrogxn]

Not sure exactly but maybe in your track selection script, you could unpin it select move it and then re-pin. So its essentially always pinned but you can move it.

[guild12]

Cool. I was originally just thinking it would be a setting I was missing. I'm not affraid to jump in to a script...just new to it in bitwig. I'll start digging around.

[moss]

TrackBanks do not follow per se the track selection in Bitwig. I implemented it like this in DrivenByMoss because this is normally what you want.
So, this is easily possible to implement. Now, that with 3.1.3 finally the correct settings are available in the init() function this could also be added as an option.

[zengel]

Hello !
I have a question regarding this subject for moss and all good willing people on this coder channel.
It's been a long time that i would love to group arbitrary tracks in banks .
Like track 2, 6 and 12 in one bank . and 4,22, 1 in the 2nd bank and 2,22,6,1 in a third .etc ...
In the same way as push 2 user mode work by pages, could it be possible to put multiples tracks in separate banks and tracks could be part multiple time in different banks. Banks would be selectable as pages in user mode on push.
Then when i select bank 1(on the push for example the same button as "pages" in user group) i would have mix , rec, mute ,pan, clips...etc of track 2, 6 and 12 on the 3 firsts "channel" on my controller . and when i select groupe 2 the 4, 22 , 1 tracks could be controlled etc ...
Can the api let program such a thing ?
Thanks for reading !

[moss]

Hello !
I have a question regarding this subject for moss and all good willing people on this coder channel.
It's been a long time that i would love to group arbitrary tracks in banks .
Like track 2, 6 and 12 in one bank . and 4,22, 1 in the 2nd bank and 2,22,6,1 in a third .etc ...
In the same way as push 2 user mode work by pages, could it be possible to put multiples tracks in separate banks and tracks could be part multiple time in different banks. Banks would be selectable as pages in user mode on push.
Then when i select bank 1(on the push for example the same button as "pages" in user group) i would have mix , rec, mute ,pan, clips...etc of track 2, 6 and 12 on the 3 firsts "channel" on my controller . and when i select groupe 2 the 4, 22 , 1 tracks could be controlled etc ...
Can the api let program such a thing ?
Thanks for reading !

Interesting question. I guess it would be possible if you create a large bank and pick the tracks you want. Question is how something like this would be configurable. Also, why not simply group the tracks you want?

[zengel]

Question is how something like this would be configurable.

I don't know how the api work . Perhaps API monitor track selection by ID ? name ? do not know.
Then , Hypothesis on Push : Could it be possible to have in user mode a per-usermacro-page (as it is now) and a per-trackgroup-view . Then when in trackgroup view select first button under the monitor screen on the push then select the track on bitwig to "send the ID" of the track....Totally hypothetical...

Also, why not simply group the tracks you want?

One track can only be part of one group in Bitwig . But the ability to have a track to be part of multiple arbitrary group in this large bank is usefull to. then the bank should be as large as the number of tracks you have in your set ?

many uses :

-Producing : If you want to monitor arbitrary tracks that are part of different groups ...here you can ...
Why ? because on one song of your set you want to monitor/tweak/record a bass, a synth and a vocal Volume mix without having all the other tracks interfering in the visual .
And after you want to do the same but with a pad of another track ,another synth on another track to but the same vocal track . Then a second group of this bank with both the vocal tracks and 2 other tracks of this bank .
perhaps you want also trigger clips of those tracks without seeing all the clips of all your set to let you focus on these few clips .

-Staging . For a set with multiple song that uses different FX, synth, presets etc ....the ability to select few tracks in a bank for the song 1 and same for song 2 with perhaps some tracks of song 1 in the song 2 bank of tracks etc...same for clips .
There are lots of other situation where such a tool could be useful
Thanks for reading !
PS : And obviously. Thanks for all your exceptional work . you are a legend for me ! as stray can be for Ableton . no kidding ! incredible work !

[guild12]

TrackBanks do not follow per se the track selection in Bitwig. I implemented it like this in DrivenByMoss because this is normally what you want.
So, this is easily possible to implement. Now, that with 3.1.3 finally the correct settings are available in the init() function this could also be added as an option.

Cool. Thanks for the response . Keep it in mind for a future release. My reason for it is to browse to something with the push and be able to noodle around with one hand...and select something else on the P6 and noodle around with the other. Pinning works...but it makes me need to click on the io button and pin something to a track. Not a huge step...but takes me out of my workflow to have to grab the mouse. Just a thought. Thanks again for getting back.