Is there a technical reason why the sequencer does not go below 10 BPM?
At first I could not find a useful application (for my usage) for the sequencer, but then I though of using it for ambient soundscapes and backgrounds.
For that the minimum BPM must be far lower than 10. Is it possible to lower the lower limit to (lets say) 0.1 BPM?
The end of that video is silent due to rights issues.
@HansR the tempo cannot be zero so I had to choose a minimum value. I chose 10 bpm because it seemed much loser than most user’s needs. The maximum value of 480 bpm were also chosen to make some logical and musical sense. The range 10..480 is presented on a controller seemed managable from a UX point of view. I am not sure I want to reduce the minimum much further but it could be done. If you feel this has benefit, add a feature request to the issue tracker describing your use case.
I think a thing to consider is if all plugins (engines) relying on host tempo (delays, loopers) are prepared for such low tempos regarding for example static memory allocation for delay buffers or similar.
Maybe not all of them have some kind of fallback mechanism when maybe an unexpectedly slow tempo requests additional memory.
Most likely most delay line based plugins must define some kind of maximum length of the delay line.
Do keep in mind that in general low BPM’s are not such a good idea
Here’s why: a lot of Midi Hardware incorporates a timeout mechanism (in absence of incoming Midi Clock Bytes, they will switch to internal clock).
But the MIDI standard does not specify a minimum, so I guess it could be done.
You’d have to ask yourself the question if it really makes sense musically to do it though (imho - nope - but who am i ;)), as there’s plenty of ways to achieve slow progression with more usable BPM’s.