WAV trigger : sample clicking

Hi sparkfun community !

last year I revived an old organ pedalboard by soldering its 13 keys to the triggers of a WAVtrigger board, and using the 3 last ones to navigate between banks.

It works fine, except each sample emits a very audible “click” right at the beginning of the sound. I sampled two different instruments (a vox continental playing long notes, a fender rhodes playing short ones), normalized the samples to -1db using audacity and the click is the same on both instruments.

I tried normalizing at a lower level, but the click is still here (propotionally softer of course). I even tried to reexport my samples with an exaggerated fade in curve of 0.25sec, but it didn’t really change anything.

I’m using a 12V DC adapter (the only one I have laying around).

Anybody encountering similar issues ?

Cyril

This is usually due to running older firmware, try updating to the latest version here Downloads — Robertsonics and see how that goes after :slight_smile:

Thank you for your quick answer.
I don’t own a USB-TTL adapter at the moment, do you think I could use an arduino mega as an adapter, as I’ve seen others do ? I don’t quite know how to do that, though…

Where are you wanting to use it? The Tsunami guide (pg 17) suggests using the SD card to update firmware

As I’m using a WAVtrigger (and not a WAVtrigger pro or a Tsunami) so I don’t think I can use the SD card to do the upload, according to the WAVtrigger user’s guide.

I tried hooking the 5v, gnd, Tx, Rx of my arduino to the wav trigger and then followed the instructions for the update. WT-flasher recognized my arduino but it couldn’t connect to the WAVtrigger and the “program” button stays greyed.

Ah, somehow I got it in my head that it was a Tsunami - using the Mega might be tricky, as you’d need to have it behave strictly as a pass-through and I’m not sure if it can do that with interfering (I also don’t know if the WT flasher wants specific serial formatting/settings to sommunicate…if the flasher uses a different baud you’d need to figure that out too).

Feel free to poke around and see if you find something, but the TTL-> serial adapter method is the tried-and-true way to update the regular WAV Trigger and the one I’d recommend. Otherwise, feel free to try your hand at putting the Mega in standby byt wiring RESET to GND and wire it as a pass-through and see if that works. Alternatively have it be active and use a sketch to forward serial data and try it that way? Something like

void setup()
{
  Serial.begin(115200);
  Serial1.begin(115200);
}

void loop()
{
  while (Serial.available())
  {
    Serial1.write(Serial.read());
  }

  while (Serial1.available())
  {
    Serial.write(Serial1.read());
  }
}

For Mega:
Serial = usb comms; incoming data
Serial1 = hardware UART pins 18 & 19; output to WAV Trigger

And see if you can get WT flasher to turn gray (ensure you have the hex file loaded too!). I’d give the 2 Mega methods fairly low chances of working but please share if you get it working!

Note in the first method (hardware pass-through) you might have to wire it strangely…if the Mega is asleep I’d think you have to wire RX to RX and TX to TX which is the opposite of how you’d normally do it (and normally for the sketch method)

How are you listening to the output of the WAV Trigger? Are you using the 1/8" stereo line-level jack with headphones, amp or powered speakers? Or are you using the on-board mono amp directly to a speaker? Does every track have the same click? Can you post one of the tracks?

If you are using the on-board amp and speaker, be aware that powering the WAV Trigger with 12V will cause the linear voltage regulator to get very hot. I would recommend 6V or 9V at the most.

Regarding firmware updates for the WAV Trigger, you do need the equivalent of a USB-to-serial adapter - something that looks like a USB COM port to a computer, and has TTL-level RX/TX/GND connections on the other end. The Robertsonics WAV Trigger Flasher application sets the baud rate of the COM port and communicates directly with the resident bootloader in the STM32F407, so it does need to be a transparent pass-through in both directions.

My best guess at the moment however, is that your click is not a firmware issue.