Tsunami Super WAV Trigger stops after first playback

Sensors Sound & Audio
1

Hello!

So I have set up my Tsunami Wav Trigger just the basic way: Using USB power supply and trigger sounds by shortly connecting any of the Trigger Input Pins with a ground pin. Headphones are connected to the output pins. Triggering a sound works fine ‒ but only for the first time. After the playback, the status LED blinks shortly once in four seconds. The device stays in this “state”; no further sounds can be triggered until I reset the device. What might be going on here?

The SD card is a Kingston SDC4/8GB card, formatted in FAT32, containing some wave files and some other stuff:

001-100BPM_4bar_pocketOperatorKick.wav
002_AGOGO1.WAV
003_AGOGO2.WAV
004_Alesis_HR16A_04kick.wav
005_Alesis_HR16A_09rimshake.wav
006_Alesis_HR16A_11shake.wav
007_Alesis_HR16A_18bong.wav
008_Alesis_HR16A_33rim.wav
009_Alesis_HR16A_34rim_rev.wav
136-73BPM_200927-stephani005.wav
137-111BPM_BoettcherstrLoop.wav
140-100BPM_4bar_pocketOperatorKick.wav
144-200BPM_1bar_200927-ampel003.wav
167-41BPM_1bar_200927-stephani005.wav
170-51.5BPM_2bar_200927-ampel001.wav
176-93BPM_1bar_200927-stephani005.wav
204-100BPM_pocketOperatorKick.wav
208_120BPM_12bar_BBC-America_San Pedro_Oil derrick..wav
232-78BPM_200927-stephani005.wav
234-103BPM_BoettcherstrLoop.wav
235-100BPM_4bar_pocketOperatorSnare.wav
245-100BPM_4bar_pocketOperatorKick.wav
254-100BPM_4bar_pocketOperatorKick.wav
255-60BPM_2bar_BremenkleinerBlumenmarktKopfsteinpflaster.wav
34-100BPM_4bar_pocketOperatorSnare.wav
42-90BPM_1bar_200927-stephani004.wav
sense.txt
TEST.TXT
tsunami.ini
tsunamix.hex

All .wav-files are 44100Hz, 16-bit

tsunami.ini looks like this:

#TRIG 01, 192, 0, 0, 1, ,
#TRIG 02, 192, 0, 0, 1, ,
#TRIG 03, 192, 0, 0, 1, ,
#TRIG 04, 192, 0, 0, 1, ,
#TRIG 05, 192, 0, 0, 1, ,
#TRIG 06, 192, 0, 0, 1, ,
#TRIG 07, 192, 0, 0, 1, ,
#TRIG 08, 192, 0, 0, 1, ,
#TRIG 09, 192, 0, 0, 1, ,
#TRIG 10, 192, 0, 0, 1, ,
#TRIG 11, 192, 0, 0, 1, ,
#TRIG 12, 192, 0, 0, 1, ,
#TRIG 13, 192, 0, 0, 1, ,
#TRIG 14, 192, 0, 0, 1, ,
#TRIG 15, 192, 0, 0, 1, ,
#TRIG 16, 192, 0, 0, 1, ,
********************************************************************
This file was generated by the Tsunami Configurator v0.30
It's required only if you wish to over-ride the default settings.
You may add your own comments below this line -->

Formatting the SD card didn’t help.

Anyone experience the same or similar issues? Please HELP!

2

A couple of things: Make sure you’re running the latest firmware, and that your wav files match the version, i.e. mono/stereo. Remove the .ini file - it’s not necessary for default triggering. And try the demo files found in the hookup guide.

The best things is to go through the hookup guide step by step. If at any point you don’t get the proper response when following the guide, it then becomes possible that you have a defective unit.

3

Are the numeric track/File numbers supposed to be followed by an underscore? I noticed you had a hyphen after the track number , then the filenames in some of the files. Maybe that was confusing it. I know that when I’ve accidentally inserted 2 tracks that had the same exact number before the underscore symbol, it froze up. I number all of mine in order with the underscore following the track number.

4

The track number should be 3 or 4 digits with leading zeroes. What follows doesn’t matter as long as it’s not a digit (0 - 9.) Using an underscore or hyphen just makes the name easier to read.

Having two tracks with the same number is likely not something I tested, so it certainly could be a bug. I’ll check, but in the meantime… don’t do that!

5

Thanks for the feedback! I just went through the [hookup guide I found on sparkfun.com, when [the SD card reader on my board broke. Operation aborted… :(](Tsunami Super WAV Trigger SD reader broken - SparkFun Electronics Forum)](Tsunami Super WAV Trigger Hookup Guide - SparkFun Learn)

6

wow, that’s a bummer. I ended up with 2 files named the same, because windows could not remove the first one that was named 004_xxxx, a SD card problem, so it left it there. Then it wrote the second one 004_zzzzz.