Nord User Forum

Informed Nord about the following bug, No reply from Nord (as usual) not even a email confirmation. Nord does not give a ... about customer feedback.

http://www.nordkeyboards.com/software-t ... -2-manager

Windows 10 used here.

The Nord drum 2 only has MIDI DIN, if you use two identical MIDI USB Interfaces, the program cannot connect to the drum. (in this case two MIDISPORT 4x4's)
Verified this by removing one of the interfaces, and then it immediately worked. Now every time I need to up/download load a bank I need to unplug the other MIDI interface.

This is the nightmare of the proprietary program dump protocol path Nord has chosen for their products instead of just using plain Sysex by a MIDI utilities..
Sooner or later it breaks under changing hardware or software/OS and will never be fixed. but MIDIOX has the same problem. Only "MIDITools" and the Chrome MIDI API work correctly with multiple identical interfaces.

Thank you Nord, excellent strategy, service and job done.

Also note that two MIDISPORT MIDI interfaces on Windows 10 won't work with the MAUDIO provided drviers on their wesbite, only the Microsoft drivers work correctly (so uninstall any M-Audio drivers). with the MAUDIO drivers only one interface is detected by MIDI Win32 API. Once Microsoft drops the Win32 MIDI API for the UWP API (that may happen in the next years), All old Nord software (any many other applications) will become disfunctional. (or you need an old OS) to load/save drum banks.

BOTTOM LINE: NORD, PLEASE SUPPORT STANDARD SYSEX ON YOUR PRODUCTS ! BOTH FOR FIRMWARE AND PATCHES REPEAT.. REPEAT, REPEAT. (Like the NORD DRUM 1)
DSI CAN DO IT, WHY NOT YOU ?

32 years of MIDI and still manufacturers and programmers can't get it right.

Hi Happy,

-If I understand page 31 of the ND2 manual correctly, it is possible to up/download programs with sysex dumps. But it’s either one program, or the entire memory (all programs), not banks as with the manager application.

-Perhaps the Nord Drum Manager can’t distinguish between the 2 interfaces of the same brand and model. Not sure what is going on there, I doubt if it’s a bug in the Nord software per se. As you say, MIDI-OX also has a problem with that configuration.

-I don’t think there will ever be a new firmware version released for the ND2. So if you have a working interface, now is the time to update your ND2 to the latest, if you hadn’t already. With updates, Nord thus far has published installer software that is compatible with operating systems of that moment.

-The lack of proper drivers will make a MIDI interface dysfunctional, and although unfortunate, I bet that if that happens, there will be other USB-MIDI interfaces that will work properly on Win 10, or whatever Win version there is at that time.

Cheers,
Albert

Quite sure this is a bug in Nord ND2 manager (and in MIDIOX) unless proven otherwise. Two same interfaces is perhaps not something many people use and Nord likely has not tested such configuration. (where is QA nowadays...) Would be interested if any folks can try the same to confirm this problem. So far any other software works fine (incl. MIDITool from mountain software and Google Chrome WebMIDI API). PS ND2 Manager sends/receives individual banks, not individual programs or all the banks, but that is possible from manual using the buttons on the ND2. Understand the ND2 is old, but the ND3 is for performers and there must be lot of folks out there holding on to theri ND2 (as you almost can't find any 2nd hand anymore)m perhaps like me, don't like the integration of pads and the controls in one box.

Hi Happy,
On the M-Audio forum I read that Reaper and Sonar X3 behave the same way as MIDI-OX and the Drum 2 Manager. So at least 4 applications don’t like it when two M-Audio interfaces of the same type are connected, while other software seems to work fine with that setup. Perhaps different methods are used to recognize connected interfaces (?) You said that using the Windows driver in stead of the propriety M-Audio driver solved it, at least for MIDI-OX, http://community.m-audio.com/m-audio/to ... w-editions So I’m still wondering if this is a bug in the Nord Drum 2 Manager, or a bug in the M-Audio driver. Anyway, I guess in theory it should be possible to let the Drum 2 Manager work with your setup, not sure if Clavia will update the software for this. Although less ideal, there is a work around. Even without the Manager you can still transfer programs to and from the ND2 with SysEx dumps. Sure, one day even that will no longer be possible, but your ND2 will probably still be alive, and you can still fully program and play it.
Albert