NRPN value 0 is not sent correctly

Hi,

First of all; THANKS so much for making this plugin. I started looking into it today, and the possibilities are just endless. I just donated - I can't imagine all the work that must have gotten into making this.

I did find a bug that is quite important, though. It seems that NPRN value=0 is not being sent correctly, and that is an important value for a lot of on/off switches for obvious reasons.

This is how my synth is sending two twists of a knob, A) going from value 2 to 1, and B) going from value 1 to 0:

10:53:27.899	From Moog Sub 3 Control	1 Non-Registered Parameter MSB 3
10:53:27.912	From Moog Sub 3 Control	1 Non-Registered Parameter LSB 106
10:53:27.912	From Moog Sub 3 Control	1 Data Entry (coarse) 0
10:53:27.912	From Moog Sub 3 Control	1 Data Entry (fine) 0
10:53:31.585	From Moog Sub 3 Control	1 Non-Registered Parameter MSB 3
10:53:31.597	From Moog Sub 3 Control	1 Non-Registered Parameter LSB 106
10:53:31.597	From Moog Sub 3 Control	1 Data Entry (coarse) 0
10:53:31.597	From Moog Sub 3 Control	1 Data Entry (fine) 1

This is how MIDI on Streamdeck transmits the same thing;

10:52:26.217	From IAC Driver E Control	1	Non-Registered Parameter MSB 3
10:52:26.229	From IAC Driver E Control	1	Non-Registered Parameter LSB 106
10:52:26.229	From IAC Driver E Control	1	Data Entry (coarse) 0
10:52:26.229	From IAC Driver E Control	1	Data Entry (coarse)
10:52:26.229	From IAC Driver E Control	1	Data Entry (fine) 1
10:52:41.064	From IAC Driver E Control	1	Non-Registered Parameter MSB3
10:52:41.077	From IAC Driver E Control	1	Non-Registered Parameter LSB 106
10:52:41.077	From IAC Driver E Control	1	Data Entry (coarse) 0
10:52:41.077	From IAC Driver E Control	1	Data Entry (coarse) 0

For A (going from value 2 to 1) the Data entry (coarse) is being sent twice - which I don't think really matters on a practical level.

But more importantly for B (going from value 1 to 0), "the Data Entry (fine) 0" is left out, instead there's a "the Data Entry (coarse) 0" there, so a lot of knobs don't react the way they should.

Thanks,
Johannes

Thanks for the donation; much appreciated.

This is not a bug in the plugin, I'm afraid. I use a cross-platform midi driver that handles the low-level sending and receiving.

On Windows, the correct midi commands are sent. I see that you are using a Mac, and the problem is either in the Mac part of the midi driver I use or in the macOS midi driver (coreMIDI), which is known to cause problems because it alters some sent commands for some mysterious reason.

I'll see if I can dig deeper and find out where the problem is.

I verified that I could reproduce the problem on Mac but not Windows.

I have also determined that the problem is beyond my reach. I have sent a bug report to the developer of the midi driver.