@squarpadmin I’m a little bit confused with these allegations that “the silent majority wants different things from the few vocal contributors” I think we ALL want the Pyramid’s workflow to be as simple and intuitive as possible.
Take the example of the note offset. displaying a note on the previous step with a 99% positive offset, is not more simple and intuitive, and displaying it on the closest step with the smallest possible offset is not more complex.
when someone asks you for the time, do you answer it’s 1:55 or 5 to 2:00? you use the later, because when you don’t need the precision, what’s important is that it’s nearly 2 o’clock. not the fact that 1 o’clock was almost an hour ago.
During the BETA process, I’m usually very careful to keep comment and suggestion to features that you’ve already decided to implement, and pointing out real-world use cases that you might have overlooked, or that your implementation makes necessarily complicated.
( ok sometimes I get excited about possibilities and about taking features to what I feel is a natural/logical conclusion, but again, I feel that my contribution is to explain use-cases as clearly and precisely as possible, and offering a potential solution, but I care less about the specific implementation because you often have better implementations, and we do not know the specific internal constraints that you have to work with. )
ignore BPM on load being an override rather than a global preference. The reason I suggested that is because you can’t know in advance if you’ll need to ignore the BPM or not. it completely depends. This is also an advance feature that only benefits the subset of people using the Pyramid in a Live environment. so claiming it that it’s this way because its best for the silent users doesn’t really hold.
separate clock from transport control having the Pyramid behave differently when receiving a MIDI clock and a CV clock is confusing, and note “more simple”
use the same workflow/shortcuts to copy/paste/delete/move items on the pads again this is a suggestion to make the Pyramid simpler to use. You learn one thing, and you know that you can apply that thing to everything that is displayed on the pads: notes, cc, patterns, tracks, sequences. Right now for example, you can’t slide CC events the way you can slide notes. Also can’t copy sequences. ( sometimes I want to copy sequence A to sequence B so I can edit A. currently if I don’t edit B it disapears )
those are the little things that make the Pyramid OS a little bit harder to use, and I can claim that they would help the silent majority that want things to be simple just as easily as you can.