In some situations it is useful to be able to trigger continuous play from a hardware trigger. Initially we thought it might be possible to configure the target channel both as triggered mode and continuous loop mode. However, we observed that as soon as we configure the channel as continuous loop from software the pulse train starts playing.
Diving into the firmware source it seems like indeed a soft trigger is automatically sent to the channel when continuous loop is enabled.
|
SoftTriggerScheduled[inByte2] = 1; |
It would be great if this behavior could be modified, either disabled or contingent on the state of trigger mode. It would also be important when in triggered mode to reset the channel when the trigger edge falls, similar to how it happens with a finite pulse.
Basically a trigger mode configured continuous loop pulse train should work exactly the same as a very, very long finite pulse.
In some situations it is useful to be able to trigger continuous play from a hardware trigger. Initially we thought it might be possible to configure the target channel both as triggered mode and continuous loop mode. However, we observed that as soon as we configure the channel as continuous loop from software the pulse train starts playing.
Diving into the firmware source it seems like indeed a soft trigger is automatically sent to the channel when continuous loop is enabled.
PulsePal/Firmware/PulsePal_2_0_1/PulsePal_2_0_1.ino
Line 521 in ecdbcf4
It would be great if this behavior could be modified, either disabled or contingent on the state of trigger mode. It would also be important when in triggered mode to reset the channel when the trigger edge falls, similar to how it happens with a finite pulse.
Basically a trigger mode configured continuous loop pulse train should work exactly the same as a very, very long finite pulse.