"fired_slot_index" behaviour changed, bothering anyone else?

Learn about building and using Max for Live devices.
Post Reply
joaoorecchia
Posts: 61
Joined: Sun May 03, 2009 3:25 pm
Location: Johannesburg, South Africa
Contact:

"fired_slot_index" behaviour changed, bothering anyone else?

Post by joaoorecchia » 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

Jabbon
Posts: 161
Joined: Wed Apr 16, 2008 8:57 am
Contact:

Re: "fired_slot_index" behaviour changed, bothering anyone else?

Post by Jabbon » Fri Apr 29, 2011 2:57 pm

mmm, yeah, actually more than bother it is imprecise, in the end it was indeed handy.
On the other side there is this very other handy thing which came in with the id assigning which is so much more reliable...
sound spatialization content & technologies @ audit-orium.com

joaoorecchia
Posts: 61
Joined: Sun May 03, 2009 3:25 pm
Location: Johannesburg, South Africa
Contact:

Re: "fired_slot_index" behaviour changed, bothering anyone else?

Post by joaoorecchia » Fri Apr 29, 2011 8:30 pm

Hm, what's the new id assigning thing?

Post Reply