Recently I encountered somewhat of an oddity with a WAV Trigger. I have it set up with a wavtrigr.ini file that provides for edge triggering of all the WAV files I have created, with the low-power option active so the unit goes to sleep a few seconds after playing the last track. All is well with this, but one of the test signals I created is a WAV file consisting of ten seconds of recorded silence. This file plays perfectly as long as the unit is awake, but triggering that particular track (UNlike all the other tracks!) will not wake up the WAV Trigger. Now this does not create any problem for me, but it sure lights up my curiosity. Is this a firmware bug, or was the WAV Trigger intentionally set up to act this way? Please explain in your best detail.
Thank you,
Richard Faith