Bug: Renaming tracks does not reflect to current_input_routing

Jul 11, 2013 at 8:22am

Bug: Renaming tracks does not reflect to current_input_routing

I’ve noticed that renaming a track does not reflect to the current_input_routing property of another track.

You can test with this javascript and by routing audio from one track to another. If you call the following code it will print the input routing for each track. If the source track is renamed and you call the code again it still prints the previous current_input_routing name:

function test() {
var api = new LiveAPI("live_set");
var totalTracks = api.getcount("tracks");
for (var i = 0; i < totalTracks; i++) {
api.path = "live_set tracks " + i;
post("TRACK: " + api.get("name")+" -- INPUT: " + api.get("current_input_routing") + "\n");
}
}

This may be related to another issue I reported: http://cycling74.com/forums/topic/bug-current_input_routing-is-incorrect-by-default-in-midi-tracks/

#255654

You must be logged in to reply to this topic.