zatch_attach
Well-Known Member
Had a strange bug happen this Sunday that I think is worth discussing. I have a Keeley Halo that I control with Auto Tap tempo from Function Switch 1. What I discovered was that, if the user saves a preset on the device while the Auto Tap is running, the PBC can save that Function Switch in the "on/closed" position, which will break Auto Tap for that preset.
To test, try this; set up a settings file with a momentary FN1, then set up Auto Tap to use it. Make a preset with a nice slow tempo, and add at least 4-5 taps to Auto Tap. Now, when you switch to this preset, and Auto Tap is currently running, manually save that preset (in my case, by holding the Loops button).
I was able to consistently create an "On" override for my test preset by doing the above. And when I did, FN1 no longer properly functioned as a tap tempo source for the Halo. Weirdly, I still heard the relays opening and closing... but saw no change in the tempo the Halo received. When I got back to my computer and removed the override, everything started working as expected.
As far as expected behavior, I would expect that Function Switches that are set to "momentary" probably should not be able to create a state override when presets are saved. However, I can see how users would sometimes like to save presets with a virtual momentary switch held closed. So, my compromised suggestion is that FN Switch overrides are not saved for switch states that are being changed by Auto Tap. After Auto Tap runs, perhaps the override-on-save feature could be reactivated.
Anyways thanks for coming to my TED talk
To test, try this; set up a settings file with a momentary FN1, then set up Auto Tap to use it. Make a preset with a nice slow tempo, and add at least 4-5 taps to Auto Tap. Now, when you switch to this preset, and Auto Tap is currently running, manually save that preset (in my case, by holding the Loops button).
I was able to consistently create an "On" override for my test preset by doing the above. And when I did, FN1 no longer properly functioned as a tap tempo source for the Halo. Weirdly, I still heard the relays opening and closing... but saw no change in the tempo the Halo received. When I got back to my computer and removed the override, everything started working as expected.
As far as expected behavior, I would expect that Function Switches that are set to "momentary" probably should not be able to create a state override when presets are saved. However, I can see how users would sometimes like to save presets with a virtual momentary switch held closed. So, my compromised suggestion is that FN Switch overrides are not saved for switch states that are being changed by Auto Tap. After Auto Tap runs, perhaps the override-on-save feature could be reactivated.
Anyways thanks for coming to my TED talk
