live.observer playing_status - does it work?
Hello, I am trying to observe the playing_status of a clip.
When I send the live.observer a getid message it sends id 1 or id 11 or whatever so I know it's set ok.
But when the clip plays or stops nothing gets output from either output of the live.observer.
Should this be posted on ableton live forum or is it ok here?
thx
It's ok on this forum but should be in the 'Max For Live' section.
Note that the observer sends output (bang) only on status changes.
it works but sends bang for things other than just play and stop.
such as set looping
I wonder why there isn't a clip start event and clip stop - they would be so useful.
hmmm - I couldn't make this do what I wanted reliably - seems to send lots of bangs for what I would say are unexpected events.
Anyone else had this experience?
I found another way to achieve what I wanted to do without using live.observer playing_status so no sweat in this case but....
I've just checked the playing_status observer and found that it sends a bang at play and stop exclusively if quantization is set to 'None', otherwise it sends a bang also at trigger. The trigger status is mentioned in the LOM, so I don't think there are any unexpected events.
And ironically that's what I did but without the live.observer.
I set quantization off temporarily while I record a clip and then set it back to its original value when done.
And then I don't need to observe whether the clip is playing or not because with quantization off the clip plays immediately leaving no gap at the front of my buffer.
I actually observe the slot_playing item of a track to figure out clip stop and start. This is actually because of other stuff I'm doing, but it works ok.
With the playing_slot_index the live.observer will give you a read out of what clip is playing as the playing state changes.
You can then use this info to know that no other clips are playing on that track.
If all clips are stopped, the LOM states that it will give a read out of -1 (although for me it gives me -2...?)
Like this:
This is the way I got around it. The playing_status wouldn't even bang on a notification of playing state change for me...