"fired_slot_index" behaviour changed, bothering anyone else?
Posted: Fri Apr 29, 2011 12:59 pm
I observe the fired_slot_index on a specific track, using the number to trigger a variety of things in my set.
Since the last update, it only outputs a number IF there's an actual clip playing somewhere in the observed track. Previously it would output the number of the clip slot even if it was empty (as long as it had a stop button) and even if there was no clip playing in the track.
I've been in touch with Support and they think it's not a full blown bug and suggested I post here to see if anyone else is bothered by it. There are workarounds for me, but it's a pain in the ass and feels like a bug, since we're talking about clip slots and not clips.
João
PS. I'm on the latest versions of Live and M4L
Since the last update, it only outputs a number IF there's an actual clip playing somewhere in the observed track. Previously it would output the number of the clip slot even if it was empty (as long as it had a stop button) and even if there was no clip playing in the track.
I've been in touch with Support and they think it's not a full blown bug and suggested I post here to see if anyone else is bothered by it. There are workarounds for me, but it's a pain in the ass and feels like a bug, since we're talking about clip slots and not clips.
João
PS. I'm on the latest versions of Live and M4L