🔥 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.

Maybe a bug report? Track Number Differs when group track is expanded

Submitted by danicroitor on Wed, 06/06/2018 - 06:56
danicroitor
Pro User
Control Surface Studio User

Hi,
I've noticed that when I"m using group tracks ... lets say that I want to map track 11 witch is the Bass Gtr. Before the track 11 I have a group track with keys. If that group is closed then yes, the track 11 would be bass but if that track is expanded then one of the keys track would be track 11. Is there anyway to avoid that aside from not using group tracks or keeping them always expanded. I"m working with a pretty good amount of tracks and It is necessary to have group track in order to navigate easily.

Also want to point out that this is not happening when using the Ableton midi mapping function.

thanks!
Dani

3 Responses

Comments

JohnC
Forum Admin
JohnC - Sat, 06/09/2018 - 14:02
#1
Hmm no way to avoid this at the moment. The track type 'specific' is designed to control whatever is at position 11 at any time. Where as the way Ableton internal mapping works is to attach the function to a certain track, meaning if you move your track to position 2, it will still control it. John
danicroitor
Pro User
danicroitor - Mon, 06/18/2018 - 16:47
#2

If you can make any button turn of and on wouldnt be possible to take the tempo message and convert it some how to on/off state of a button? does that make sense? This way doesn't matter if a controller has a certain way of making stuff blink.

I have an livid cntrl and the default script had that - I don't know actually how is implemented though (if you wanna take a look: https://www.dropbox.com/s/j6xpuo60owc4hhs/Livid_CNTRLR_v2_retro.zip?dl=0 )

danicroitor
Pro User
danicroitor - Mon, 06/18/2018 - 16:50
#3

wrong post... sry :)