Nord User Forum

once the program has been memorized, the volumes of the synth piano organ sections are not memorized in the position during the deliveries, but they follow the position of the pedal at that moment.

That’s not a bug; that’s how the Stage works. (It was the same on the Stage 2.)

no in ns2 I save the program with the volumes I want with morph assign on the pedal and the next time I'm presented again as they were saved and not based on the position of the pedal that can 'be different

So you mean that on your NS2, if you save e.g. an organ with the pedal down when you recall it again while the pedal is up, then it still plays at full volume?

That is not how I would like my NS3 to work... I would surely want the programs to reflect the current position of the pedal/wheel, not how they were saved.

Electro owner here. On the Electro the gain setting is stored per program as you describe - is that what you mean? That's an important function for balancing patch to patch levels.

Edit after reread. Regarding morphing, I think the A1 behaves like you describe the S2. At moment of patch change, control pedal position is irrelevant. When you change pedal position, it then snaps to current pedal value.

Yes. Of course

I think it's more like a bug in NS2...

I often load a patch, the pedal or mod wheel is in eg the middle, when I turn it there's an uneven volume/morph/parameter change, because the S2 often (or always? I'm not sure) doesn't check what position the pedal / mod wheel is at the moment...

I always remind myself to reset the pedal and mod wheel to zero, because that's what I build my patches upon..

But what should the patch do? Initialise to the pedal position or the morph wheel position? No guarantee they are the same or at zero when the patch is chosen. In my case there are patches where I use the wheel for morphing (eg RH solo), and some where I use the pedal for morphing (eg pads). I'm often faced with that situation of unknown pedal/wheel position when I change to the patch. And how does the patch know whether I'm going to use the wheel or the pedal to morph it? I guess my instinct is to wiggle the relevant controller before I start playing. But I think it makes sense to initialise to the saved state, then only take the current wheel or pedal position when one of them is moved.

CountFosco wrote:But what should the patch do? Initialise to the pedal position or the morph wheel position?

On the NS3 (at least), you need to be explicit about morphing: You target either the wheel, pedal or (aftertouch) to whatever settings you want it to morph.

So are you talking about having programs where you select multiple controllers for the same parameter? For me, that would be a somewhat rare situation...

But in that case, it would be somewhat random what value would win, and jumps are difficult to avoid, since multiple controllers will rarely be at the same setting -- but it could be decided by e.g. aftertouch > pedal > wheel or some such rule. But there can easily be "noise" in the readings, so a controller (i.e. pedal) value may fluctuate slightly, and at any given random time cause a jump in the value...

Sorry, I have an A1, not a Stage, I thought they were similar. On the A1, there are two morph controllers. The first is "Wheel/Pedal". The second is "Velocity". I didn't realise the Stage separated Wheel and Pedal. My bad, butting out!