Hi Brennan,
With the pre 5.x.x firmware I was getting oneshot functionality by using a midi controller that would send 3 midi cc commands, in sequence, with one footswitch press:
CC:39 value:x (solo track x)
CC:43 value:1 (start playback)
(automatic 500 ms delay supplied by midi controller)
CC:43 value:0 (stop playback)
This would achieve selecting the desired track, start playback, stop playback at the end of the part, all with one footswitch press.
With the regression of the solo function in firmware 5.x.x, my oneshot songs no longer work.
I set out to reprogram my midi configuration to recover those oneshot songs when I found another functionality change that may prevent this entirely.
I have found that with the 5.x.x firmware, if there is a one second or less delay between the start and stop signals, the Aeros will stop immediately when getting the stop command.
If there is, for instance, a 5 second delay between the start and stop signals, the Aeros will play to the end of the loop and then stop.
My midi controller will not allow me to delay an automated midi command for more than 1000ms, which was an adequate delay for the pre-5.x.x firmware, but is not long enough for the 5.x.x firmware.
Was the change in rapid start-stop behavior intentional, and is there any possibility of getting 5.x to behave like 4.x did?
Is there any possibility of getting a specific oneshot midi command that would select a specific part, start playback, and stop playback at the end of the part, all with one midi CC command?
Thank you!