Member Since: March 15, 2006

Country: United States



  • Not using an existing connector. You could always just solder 3 wires to the pins/pads of the 3.5mm jack.

  • You mean like this?

    The WAV Trigger holds 2048 tracks vs the MP3 Trigger’s 255. There are few things the MP3 Trigger can do that the WAV Trigger can’t do better. Just saying.

    Actually, you could connect an XBee S1 module directly to the WAV Trigger’s RX pin and send serial commands over XBee with no on-board Arduino. Just a thought.

  • Anticipating the first question… This version just updates the shipping firmware to the latest rev (v1.21) and updates the above product description with the latest firmware feature set. New capabilities include support for 2048 tracks, real-time playback speed/pitch control and enhanced trigger and MIDI features. It’s no different than if you had bought the previous version and updated the firmware.

    Also, here’s the link to the Arduino serial control library, and here’s a short tutorial on serial control with an Uno.

  • 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.

No public wish lists :(