WavTrigger still retriggering w/firmware 130b

Sensors Sound & Audio
1

hi there!

small problem.

i want to use the WAV trigger for something that seems simple enough: press a button, hear a single random soundfile.

only when that file has ended, the WAVtrigger should respond to a new button press to play another file.

while the file is playing, i want button presses to be ignored.

now i have hooked up a button to trigger 1.

my settings are: Trigger01, contact closure, edge type, random (tried ‘next’ as well.).

non-inverted, re-trigger disabled (want files to play all the way through), polyphonic disabled (want to hear only one file at a time), loop off.

if i press the button multiple times but rather slowly, all seems well.

however when i press the same button in rapid succession, files don’t play all the way through and at some point a new file will start, interrupting the one playing. after that, the WAVtrigger seems to go haywire in whether it will respond to a retrigger or not. even slower presses will retrigger.

i tried upgrading to both firmwares 130b and 131, as for 130b it states ‘Fixed bug that allowed track re-trigger if both Re-Trigger and Poly options were deselected’, which describes exactly what is happening.

i upgraded using the sparkfun FTDI (and the flasher app says upgrading is successful). no luck, same behaviour.

i could insert a 555 timer to slow triggering down, or i could run trigger + PLO signal through an AND gate, but i would think the WAV trigger should be able to do what i want on it’s own?

any experiences with this? thanks!

2

Sorry - just saw this. Certainly could be a bug. I see that you’ve tried both “Random” and “Next” trigger functions. While I know it’s not the function you want, have you tried it with the “Normal” trigger function? It’s possible that the same bug that I fixed earlier is still present when using these other trigger functions.

I’ll take a look and get back to you here.

3

hello robert, thanks for your reply.

i haven’t tried the ‘normal’ function really, since that would only play the first file again and again :slight_smile:

but i definitely see your point - will try it and report back.

4

I think the same issue that I had previously fixed for the Normal trigger functions was similarly plaguing the Random, Next and Previous functions. I just posted new firmware v1.34 on the download page. Please give that a try and let me know how it goes.

5

will do! thank you, will report back asap!

6

yes! success.

thank you very much for the quick follow-up.

happy camper.

am i correct in assuming that there is no such thing as an ‘exclusive random’ - i mean going through the full list before repeating an item? this sounds like every trigger is it’s own new dice roll.

( like in PureData there’s the [urn] object, which keeps track of which files have already been played and which ones haven’t, and only chooses from the unplayed ones until all items on the list have been used.)

this is for an artist’s installation, so i’ll discuss with him if he prefers the hardcore randomness (with possibility of early repeats) or the ‘next’ function, fixing the order.

anyway, it works as expected now, thank you for that!