jayhardesty

I have a device [below] consisting of a live.path that has received "goto live_set tracks 0 clip_slots 0 clip". (such clip exists)

The live.path object thereafter outputs the id whenever I add or delete a track (MIDI or audio) in the set, even though the live.path object has not received any new bang or message. There is no other Max4Live device in the set.

In a real device this is a problem because outputting that id has side effects (triggering other things unexpectedly)

Any idea if/why this would be correct behavior?

The live.path object thereafter outputs the id whenever I add or delete a track (MIDI or audio) in the set, even though the live.path object has not received any new bang or message. There is no other Max4Live device in the set. 

live-path-outputs-id-when-addingdeleting-track

I guess that's normal when using the middle outlet of live.path since the path is re-calculated at configuration changes. This could be avoided by using the left outlet but it may introduce other adverse behavior.

OK that does make sense - exactly what I needed to know. Thanks!

live.path outputs id when unrelated track is added or deleted