M4L Device that simply displays the name of currently selected scene
Hi,
I'd like to have a simple M4L device that just displays the name of the selected scene in a large font. During my live show, my laptop is often a bit further away and this would make it easier to know where the live session currently is.
Any ideas how to accomplish this?
Thanks!
Best,
Karan
Hi,
this works great - thanks so much!
I have a good understanding of the standard concepts of programming (like Java) and have never really worked with Max but I am interested in learning. Could you maybe briefly explain what the separate components do?
Thanks,
Karan
I am actually not Live user, this was part of the patch I made to help
someone out.
As you can see there are only few objects live.path, set to monitor the set
and live.observer No. 1 asked to report selected scene when it changes.
Second live.observer is than asked to report name of selected scene.
All the time id's of monitored items are sent to next objects together with
parameter which has to be observed.
If you have interest in that stuff, than you have to read
Live Object documentation.
Hey there,
I have a follow up for this question:
I would like to modify this patch so that I can also see the next (or potentially next two) scene's name(s). I tried doing this by basically adding a "+ 1" object after the "pipe 100" object. This only works for a few scenes and spits out seemingly random values for others. Not really sure why this is happening. I have pasted the patch I am currently using at the bottom(converted it into an Max Audio Effect to be able to insert it onto Audio channels).
I am monitoring the values going into the "id $1" object and incrementing them. I am testing this patch with an empty Ableton Liveset that has 14 scenes named "1" - "14". I have documented the values and displayed name for each selected scene.
As you can see it doesn't work for the first two scenes and also has a weird jump when the 8th scene is selected.
Would appreciate any help!
Disclaimer: I am still very inexperienced with M4L, so I might be making a simple mistake, sorry about that in advance!
you have to list all scenes, fill coll with their ids or even names.
when you get selected scene id call ids of 1 or 2 next scenes
to display them.
Hi,
thanks for the quick reply! So instead of going to "live.path live_set view", I'd have to go to "live.path live_set scenes" to get a list? How would I fill the columns of the list? Sorry, just know some traditional programming concepts but can't really figure out Max.
I also tried changing the "id $1" command to "id $2" since I thought this might get the next item but this doesn't work. I'm guessing the list after the "unjoin" object only has one item in it.
Sorry once more for being so clumsy and helpless with this!
Thanks in advance!
AFAIK the id numbers are dynamic, reusing id numbers directly or assuming they will scale regularly doesn't work (all the time), you can't assume id 12 will be the next Scene after a Scene with id 11 (or even a Scene, could be assigned to a device or knob this time).
(Not really sure how dynamic they are, for example maybe a saved Set retains the ids, maybe they change every time you load the Set, I have no idea.)
I think live.path is used to get the id for the "path".
Okay wow, yeah this works! Thanks a ton!
I tried to look into the patch, thinking I might be able to modify it so that I could output the different scenes to different messages boxes (so that I could display each scene name in a different size and maybe different color) but honestly, I don't really understand what it is doing at all...
Could you give me a hint on where in the patch I could get each scene name to a seperate box? Or is this not possible in this patch?
And could you maybe also tell me where I could modify if I wanted to maybe even also display the scene previous to the selected one?
Really don't want to be annoying but you really seem to know your way around and I want to soak in as much as I can.
Best,
Karan
In that patch umenu gets filed with scene IDs, NOT their numbers.
When a scene gets recalled, live_observer sends it's ID out to menu with symbol prepended,
which makes umenu recall that id, and 2 delayed bangs
send next message to umenu, which then outputs next 2 scene IDs.
Exctly what you asked for.
So it is not set to route to different places or to step backwards.
It runs in a loop, when last one is reached it counts from the beginning.
That's the way umenu reacts to next message.
Doing what you want is bit more complicated.
here is one option, it could maybe be done eith less and
different objects, but as menu is allready used let's keep it that way.
I don't use live, but it is known to be a bit laggy compared to Max
when one uses observer stuff too much
Once again, thanks so much! This works great for what I need.
I'll make sure to try and understand the patch more in depth but for now it's great to have a quick and working solution! Really appreciate it!
Best,
Karan
Hi, I'm new here, I found this device interesting. Is there a way to export the reproduced scenes in txt?