Indicator for loop length of recording
Opened this issue · 10 comments
@Disc0erg0sum I might start on this soon, didn't we have a graphical draft for what it should look like at some point?
That's a quick sketch for the record indicator for now.
Thanks for the sketch @Disc0erg0sum. There are a few things that are unclear in the context of the current implementation. Right now, it is possible to record several patterns (even in different channels) at once by pressing multiple buttons before starting to drag on the touchscreen. The problem with that is that they could have different loop lengths. Drawing multiple indicators with a different number of divisions will be confusing I think. The easy way out would be to allow just a single pattern to be recorded at a time. Any suggestions/ideas about how this should behave? Is recording the same motion into multiple patterns at once even a use-case?
Given the fact that we were planning a feature to copy from one pattern to another, I would argue that in order to keep it simple, we just allow recording a single pattern at once, which can then be copied afterwards if I need the same motion in different patterns. If we decide that recording into multiple patterns at once is something that we want, then we would have to come up with a different solution for the record indicator.
I think it could make sense to record the same pattern, if we would have a parameter to delay one somehow. So that could give an effect of run & hunt each other within a certain range "spread"
Delay is an interesting idea that we haven't thought about so far. Could be quite cool yeah, I'll create a separate issue for that. The question is, do we need to complicate the interface in order to be able to record them really in a single go, or would that usecase also be covered by
- record single pattern
- copy to second pattern
- delay
I think for the beginning a single pattern is perfectly fine.
I'll keep thinking about it, but for today I'm out. Good night. :)
We could also go for a compromise solution such as recording patterns simultaneously across channels is only allowed when they have the same loop length. That would need some kind of indication however, so that it's clear to the user why it is sometimes possible to simultaneously record and sometimes not. I also lean towards keeping it simple for the time being and just allowing a single pattern to be recorded.
I guess recording in a single go would be required, if you want to perform the similar pattern on different signals at a certain point of time, otherwise you would always need to wait and add up the different signals until you match them up. The ideal moment could be gone already then. For the first version I think copy/paste would be fine.
If you want to perform the effect live then there is no other way yes. Except if we had some "direct control mode" that doesn't even record a pattern but just overdubs the channel with live motion. This is something we should consider anyway, now that it comes up.