Select Track – Suddenly Relative?

Solved384 viewsCSS BugsBug
0

I noticed unusual behavior from my script and eventually troubleshot down to a conclusion that behavior has changed on Select Track. Previously, when I use Select Track in a reaction and provide a track position number, it would select the track position as is. Now it seems to account for only visible tracks when I have folded groups. My use case is looking for the track position (Unless I refactor approach).

A few things have changed since I last used this, I\’ve upgraded to Ableton 12.3, added Push 3, and went from CSS 3.0.1 to 3.1.1, I\’ve added functions to my original script and saved new version. For this testing in this, I created a new scripted, imported two relevant mapping and also generated two simplified new mappings.

While I am not sure, I noticed on CSS3 release notes something perhaps related:

However there are references to UI options that I don\’t see in my CSS3 UI.

When folding it up, I would expect based on prior scripts and experience, the logging of the positions would have remained explicit positions: 0, 3, 4, 5 instead I’m getting dynamic positions back.

toneyvecchio Selected answer as best
0

You’re correct, the set selected track action was changed to use visible tracks only.

if you don’t want to use all tracks, use the following code instead:

self.song().view.selected_track = self.song().tracks[1]


The square brackets at the end [1] are where you insert the track number, these are zero indexed so 0 is track 1, 1 is track 2 and so on.

toneyvecchio Posted new comment

That was the fix, I’ll refactor my code – thanks!