How to scroll remote controls accordingly with track banks

[sickozell]

Hello,
I'm new to writing scripts and this is a thing I couldn't find reading this forum threads.
I have scrollable trackbanks, and every track has one remote control set in the preset page, mapped to the controller directly via bitwig, so values are not set by the script, bacause it has slower response.
When I scroll track banks, can I assign the remote controls to the corresponding tracks in the new bank? If yes, how?

[moss]

Hello,
I'm new to writing scripts and this is a thing I couldn't find reading this forum threads.
I have scrollable trackbanks, and every track has one remote control set in the preset page, mapped to the controller directly via bitwig, so values are not set by the script, bacause it has slower response.
When I scroll track banks, can I assign the remote controls to the corresponding tracks in the new bank? If yes, how?

I do not fully understand what your are doing, e.g. what does "mapped to the controller directly via bitwig" mean? If you use direct mapping via MIDI learn it is not using remote control parameters.

[sickozell]

I'm sorry, I'll put it in another way:
is it possible with scripting to stop bitwig from reading values of mapped controls assigned via midilearn ?
I'm asking because I'm trying to write a script to manage several songs in a project, so every song is one trackbank, and I would perform with cliplauncher view.
Let's say that every track in the bank has one knob assigned in the preset page of remote controls. So when I scroll trackbank (song) I'd like that bank1/track1/control1 is assigned to bank2/track1/control1. The problem is that these controls have to stay independent in readings.
I explain: I first tried to midilearn controls in different banks on the same knob. It works, but when i scroll banks the initial value (the one that is saved in the project, which is the one I would like to start with for that song) is lost.
So I wanted to know if there's a scripting way to fix it, or maybe there's another way to do that.
Thanks for your attention.

[moss]

I'm sorry, I'll put it in another way:
is it possible with scripting to stop bitwig from reading values of mapped controls assigned via midilearn ?
I'm asking because I'm trying to write a script to manage several songs in a project, so every song is one trackbank, and I would perform with cliplauncher view.
Let's say that every track in the bank has one knob assigned in the preset page of remote controls. So when I scroll trackbank (song) I'd like that bank1/track1/control1 is assigned to bank2/track1/control1. The problem is that these controls have to stay independent in readings.
I explain: I first tried to midilearn controls in different banks on the same knob. It works, but when i scroll banks the initial value (the one that is saved in the project, which is the one I would like to start with for that song) is lost.
So I wanted to know if there's a scripting way to fix it, or maybe there's another way to do that.
Thanks for your attention.

Still not 100% if I understand what you want to achieve. MIDI learned parameters are NOT controlled by the controller API and therefore cannot be changed from a script.

If I understood you correctly you want identical mappings of device parameters for all of your songs. What you need to do, is to have always the same number of X tracks for a song. Then you can create a track bank (only 1!) with a page size of X. To switch songs select the previous/next page.
To control the parameters, collect the parameters you want to control in the first top level device for each track, get the remote control parameters from this device for each track and map these to your incoming CC messages. These will than switch with the page changes.

[sickozell]

Yes, I'm sorry, the fault was mine calling every song a trackbank instead of "pages of the trackbank".

I'll try to do as you say, but when you write:

get the remote control parameters from this device for each track

I have to do this with scripting, right?