maybe like this ?

this is not useful in M4L considering my needs :/ as i said it will send 0 when "anything else" will be touched/selected "on the same channel" as the device . and it will send 1 when i touch the device , thats not useful in my case . the [closebang] works great but opposite way :/ it will bang when i leave the channel ,thats fine ,but the other way ?

ps: what i want to do is to isolate UI update when channel is not selected , i can stop UI but cant get it back automatically when i back to my channel

i haven't any experience with max for live so i might be wrong, but cant you just use the "1" from the [active] ? with a [sel 1 0] as i posted above ? Use the bang from 0 to stop the UI update, and the 1 to restart it. Nikolas

thanks for your time Nikolas. well ,[active] will send 1 only when i touch the device ,not when i get back to its channel ,so i must go back to its cahnnel and touch again the device to see its update :/ . [closebang] sends a "bang" when i leave the channel only :/

Ok, I got it i think.. sorry i couldn't help!

its okay Nikolas , thanks again

can you not just observe the 'selected_track' ? when the selected track is the track you're on, you got your bang..

with [live.observer] ? i hope i can but cant get my head over this methodology ,commands and stuff ,its way too complicated .

ps: i could not get it to work with [live.observer] ,im sure im not doing it right ,mess of commands ,im not sure what to call where , and the other objects require a bang everythime to get the data from them .

put this in your M4L device, the toggle indicates whether the device is on the selected track or not.

Note it will only work for devices that are right under the track, not for devices that are in chains within racks (its just a small modification to make that work)

omg . basvlk !! thank you for your time , i thought that only [live.observer] can detect any changes ,ive never came across [thisdevice] thing . this is utterly amazing :D thanks again

much.love k

no worries - we've all been through the steep learning curve. Just promise you'll go through the tutorials, and help some others here :-)

it's not the live.thisdevice that notices the changes. thisdevice is just initialising the patch.

It's live.path which dynamically updates. There's also an interesting difference in the outlets of live.path but I won't bother you with that, it would probably ruin your mood...

wow - I forgot the 'deferlow' which is the other thing that will drive you crazy in M4L! below an improved version, this one should work for any device, including the ones buried within racks

im trying my best to get my head over the problems of others ,often without a luck ,sometimes i just have thoughts that might or might not be on the point ,so im trying to avoid the confusion and not to post potentially wrong answers but it happens too . i promise of course,also to myself , i mean my knowledge is relative to my progress as with everything (success over the problems) and i dont see an end of this but it depends on the case . i will get better ,it will be good for all LOL .

actually you can bother me with that "interesting difference" of the outlets , now definitely i would love to know the scenario .

thank you for an update and those informations !!!!