Source Selector: Track.sourceSelector()

Post Reply New Topic
RELATED
PRODUCTS

Post

Is there anyway to set the source on the track source selector?
source_selector_in.png.png
I'm looking at the API and it seems like its missing those parts? or am I missing something or perhaps even the documentation is missing an inherrited class here.
source_selector.png
I'm not even sure how this would help any script? From what i see here it just provides read only values if something is selected or not...
You do not have the required permissions to view the files attached to this post.
----------------------------------------------------------------------
http://instagram.com/kirkwoodwest/
http://soundcloud.com/kirkwoodwest

Post

I was wondering the same when it was introduced and think this is simply unfinished.

Post

Kirkwood West wrote: Tue Feb 15, 2022 8:55 pm I'm looking at the API and it seems like its missing those parts? or am I missing something or perhaps even the documentation is missing an inherrited class here.
The API is missing a good number of things, although thankfully that list is gradually shrinking. As always, complain to them loud and often enough, they might consider adding it. I can see this one being iffy, though.

Post

I sent an email to Jesus. Hopefully we will be able to script some source selection at some point I’m the future. 🙏
----------------------------------------------------------------------
http://instagram.com/kirkwoodwest/
http://soundcloud.com/kirkwoodwest

Post

Just want to throw my hat in here, I requested this addition (for likely similar reasons) about 6-7 years ago. Would love to see it happen.

Since then I've come up with an alternate solution for my particular use case (live improv) where I group track inputs by color, and have my script only ever arm one track per color group at a time. So I can have both my drum pad and keys on different tracks, and only ever on one track at a time. But they can never control the same track (which works for me). If I had two keyboards, it wouldn't work.

Post

Oh, and if you really want to get around it, I just had an idea!

So far, the best way I've found to communicate between different scripts is by observing the master track name, and then passing communications through it. If you have a better way, use it.

But you *could* finagle a way to make different controllers coordinate with each-other and trade midi channels. Each of these midi channels would be for a different track. Then there are multiple ways to only allow one channels data through per track.

Post

key thing here is to be able to set the routing. i see the work around though. thats a great idea.

My goal is to create a new channel based on a channel that already exists. Then have it route the audio or midi from original channel.
----------------------------------------------------------------------
http://instagram.com/kirkwoodwest/
http://soundcloud.com/kirkwoodwest

Post

Still wishing I had this available to change the source selector. Would be a huge win for my extension.
----------------------------------------------------------------------
http://instagram.com/kirkwoodwest/
http://soundcloud.com/kirkwoodwest

Post Reply

Return to “Controller Scripting”