Minimum track elasticity seems to be 50%. Any plans to change the minimum to 25%?
2 Likes
And on the other side, 400% would be welcome, too. It’s so nice that the BPM can go all the way down to 1. I’ve never understood why devices can’t simply enable low tempos because you’d think it’s a no-brainer firmware-wise. Same thought for elasticity: if it’s easy to implement, why not maximize the range? People with no need for wider ranges (like BPM = 1) would never be bothered by possibilities that don’t interest them. Win win.
1 Like
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.