Member Since: March 15, 2006

Country: United States



  • You can easily set the WAV Trigger up to automatically loop a track on power up, without any jumpers or trigger connections. However the WAV Trigger can only loop on increments of it’s audio buffer, which is 128 samples long. Unless your wave file exactly fills the last buffer, there will always be some number of samples of silence at the loop point. It will be very small, as in a couple of msecs, but very likely not 0.

    I always suggest using your sample editor to seamlessly loop your file many times and save it as a really long track - there’s plenty of space on the flash card. That way, the short gap will occur very infrequently.

  • Please contact me directly at info(at)robertsonics(dot)com and I’ll help you sort this out. Sorry for the inconvenience.

    Update: I haven’t heard from you, but I did write up this post to help clarify.

  • Those comments apply only to the original hardware version (WIG-12000) and not to the current version (WIG-12897) of the WAV Trigger, wherein the missing cap has since been added to the design. (Mentioned in the comments just above this one.) I will try to make this more clear.

  • How are you changing banks? By changing the MIDI Channel on your keyboard, or with a trigger input using the BankUp/BankDn function? Firmware v1.04 and above added support for using MIDI Program Change messages to change banks. Is it possible that you’re sending Program Change messages? In any event, I’ll have a look at what else might have changed, although I’ve not heard any other reports of problems.

    If it’s easy, can you try the versions between v1.02 and v1.10 and see which one breaks it?

    By the way, I just posted v1.20, which increases the number of tracks from 999 to 2048. Filenames can now have 3 or 4-digit track numbers, up to “2048xxx.wav”. This version also maps all 128 MIDI notes to a bank and supports 16 banks (up from 10), so the MIDI to track number mapping has changed. If you’re using multiple banks, you’ll have to rename files with this version. See the release notes on the download page.

  • So it sounds like your conversion from MP3 to wav is wrong. Have you seen this video? If you simply aren’t able to convert a particular MP3 correctly, you can email it to me at info(at)robertsonics(dot)com and I’ll have a look.

  • Need more info: What firmware version are you using? How are you triggering the tracks? With trigger inputs or serial control? Is it consistent? Does a track that seems to play too slow always play slow, and fast tracks always play fast? How did you create the tracks? What’s hooked up to the WAV Trigger?

    SD Card and track length should not matter. One test would be to remove all tracks from the card except one that plays too fast, remove all the connections to the WAV Trigger and play the track using the on-board button (which plays the lowest number track it finds.)

  • I must admit that cold is not something I’m used to worrying about. It’s usually heat. That doesn’t sound too bad, but I certainly have not conducted cold tests. The only thing I could suggest would be to look at the individual datasheets for the major components and review specified operational temp ranges. Not conclusive, but at least a start. Condensation would of course be bad.

  • Correct. If you’ve managed to blow away your bootloader (which can only be done with a hardware programmer) then you’ll need to contact SparkFun tech support.

  • If you record the output using an audio editor like Audition or Audacity, you can zoom in on any anomalies. With sine waves anything wrong should be readily apparent - both audibly and visibly. I’ve spent a lot of time looking at the output and haven’t seen or heard of this, so I’d be very interested in any data to the contrary.

    The introduction of pitch bend / sample-rate control in firmware v1.05 did introduce some distortion (bad samples) when actually pitch bending, but this was fixed in v1.08 and later. Firmware v1.10 is on the download page now.

  • It’s not supposed to do anything if you request a track that doesn’t exist. Assuming you’re using the serial control port, can you post your code? Are you using the Arduino library or did you implement your own serial port code? Which command are you using?

No public wish lists :(