BUG: with nektar SE61, transport buttons activate mapped action on press AND release

• Jun 10, 2024 - 01:37

on Windows 11, MuseScore 4.3.1.241490900
ACTUAL:
1. factory reset nektar SE61
2. setup buttons for "Transp." mode (Setup, Transp., Enter)
3. setup Play/Stop for transport mode (press Play and Back together)
3. in Musecore, click Edit, Preferences, I/O; select SE61 as input and output
4. select MIDI mappings, Play, Assign MIDI mapping...
5. on SE61, hit Play button (CC 106)
6. on MuseScore, hit Add, then OK
7. press (and release) the Play button - MuseScore quickly starts and stops playback
8. press (and hold) the Play button -- MuseScore begins playback
9. release the Play button -- MuseScore stops playback

EXPECTED:
Press (and release) starts playback, Press (and release) again stops playback.

Perhaps there needs to be a checkbox to change this behavior, or a value filter (i.e. CC 106, Value = 0)

Comments

Burton Rodman

• Jun 10, 2024 - 01:41

FWIW, mapping a MIDI note to the Play action works as expected... except it uses up a note that I'd rather have for... playing notes ;)

Burton Rodman

• Jun 10, 2024 - 02:34

===> MIDI-OX Version: 7.0.2.372
===> Log Opened: Sun 09-Jun-2024 21:33:12 ===>
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
0006453E 1 1 BF 6A 7F 16 --- Control Change [PLAY]
00064541 1 1 BF 6A 00 16 --- Control Change
00064998 1 1 BF 6B 7F 16 --- Control Change [RECORD]
0006499A 1 1 BF 6B 00 16 --- Control Change
00064D73 1 1 BF 67 7F 16 --- Control Change [BACK]
00064D7A 1 1 BF 67 00 16 --- Control Change
00065274 1 1 BF 68 7F 16 --- Control Change [FORWARD]
00065519 1 1 BF 68 00 16 --- Control Change
<=== MIDI-OX Log Closed: Sun 09-Jun-2024 21:33:28 <===