I am having trouble with the loop function on the Tsunami. The track will not loop unless it has already been played by a trigger. I am still trying to understand what steps need to be taken for the serial command to loop the file, but I can make it work as long as I have setup the triggers and trigger one before sending the command.
Once I have physically triggered a set of tracks using a trigger pin, the command seems to work every time.
I have tried firmware version 0.8 and 0.9
This is an example the message I am sending:
f0 aa 0a 03 01 09 00 00 05 55
Starting this trigger seems to get things working:
#TRIG 05, 48, 0, 0, 14, 9, 16
Thanks for any advice
This certainly could be a bug. Once you use the trigger to start the loop, can you turn off the loop using the serial command, or does it always loop when started via serial? I’ll take a look at this and report back here - might take me a few days.
Maybe there’s a misunderstanding about the function of the serial TRACK_LOOP_ON / TRACK_LOOP_OFF commands. These commands simply set the state of the track’s loop flag to true or false. You must use the TRACK_PLAY_SOLO or TRACK_PLAY_POLY to start the track. Once started, the track should honor the state of the loop flag. You should also be able to change the state of the loop flag while the track is playing. If you issue a TRACK_LOOP_OFF to a track which is currently looping, it should play to the end of the track and stop. Let me know if I misunderstood or if this still doesn’t work for you.
I think it probably is a misunderstanding on my part. I will try to issue the TRACK_LOOP_ON command after it starts playing. I am having trouble understanding the order in which flags need to be set, but I think with the information you have just provided, I might have success.
Thank you for the prompt reply! I will follow up tonight.
robertsonics:
This certainly could be a bug. Once you use the trigger to start the loop, can you turn off the loop using the serial command, or does it always loop when started via serial? I’ll take a look at this and report back here - might take me a few days.
I can stop it with a serial command.
It was totally my misunderstanding of the format of the message. I’m no programmer, but if I could make a selfish suggestion for the manual, I would ask for extremely verbose examples. In the end, it is all clear, but I did struggle with what each component of the command meant.
Thanks for making a wonderful product! If you or anyone else is interested, I am using ten of them to play the audio in a rather big haunted house attraction. Last season they were set up to play the tracks on loop by permanently shorting a trigger. I added an emergency evacuation message to make the fire department happy. The tracks were triggered by a remote optoisolated switch. Unfortunately, the long wires and hostile noise environment caused too many false activations for production. This season I am adding an ESP8266 to each one which will receive MQTT control messages by WiFi and send commands to the Tsunami via serial. No more false activations (evacuations!) and many more possibilities than the “dry contacts” were capable of.