to_the_sun

I'm trying to wrap my head a complex m4l mapping abstraction (MapButtonLFO.maxpat). In it there's a [live.observer id] monitoring the id of the mapped parameter. Other than if that parameter disappears completely (resulting in output of 'id 0') when would an id actually change? It doesn't seem like they do, even if tracks move around for example.

when-do-ids-change

they don't - anymore - but they could do when M4L first came out - I think persistent ID's were introduced in 8.2 maybe, so theoretically, if anyone is still using 8.1 then this may happen.

saying that tho, can't remember what happens if you delete a device and then undo the delete - not sure whether it keeps the original IDs or whether a new set get generated...

That makes a lot of sense. There's a gate in this patch that seems to exist solely to keep out midlife id changes, the likes of which i'd never seen. I'll have to check out that undo scenario, but otherwise i should be able to simplify things quite a bit as i adapt the patch to my own purposes.

Looks like upon undoing a deletion ids are retained (and output from [live.observer id]), thankfully. It seems i have everything in working order. Finally!

When do ids change?