Nord User Forum

I am having a very similar problem controlling my NS3 from an Alesis Vortex 2 keytar since updating to 1.52. I ended up reinstalling 1.42 and it works fine again. Definitely some kind of midi bug with this latest OS.

Yep, this is definitely a MIDI implementation bug (and it has been reported to Nord).

baekgaard wrote:Yep, this is definitely a MIDI implementation bug (and it has been reported to Nord).

The bug also seems to affect all incoming MIDI, not just in DualKB. I am able to reproduce the sustained notes using Global midi, Panel A/B, or DualKB.

Yes, it is not only related to Dual KB.

I'm using Yamaha moX6 to control NS3 via Midi. No Problems, but when I try to use my Novation Impulse, the problem comes right away. I'm going back to 1.50 because I need that swell pedal to work in dual kb mode.
This is ridiculous. I've been giging with nord stages over ten years, first NS1 then NS2 (which I still have) and never had any problems. Well NS2 had the same swell pedal bug first, but it didn't take more than couple of weeks Clavia to fix that. They even sent me a beta os for testing.

Hi, trying to help a friend which is experiencing this same issue (using a Novation Impulse or M-Audio Code), I suggested him to roll back to 1.46 but he received the NS3 already with that version so he doesn't have the 1.46 Updater and looks like manually changing the download link ( of 1.52) is not working any more!! ... help!!

(Note: my friend has a Mac so if anyone can share the 1.46 dmg it would be greatly appreciated!)

Was hoping there would be a fix for this velocity zero bug posted quickly.

But I have a temp fix for this as I have a regular Thursday night gig where I use my keytar with wireless midi going into my NS3. I have a BomeBox ( pretty handy little device by the way ). I created a midi translator project that intercepts note off messages and if the velocity is zero it changes it to 1. This seems to solve the issue until the fix is available.

Gospelkeys wrote:Was hoping there would be a fix for this velocity zero bug posted quickly.

But I have a temp fix for this as I have a regular Thursday night gig where I use my keytar with wireless midi going into my NS3. I have a BomeBox ( pretty handy little device by the way ). I created a midi translator project that intercepts note off messages and if the velocity is zero it changes it to 1. This seems to solve the issue until the fix is available.

Great fix and BomeBox looks to be something I could use for many reasons. Murphy’s law says the new update will be released during your gig on Thursday night!

maxpiano wrote:Hi, trying to help a friend which is experiencing this same issue (using a Novation Impulse or M-Audio Code), I suggested him to roll back to 1.46 but he received the NS3 already with that version so he doesn't have the 1.46 Updater and looks like manually changing the download link ( of 1.52) is not working any more!! ... help!!

(Note: my friend has a Mac so if anyone can share the 1.46 dmg it would be greatly appreciated!)

Hi, I have to check if I have still 1.46 for Mac available. But how is the legal situation when sharing th OS without Nord’s approval, does anyone know if this is allowed or if this is against Nord’s license terms?

Gospelkeys wrote:Was hoping there would be a fix for this velocity zero bug posted quickly.

But I have a temp fix for this as I have a regular Thursday night gig where I use my keytar with wireless midi going into my NS3. I have a BomeBox ( pretty handy little device by the way ). I created a midi translator project that intercepts note off messages and if the velocity is zero it changes it to 1. This seems to solve the issue until the fix is available.

PM me for more info.