I notice the conversation has shifted to latency.
I know these amounts are small and probably not noticable.
But...this is a big reason I'm afraid to move from hardware to software Looping. The clock sync in my hardware rig is sooo tight( at least to my ears) and I'm really afraid of latency being an issue in software setups.
If we have latency from the pedal push to the command coupled with the inherent latency of computer based systems where does that leave us? Especially for tight rhythmic work.
It must not be too bad though because Alot of people use software/laptops/controllers live.
Ed Sheeran now uses Mobius in Ableton with a custom made foot controller and his stuff sounds super tight. Granted he probably has a $5000 laptop.
On Tue, Dec 8, 2015 at 4:48 PM, andy butler <email@example.com> wrote::-( 5mS is about max for me (including response time of the looper)
As I said, I didn't measure it, so it could be lower... I really can't tell past a certain point. How would you measure this?You can get the arduino to drop whatever it's doing and respond *immediately* to your button press if you use the hardware interrupt pins. The bulk of the latency would then be determined by your button debouncing... you would have to use buttons that stop bouncing very quickly to achieve less than 5ms latency.Sylvain