display_name (track)

You need this in js?

yes. But either way, with max object, getting name seems to nee to go through observer / audio_outputs / available_routing_types

Max:

JS:

function bang()
{
    var mytracks = new LiveAPI("live_set");
    var track_ids = mytracks.get("tracks");
    post(track_ids + "\n");
    
    for (i=1; i <= track_ids.length/2; i++)
    {
        mytracks.id = track_ids[i*2-1];
        post(mytracks.get("name")+"\n");
    }
}

Oh wait, you wrote "display_name". I thought you meant the normal track names.

no great, i mean i was using another path, but this is nice too, thx! display_name is like name i think.
Would you know how to keep this list updated if you delete or create a track?
i m trying with a callback function that i use for other property, but i can't get it work.

First no, display_name is what you see for example in the input routing dropdown of a track. In case someone wants to get them:

function bang()
{
    var mytracks = new LiveAPI("live_set");
    var track_ids = mytracks.get("tracks");
    post(track_ids + "\n");
    
    for (i=1; i <= track_ids.length/2; i++)
    {
        mytracks.id = track_ids[i*2-1];
        
        var dict = new Dict();
        d = mytracks.get("input_routing_channel");
        dict.parse(d);
        post(dict.get('input_routing_channel::display_name') + "\n");
    }
}

And here is a track name observer:

function bang()
{
    var test = new LiveAPI(callback, "live_set");
    test.property = "tracks";
    
    
    function callback(args) 
    {
    
        if (args[0] == "tracks")
        {
            post("tracks changed" +"\n");
            var mytracks = new LiveAPI();
            
            for (i=1; i <= (args.length-1)/2; i++)
            {
                mytracks.id = args[i*2];
                post(mytracks.get("name")+"\n");
            }
        }
    }
    
} 

thx a lot! the difference between display_name and name wasn't clear to me.

And also thx for the observer :)))

Such help is really precious honestly. The forum where i use to come for usual max ressource is pretty poor in js, and even more for js/live.api while i find js is more appropriated to control live.

hi 11olsen,

i cant get the display_name part working. I think it's the wrong path, and display_name doesnt exist in song/track.
I m saying this because my end purpose is to have a dynamic dict that containes current live track name, so i think it'd be easier to use an array that exists, from available_output_routing? isn't it?

This is working:

var mytracks = new LiveAPI("live_set");
mytracks.goto("live_set this_device canonical_parent");
var t = mytracks.get("available_output_routing_types");
var d=new Dict("mydict")
d.parse(t);
post("dict_elements",t);

It creates a dic with all the tracks but i have now another problem, to query the subkeys. This is not working, because it's a dic in a dic:
post(dict.get('available_output_routing_types::display_name') + "\n");

Would you mind to help? maybe it'd be easier to parse only by
{"display_name" : "1-audio", "2-audio"}

but I dont know how to do it. In max it's ok using route dictionnary + dict.unpack , but for some reason i want to achieve this in js. How would you do this?
thx!

I still don't understand why you think that available_output_routing_types or input_types can give you a complete tracklist of your Liveset. Depending on the tracks this list is incomplete and includes things like "Ext. Out" and "Sends Only" which are obviously no track names.

I m saying this because my end purpose is to have a dynamic dict that containes current live track name

So why not modify the track name observer example and update a dict in the callback method?