NL4 Velocity Morph & Delay/Reverb Bug Report?
Posted: 12 Apr 2015, 18:46
Can anyone confirm this for me?
Velocity Morph is acting very odd via MIDI. I'll take this step by step to try and avoid confusion.
1) When LOCAL is on and using the NL4 by it's own keybed, velocity morph DOES accurately control assigned functions in the Delay/Reverb Section.
2) When LOCAL is either ON or OFF and controlling the NL4 from another MIDI source, velocity morph works with everything EXCEPT the Delay/Reverb Section in which there is zero response to settings.
3) When LOCAL is OFF and the NL4 keybed is being echoed through a MIDI sequencer (Sonar X3, Reaper 4, external hardware sequencers)... ALL velocity morph assignments work EXCEPT the Delay/Reverb Section in which there is zero response to settings.
So it short... the ONLY way the NL4 Velocity Morph is successfully affecting the Delay/Reverb section is with it's own keyboard and set to LOCAL.
I can see this being a major issue for NL4 rack owners but it's also adversely affecting a sequence I've been working on.
Anyway.. can anyone confirm this? I'm assuming this is a bug. Clavia can make some odd decisions sometimes but this just seems to inconsistent to be intentional.
Thanks for the feedback!
-C
Velocity Morph is acting very odd via MIDI. I'll take this step by step to try and avoid confusion.
1) When LOCAL is on and using the NL4 by it's own keybed, velocity morph DOES accurately control assigned functions in the Delay/Reverb Section.
2) When LOCAL is either ON or OFF and controlling the NL4 from another MIDI source, velocity morph works with everything EXCEPT the Delay/Reverb Section in which there is zero response to settings.
3) When LOCAL is OFF and the NL4 keybed is being echoed through a MIDI sequencer (Sonar X3, Reaper 4, external hardware sequencers)... ALL velocity morph assignments work EXCEPT the Delay/Reverb Section in which there is zero response to settings.
So it short... the ONLY way the NL4 Velocity Morph is successfully affecting the Delay/Reverb section is with it's own keyboard and set to LOCAL.
I can see this being a major issue for NL4 rack owners but it's also adversely affecting a sequence I've been working on.
Anyway.. can anyone confirm this? I'm assuming this is a bug. Clavia can make some odd decisions sometimes but this just seems to inconsistent to be intentional.
Thanks for the feedback!
-C