I have no power to make any of these feature requests real, but at least these requests will all be in the same place

Hi Petur,Petur wrote:What i am thinking is a click track that (for instance) a drummer can play after. Lets say you want to use an arpeggio or a sequence in a part of a song in a live situation.
Engaging an arpeggio or a sequence live in the middle of a track is pretty tricky when it comes to syncing the arp/seq tempo with the song.
I guess i can use one of the synths to program a sequenced click track on the sequencer and route it to one of the auxiliary outs (for the drummer). But i was hoping there was a dedicated feature for this so that an entire synth track wouldn't have to be sacrificed.
Another solution would of course be to use an external source for the tempo and the click track, and sync the Moog One to that. But that means extra hardware and complexity.
Hi jmcecil, that one is already in there.jmcecil wrote:3) Noise as a Modulation Source
Hi jmcecil, be more specific:jmcecil wrote:MORE button vs just getting focus when you move a knob.
Maybe we can have a mode like a "focus" mode that allows the more page to open up when a control is touched. Leaving it off is the current behavior of using the "MORE" button.
Hi conradk,conradk wrote:I would like the option on the Moog One of ‘parameter value pass through’ - a feature on my Moog Little Phatty which allows you to turn your control knob until you achieve the preset value and then the parameter changes. Otherwise you have to be very careful with your knobs when making live changes to preset parameters as the change between current and new can be extreme/jarring.
This is a great question. Obviously with endless encoders you just keep turning. It doesn't feel like the movement is disconnected from the change. Although it still is "squishy" on a DSI synth._DemonDan_ wrote:Hi jmcecil, be more specific:jmcecil wrote:MORE button vs just getting focus when you move a knob.
Maybe we can have a mode like a "focus" mode that allows the more page to open up when a control is touched. Leaving it off is the current behavior of using the "MORE" button.
In a feature request I've been calling Auto-MORE, what happens the first time you touch a knob in a section that's not on the screen? Do you mess up your current value as the screen jumps to that section? Or, does a knob that's currently not on the screen NOT react to your first knob twist? And then only react to that knob being twisted after the screen comes up?
My concern is that it will feel very broken if nothing happens the first time you move a knob (in a section not currently represented by the screen).
Ok, you forced me to think it through and my conclusion is that you should NOT treat the knob as just a different "more" button. It should continue to control the value in real time and you change the screen as quick as it can to catch up. The knob should NOT be disconnected from its main purpose and be repurposed as a "more" button._DemonDan_ wrote:My concern is that it will feel very broken if nothing happens the first time you move a knob (in a section not currently represented by the screen