Midi Keyboard Mapping
I have been using MuseScore 3 with my NEKTAR Impact LX 61+ Midi Keyboard without any problems. I mapped all the buttons, Pads and Knobs to how I wanted them. This made the prosses of scoring considerably quicker. Since I have been using MuseScore 4, I am unable to use the my NEKTAR Impact LX 61+ Midi Keyboard to map the Buttons, Sliders, Pads or Knobs to how it was mapped in MuseScore 3. I am able to put notes onto the stave using the midi keyboard.
I have reset the NEKTAR Impact LX 61+ Midi Keyboard back to the factory Setting on more than one occasion. This has not helped in solving my problem, when I try to map the Buttons on my keyboard it registers as CC0 I then move to the next button and that also registers as CC0 as well. Then nether button dose anything.
Please Help Ian wasting a lot of time
Comments
I am experiencing the same problem with a Nektar Impact GX mini. Configuring and using the buttons on the keyboard works easily in Musescore 3.
In Musescore 4, I can configure the buttons, and they are correctly recognized as CC106, CC107 etc., but when I use them, Musescore reacts to both the button press and release event, so I can use the buttons only for things like choosing note duration, where it doesn't matter if two events are fired. When I assign e. g. "toggle rest" or "toggle duration dot", the rest or dot is activated on press and deactivated on release, resulting in a useless button.
There seems to be no way of configuring the buttons on the Nektar in a way that they only send one event. It would be very useful, if Musescore 4 ignored the button release event, like Musescore 3 obviously does.
In reply to I am experiencing the same… by pohli
I have same problem as pohli on Nektar LX49 on Musescore 4.4 Linux, and agree on change in MuseScore 4.
Also Midi mapping containing CC=6 register in mappings as CC=0, while other CC values work fine.