🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

Moving Track Selection with Session Box Navigation

Submitted by rpacker on Thu, 06/15/2023 - 22:09
rpacker
Control Surface Studio User

I have a Faderfox MX-12 (12 tracks) and have a script that successfully does the following:

-- banks the session box to advance 12 tracks
-- fader volume banks as expected
-- device selector controlling macros banks as expected

What isn't banking is the track selector using highlight navigation. It works fine for the first 12 tracks but then when I bank to the next 12 tracks, the highlighted track selection doesn't move with the session box.

Am I missing something to get the track highlight to bank?

Thanks!

Topic Category: 

11 Responses

Comments

Wim
Control Surface Studio User
#1

Hi rpacker,
I don't have any code to work with here. I assume you already have a reaction somewhere to find the highlighted track.
Add a listener there that searches where you are when you change the session box.
Hope that sets you in the right direction.

upload files: 
rpacker
Control Surface Studio User
#2

Thanks for the response. I am not using reactions, just the highlight. It seems like such a simple thing to bank the highlight selection. Is there really no way to do this except with reactions? I may combine Control Surface with my own Ableton LOM script to try and simplify.

rpacker
Control Surface Studio User
#3

I just tried place a reaction/modifier on the highlight, but it didn't work. Not sure if your screenshot is showing the whole process? Are there any actions required, you just show the listener portion. Thx.

rpacker
Control Surface Studio User
#4

I just test this script: "Track Highlight Relative to Session Box" but when I incorporated into my MX-12 script the css script disappeared!

Be great to get some help with this.
Thanks!

Wim
Control Surface Studio User
#5

Hi rpacker,
True I only supplied the listener since I didn't know how your script is working right now.
About post #4: I would suggest starting a new script (new script name) to test out the "Track Highlight Relative to Session Box" That way it should definitely work!
I will try to make something work later today based on the "Track Highlight Relative to Session Box" and share my findings here.
Greetings

Wim
Control Surface Studio User
#6

Hi rpacker,
I just tried John's "Track Highlight Relative to Session Box" script and it works flawlessly here.
I added a Reaction that automatically sets the highlighted track to the new Session Box view. In this example with 4 tracks; when the Session Box moves 4 tracks to the right (it now shows track 5 to 8) the highlighted track automatically changes to track 5. If the Session Box shows track 9 to 12, track 9 will become highlighted,
It is not perfect yet, but it might get you where you want it to go.
Keep us updated ;-)

rpacker
Control Surface Studio User
#7

Many thanks! I'll give it a try.

rpacker
Control Surface Studio User
#8

It works! I modified it for 12 tracks instead of 4. Also, instead of scrolling for banking, I use a set of buttons to bank by 12. Now I just need to integrate all the other things I am doing such as device selection and parameter banking, etc. Thanks so much!

Wim
Control Surface Studio User
#9

Great to hear that!!
Thanks for the feedback :-)
Just to make sure you know; in script mode, you can drag and drop mappings from one script to the other by clicking on the green icon and dragging them to your new script.
In my workflow, I duplicate the mapping first and drop it in the new script, that way the original mapping stays at the same spot.
Happy scripting!

rpacker
Control Surface Studio User
#10

Thanks for the tip. I am still wrapping my head around CSS and am only now realizing how deep it is.

Wim
Control Surface Studio User
#11

Yeah, that is also a reason why some features, while in our heads straightforward, are not directly implemented. It would get in the way of how other people would like their script to behave...
Have a nice one ;-)