Double-click on drum palette produces wrong note when transposing instrument at top of score and concert pitch off

• Jun 29, 2019 - 18:55
Reported version
3.2
Priority
P0 - Critical
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project

1) Add the drum kit to the project

2) Press N and get in to notation mode

3) Double click the options shown in the tab (Clicking it once will play the correct sound but when double clicking one note, a different "note" is written down, for example when i hover over the first option, it says its an acoustic bass drum, click it once, it plays the acoustic bass drum, double click it and it inputs a low tom into the staff)

The only way i could get the correct "note" on the staff was to use the arrow keys to manually scroll through the options.


Comments

Status active needs info

In order to investigate, we'd need you to attach the score you are having trouble with, also be more specific about which instrument you are adding, also say if you are using the MDL extension. I can't reproduce a problem using the default empty score, adding a Drumset from the basic unpitch percussion, and double clicking the first icon - I got exactly the acoustic bass drum.

Title Drum notations not working properly Double-click on drum palette produces wrong note when transposing instrument at top of score and concert pitch off
Severity S4 - Minor S3 - Major
Status needs info active
Priority P1 - High

OK, I've figured out the problem and have changed the title accordingly. The problem happens if the top instrument in the score is transposing and concert pitch is off. In that case, double-click apparently tries to transpose the drum palette note for some reason. Other methods of note entry (keyboard shortcut, or click palette then click in score) are fine. Easy workaround for now if you want to sue double-click is turn off concert pitch while entering the drum part.

Priority P1 - High P0 - Critical

I'm raising the priority of this because with the new single-click model of palette interaction, this is easier to run into: now you see it on single click (double-click is no longer a thing). So I see it as connected to the larger design of single click in the drum palette.

As discussed on Telegram, I feel we need to step back and look at how single-click works in the drum palette, and possibly go back to the old model, or come up with an improvement - and soon. Fix for this issue may or may not depend on what we do about the design. But I'm guessing since the same bug existed for the old double-click model and the current single click model, the same code might apply and hence the same fix.