Uncaught N-API callback exception detected aka Bad MIDI Value error

[tobyhede]

Encountered this using the WebMIDI wrapper library.

Node keeps nagging me with a message saying:

(node:20096) [DEP0168] DeprecationWarning: Uncaught N-API callback exception detected, please run node with option --force-node-api-uncaught-exceptions-policy=trueto handle those exceptions properly.

When I use -force-node-api-uncaught-exceptions-policy=trueto I can see the exception details inside JZZ.

  RangeError: Bad MIDI value: 144,48,64

  at _throw (node_modules/jzz/javascript/JZZ.js:1635:30)
  at MIDI (node_modules/jzz/javascript/JZZ.js:1550:49)
  at Object.handle (node_modules/jzz/javascript/JZZ.js:832:25)
  at node_modules/jzz/javascript/JZZ.js:837:66

MIDI messages seem to be sent correctly.
The MIDI values in the error seem to correspond to the Note and Velocity being sent.

The errors appear to be triggered via a timeout, they are reported aftert the program has completed.
There are more errors than actual send events - like something is caught in a loop internally.

[jazz-soft]

Thank you for the notice.
That looks strange. I'd suspect there is an extra pair of "[]" braces somewhere.
Could you create a minimal code snippet to reproduce the error?

[tobyhede]

The code is a very basic note on/off setup via WebMidi

        channel.sendNoteOn('C3', {attack: 0.5} )
        channel.sendNoteOff('C3');

I have done some tracing, WebMidi is only calling the underlying JZZ.js library twice (once for on, once for off).

[jazz-soft]

I am running the following code and I don't see any errors:

const {WebMidi} = require('webmidi');

WebMidi
  .enable({sysex: true})
  .then(onEnabled)
  .catch(err => console.log(err));

function onEnabled() {
  let output = WebMidi.outputs[0];
  let channel = output.channels[1];
  console.log('sendNoteOn');
  channel.sendNoteOn("C3", {attack: 1});
  console.log('sendNoteOn done');
  setTimeout(() => {
    console.log('sendNoteOff');
    channel.sendNoteOff("C3");
    console.log('sendNoteOff done');
  }, 1000);
}

Windows 11 Home, Node v19.0.0, webmidi v3.1.4, jzz v1.5.9.
Is there anything I'm missing?

[tobyhede]

Thanks heaps for taking the time to look into this.

That works for me as well. but helps narrow it down.

My output is set to a LoopMidi port on Windows 11.
Error occurs on this output, but not the default.

I can see the LoopMidi port receive the event (via MidiView), and Reaper is playing the correct note.

[tobyhede]

I've been digging into this more but I can't find the issue.
It seems like there is a retry or retrigger of the original midi message, but paramaters are being pushed into an array.
Just can't trace it though.