Topic by concorde

  • Avatar
  • concorde
  • Member
  • Offline
  • Registered: 13-09-2021
  • Posts: 27

Topic: MIDI - Missing Notes And Stuck Notes

I have an 88 key Technics SX-PR110 (an old keyboard). I just bought a "Miditech Midilink Mini" driverless, class compliant USB to MIDI interface cable. I connected it to the Technics and my PC via one of the USB 2.0 ports.

In both Pianoteq (Trial) and another software (Reaper) when I record a short part from a song with the software from the Technics, there are notes missing and there seem to be notes that are stuck on. I have a high spec computer so that is not the issue. This is on Windows 10.

The notes missing are not the disabled keys for the Trial of Pianoteq, I can assure you.

I tested the cable connected to the keyboard with the "Pocket Midi" application. It seems to output keys fine. It outputs a 0x90 signal with the velocity for a given key, and instead of outputting 0x80 for key off, it outputs another 0x90 with ZERO velocity when I release a key.

It also outputs an FE signal regularly, about once every 300 ms, which I suppose is a timing signal.

I find it odd that two separate softwares both have this issue with MIDI. It seems the MIDI is not being interpreted correctly by the softwares.

I've tried all the Dialect options in Pianoteq. I'm using ASIO for output. Multicore rendering and CPU Overload detection are both ON (default). Maximum polyphony is set to 48. Everything is at default settings.

Any advice on how to get this working is appreciated!

Reply by Defenz0r

  • Avatar
  • Defenz0r
  • Member
  • Offline
  • Registered: 11-06-2019
  • Posts: 88

Re: MIDI - Missing Notes And Stuck Notes

concorde wrote:

I have an 88 key Technics SX-PR110 (an old keyboard). I just bought a "Miditech Midilink Mini" driverless, class compliant USB to MIDI interface cable. I connected it to the Technics and my PC via one of the USB 2.0 ports.

In both Pianoteq (Trial) and another software (Reaper) when I record a short part from a song with the software from the Technics, there are notes missing and there seem to be notes that are stuck on. I have a high spec computer so that is not the issue. This is on Windows 10.

The notes missing are not the disabled keys for the Trial of Pianoteq, I can assure you.

I tested the cable connected to the keyboard with the "Pocket Midi" application. It seems to output keys fine. It outputs a 0x90 signal with the velocity for a given key, and instead of outputting 0x80 for key off, it outputs another 0x90 with ZERO velocity when I release a key.

It also outputs an FE signal regularly, about once every 300 ms, which I suppose is a timing signal.

I find it odd that two separate softwares both have this issue with MIDI. It seems the MIDI is not being interpreted correctly by the softwares.

I've tried all the Dialect options in Pianoteq. I'm using ASIO for output. Multicore rendering and CPU Overload detection are both ON (default). Maximum polyphony is set to 48. Everything is at default settings.

Any advice on how to get this working is appreciated!

It's the MIDI cable adaptor.
Don't buy such devices. Buy a solid appliance.

Two examples

e.g https://www.thomann.de/gb/steinberg_ur22_mk2.htm or https://www.thomann.de/gb/focusrite_sca...rd_gen.htm

Reply by Luc Henrion

  • Avatar
  • Luc Henrion
  • Member
  • Offline
  • Registered: 02-05-2007
  • Posts: 935

Re: MIDI - Missing Notes And Stuck Notes

The message "velocity at 0" instead of "note off" is indeed a sign that you have a vintage keyboard: some Roland pianos from the 90's also used this system. But this could lead to problems with current software/hardware, probably not missing notes but stuck notes yes.

Luc Henrion's Website

Reply by concorde

  • Avatar
  • concorde
  • Member
  • Offline
  • Registered: 13-09-2021
  • Posts: 27

Re: MIDI - Missing Notes And Stuck Notes

I monitored the MIDI messages with between 1-11 (all inclusive) keys pressed down at the same time then released. With the cable there were frequent missing messages (both key on and key on 0 velocity). So I thought it was the cable.

But then I tested the keyboard with an oscilloscope. It turns out some messages are not being sent from the keyboard itself.

So the keyboard is at fault here. I will either try to get it fixed or get a simple modern USB MIDI keyboard.

Last edited by concorde (13-09-2021 11:26)