Hi Gang,
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,
I donāt know if itās possible to add this but, this FEATURE Requests thread is the best place to ask ![]()
Hi Dan, Thanks for starting this thread. I was going to do it yesterday, but figured youād get round to it eventually. I wonāt have mine until Wednesday, so for the most part I will wait until I dig in. But just to make sure a couple of things donāt get lost ā¦
- Ability to have a fixed per voice pan position.
- A per synth voice spread modifier (I know there are ways to sort of achieve this now, just an actual voice allocation spread with a width and pan control would be nice)
- Noise as a modulation source
- 0 to 10v on CV IN/Out | CV scaling as a modifier
Thanks for all the info so far!
A discussion on GS brought up the issue of the 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 jmcecil, that one is already in there.
Choose S/H as an LFO wave shape, then set the LFOās VARIATION to 100%.
Hi jmcecil, be more specific:
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).
Iād like to ask for a sanity check - it may be just meā¦
A feature I requested on the Sub 37 and would like the option on the Moog One is ā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.
I recognize for some new people they would be confused by turning the knob and nothing immediately happens so it should be an option.
IIRC pass-through mode is already in there?
Iād love to have some lanes of sequencer āper voiceā (starting on each ānote onā) as an alternative to the sequencer āper synthā. A.K.A. the āgated sequencerā in DSI REV2 (p.46 of rev2 userās guide).
Thanks for starting these nice wish-threads.
Hi conradk,
These following options are already available on Moog One (and the Sub 37s):
KNOB MODE (ABSOLUTE, PASS THROUGH, RELATIVE)
Having hardware knobs on a programmable synthesizer means that once a new Preset is loaded, a knob will no longer reflect the current value of that parameter. Knob Mode determines how a knob should respond when it is tweaked.
ABSOLUTE
In this mode, the parameter value will immediately jump to match the current position of the hardware knob.
PASS THROUGH
In this mode, the parameter value will remain unchanged as the knob is turned, until the knob position matches the current value. So, in this case, the knob must pass through the current setting before it becomes active. From then on, the knob will function normally.
RELATIVE
In this mode, the value range is scaled so that the current value is matched to the actual knob position, and the remaining knob range equals the distance from the saved value to the minimum or maximum extreme. The minimum and maximum values remain the same, and once the knob has been turned to the end of its physical range, it will function normally.
Hereās a link to the latest Moog One Owners Manual:
https://api.moogmusic.com/sites/default/files/2018-10/Moog_One_Manual_2.pdf
It will allow you to perform your own sanity checks:-)
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.
On the one hand, I think your hands would learn that you wiggle to get the screen, then you make the change. I agree that at first that would feel a bit broken. I actually think muscle memory would take over in this version of āauto-MOREā mode. The advantage to this approach is you donāt change the main value when what you want is a sub value. The disadvantage is when you are trying to access the main value of the knob.
In ādo it nowā mode, the knob should already be intrinsically tied to the main value, so Iām not sure itās that much of a problem to be doing the change while the screen is being loaded. Unless of course the only reason you twisted the knob was to get access to the scaling or some other sub value.
Unfortunately, I donāt have mine yet (two days to go) so I donāt know if I will find it a real problem or not. I was just echoing things from the GS thread about the MO. I actually donāt like the continual jumping on the DSI synths. A lot of times (if not nearly every time) Iām trying to tweak in relation to something else, and I donāt need to see the change to that other controller as I already know where āitā is. In the end I think either approach will work. And both approaches will be met by both āthank youāsā and āwhat were you thinkingā. ![]()
On Gearslutz there has been a couple of interesting ideas thrown around quite a bit.
One is about a table of known envelope slopes for classic synths. What Iād love to see is some preset envelope blocks for us to call up, in order to program with. Put the classics in (Minimoog, SEM/OB-X, Prophet, CS-80, Jupiter/Juno). Though I most interested in exploring the new āMoog Oneā sound, it would be great to have quick access when needed for some of those classic tones.
Another feature would be an easily accessible menu item for stereo voice pan/spread. That one has been mentioned a lot.
Thanks!
I know for instance, when Iām detuning OSC 2 and the More is on any of the other OSCs, Iād like the parameter to invert colors so it stands out and show the movement of the knob.. and as soon as it stops moving snap back to the Osc the More page is on. Would help with setting OSC offsets more quickly. Might work for the Filter sections and Envelopes too
More detailed control over velocity curves would be a serious improvement for those of us that are piano/keyboard players more than or in addition to programmers. It is hard to get some patches to articulate the way one might want, and have good control of a wide dynamic range.
Stereo spread by voice without jumping through hoops would be cool. At the very least, having access to voice number in the mod matrix, as opposed to key number, would allow panning by voice.
In conjunction with a transform like modulo 2 so that even or odd voice number could be a binary modifier, we could pan every other voice to one side or the other.
But really, a stereo spread parameter that behaves like DSIs would be nice.
I donāt know if this is physically possible, and I suspect that it is not - but post-mixer pre-filter is the best place to have an insert for me.
<<Edit: This only really makes sense for mono sounds, but that is what I want it for.>>
I would also like for The One to get my son up and off to school in the mornings, so that I could sleep in.
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.
Obviously this conclusion may be one of those things that looks great on a drawing board (or in this case chasing squirrels around my skull) .. Iād have to go hands on with the two options to see which seems the best compromise since we donāt have capacitive knobs.
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ā¦Obviously this conclusion may be one of those things that looks great on a drawing board (or in this case chasing squirrels around my skull).
Hi jmcecil,
I think about an Auto-MORE option every time I program One. But I keep getting stuck at the āwhat to do about messing up the initial parameter valueā problem. And, like you, my squirrels keep going back and forth about it.
I think, in the end, I would still like to have Auto-MORE as a feature, but definitely NOT as the default behavior. Hereās why:
On synths that donāt have a screen readout, grabbing an unused knob ALWAYS wrecks the preset value, and I donāt even think twice about it. So, until Iām ready to do uber-fine OCD types of program finessing, I think having the screen follow me around is far more convenient for those who grab knobs quickly and fearlessly.
On synths that donāt have a screen readout, grabbing an unused knob ALWAYS wrecks the preset value, and I donāt even think twice about it.
Exactly, I think I expect the value to get jacked up when doing that. I know this gets complicated by fixed rotation knobs and various takeover/relative modes. But, Iām still pretty sure I just want it to act like a knob and do its thing instead of having to give a wakeup the screen nudge. As I see it, as I wait for my box, is having to wiggle the knob is really not that much different than just clicking the more button on the way to the knob. Anyhow, I have 7 of 92 squirrels nodding yes .. thatās damn near unanimous between my ears.
This is a logistic request directly to you Dan. When you update the manual please put a version number and/or revision date prominently at the front of the document. Iām sure that is your intent but I have seen other manuals where it isnāt shown or is hidden somewhere in the back!
My only current manual suggestion would be a block diagram showing overall signal flow.
Looking forward to updates to the One and the manual!
This is a logistic request directly to you Dan. When you update the manual please put a version number and/or revision date prominently at the front of the document. Iām sure that is your intent but I have seen other manuals where it isnāt shown or is hidden somewhere in the back!
Hopefully, the Moog folk will see this request. I live 600 miles from Asheville, and have no say in how they do things:-)
Ah sorry. I guess they deal with the final format and updates. I assumed that you would be working on updates to the manual. Well we are on a Moog forum so hopefully they are reading these suggestions. There are some good ones! Like others I would like to see a new addition to VCA more menu that adds a pan spread control.
And great job on the manual Dan!