Hello,

first let me discripe my project in short way:

Im using a wii nunchuk-controller with an arduino to controll short wav-files(small soundfiles like a drumkick) played in pd.

I want to use an array to store which file shell be played (0 for none, 1, 2, 3, etc.). With a [select] pd choose the rhight file. The Arduino sents messages every 125ms.
This is working so far...

But now my problem: By pressing the "C"-Button the user decides to not play from the array but from his interaction-input. And by pressing the "Z"-Button the user decides to override the old array with his interaction-input. But the Array shell only have the length depending of the users-input (so that their is no pause in the loop or the array is to small).

So in my thougt I need to "reset" the array if the user hit the Z-Button and than resize the array +1 each intervall the Z-Button is pressed. But I can't find a way how to detect if the "1" from Arduino-input is sent the first time or in a row, so PD don't knows if it should count up or reset.

So is there a object or a construction giving the following logic:

bang if you got a 1 the first time, but do not bang if it is the second time without getting a 0 before?

I hope you understand me and have a solution. If not please ask or help me to explain better

@Abgehter Hi, this kind of logic lets only the first 1 through until a 0 is received

EDIT: I mean, it sends out a bang at the first 1 only

Great thank you, it works fine

I know its a little offtopic but can someone show me the right syntax for the |resize< message-box?

i tried

|number]
|
|resize $1 datas1< and also |resize datas1 $1<

All i got is a "argument $1 out of range" Error.
I also tried it with replacing $1 with 100 and klicking it but nothing happend. Do i need to connect the outlet to somewhere? Its a little confusing^^

@Abgehter Assuming you mean resizing a table, here are two ways of doing it:

@Abgehter If you are loading .wav files you just need to include the -resize parameter as you open the file, and send it to [soundfiler].
The message will automatically resize the array to the length of the file.
You don't need to use the same array all the time. You can have many. They are not expensive in cpu terms if they are kept hidden.
Once loaded, maybe at the opening of the patch, they stay loaded and can be reused for instant playback.
play.zip
You can also use abstractions to automatically load the samples, and keep them hidden.
abs_play.zip
You can also avoid repetitive triggering with [change] and then [select]........ although the info @weightless gave you will be useful for doing more complicated logic with your data.
David.