Could someone cast an eye over my drum sequencer pls. Previously rows 1 & 2 were working fine and printed the right values, then row3/4/5 etc started printing step values 1 behind. i.e. 0 when it should have been 1 and 1 when it should have been 0.

Annoyingly i deleted and reduplicated the subpatch for row3 then saved it, so i doesnt occur any more! But nothing is different.....why would this be? Have I got the sequence of events wrong? How should the flow be going?

errrr

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

It looks okay to me. I bang [r pos] and it cycles okay, the values seem to get written to the right place in the table and read back out correctly too. There's an undefined order in the reader, but that shouldn't make a difference because it only has an effect the instrument order on each beat*

Maybe you just got into a muddle with how you were testing it.

If you still have probs try and make a test rig patch to *clearly* demonstrate where you think the error is.

*(aside hint: if there is ever any delay/order issue between sounds on a single beat define this order as hi-hats, then snare, then kick for the best consistent sound - ie start with the highest frequencies and work down)

yeah it seems to work fine now. Maybe there was some scrappyness lingering from previous subpatches, when I edited the patch in the text editor.

On a sidenote, Pd seems to format the text in a rather random order - If I format it and group all the toggles into one chunk of text into a more linear fashion would this maybe break the layout (assuming that none of the lines were broken)?

Thanks for looking and for the tip!

AAAAarrgh its doing it again!

I added some little toggles for accent. Try toggling the first togs of row 1 and watch the post window. The 0 and 1's are inverted. Do send somehow sum and invert values if they're being shared? Its confusing me and its self. :/

ta

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

your subpatches that catch the toggle values have undefined executions.

there are 2 patch cords coming out of each receive object, but without a [t f f] ,

elsewhere in your patch, you depend on the instrument number being sent second, so you should use triggers in those subpatches to do that.

probably something similar going on with your accent triggers, though i didn't check that, and just closed pd.

in general, i think it's a good practice to ALWAYS use triggers, and rarely, if ever, take two cords from the outlet of one object.