hi, I'm new to the forum so I'm not sure if this is unreasonable or not...

I made a sample slicer/midifier kind of thing, and then expanded it with a sequencer, I wanted to get this one last feature working on the sequencer before putting it all together (the attached patch has just one slicer bank and one sequencer channel.)

what I added to the sequencer that doesn't quite work is a row of toggles that can deactivate individual steps, regardless of the note that step is supposed to trigger. I had that working, but I then changed it so that the "on/off pattern" of the toggles was saved and recalled from an array so separate patterns would remember the corresponding toggle states...

So, It does work --except for the last two toggles??-- of the sixteen steps (regardless of the pattern) I'm pretty stumped about it, the last two toggles wont keep their setting, the toggle table seems to be stuck for them and just sets them the way it wants.

anyway, I don't really expect anyone to solve that, but the patch is kind of cool anyway... thanks!

http://www.pdpatchrepo.info/hurleur/sample16.pd

I suspect the problem lies in subpatch [pd seq] where you have undefined ordering between the [route] and [tabwrite] objects. Separate these with triggers and the problem should go away.

Very nice slicer btw. Works great with some breakbeats I loaded.

thanks, I messed around with it and it was pretty clear that having that array to retrieve the toggles was way too complicated, so I redid that part with a simpler approach that doesn't involve an array. the whole problem was that I needed to access multiple parts of the array simultaneously which, it can't do, so something made of float boxes seemed better. and it works! I'll post the thing when Ive done some more messing with it.