One of the pioneers complained that the BPM setting is not saved with the patterns.
There a 2 conflicting usecases here.
- you made a pattern that sounds good on a specific BPM and you want to recall it the next time you use the pattern -> save BPM with pattern
- you are performing and the sequencer is running. Loading a new pattern should not change the tempo since this would break the flow of the playing song.
Possible solution 1:
- if sequencer is stopped -> load tempo from pattern preset
- if sequencer is running, keep the current tempo.
Solution 2:
- add a parameter to the settings menu to turn tempo load on/off
what would you prefer?
Comments
I'm in favor of saving separately :
drumsounds
drumsets (collection of drumsounds)
patterns (only the rythm no sounds and tempo)
multi (saves tho whole state of the machine, so drumsets with patterns and tempo)
This is kind of how it's done on the Ambika.
- Drumsound - a set of sounds for the 6 instruments
- Song - a set of 8 patterns.
single instrument and multi are planned for future updates.
Littel question though:
What would happen to the bpm for a pattern that was saved with say 100bpm. Then you load it with tempo_load=off while the tempo is at 120bpm. Then you make changes to the pattern and save it. Would the original tempo be overwritten?
Basically the question is: does the tempo_load equal tempo_save?
Not sure if this is really important because one can always save in another slot.
because when you save something, you want to save the state you hear, regardless of its previous state.
load tempo [on/off/auto]
and in the end the idea of a simple, little drumsynth evolves into something needing a 60 page manual
Do what you feel is right in the end, before you end up with 60 pages of manual
:-B
8-}