Notes displayed in wrong octave after change of transposition
I looked around and don't think this bug was similarly reported.
I have a score with one clarinet staff. I change the instrument from Clarinet to Alto saxophone. If we look at the notes in concert mode, all seem fine, but if we switch to normal mode (concert mode off), some of the notes are drawn one octave higher (but the sound is correct).
Steps to reproduce :
1. Open attached score
2. Right click on the Clarinet instrument to change the staff properties.
3. Change instrument to Alto saxophone and click OK
4. Toggle Concert mode to see some note shown really high on the staff
GIT commit: 3543170
| Attachment | Size |
|---|---|
| test-alto-concert-mode.mscz | 1.76 KB |
Comments
BTW, that's a really old build, and transposition has changed quite a bit since then. Scores for transposing instruments built in older builds are no longer likely to work. But this issue can be recreated from scratch as follows:
1) new score for clarinet, key of C, 4/4
2) make sure concert pitch is off
3) enter quarter notes A B C D
4) right click staff
5) change instrument to Alto Saxophone
Result: first two notes are an octave too high
It is also the case that the notes should probably have transposed but didn't - they still display as A B C D, even though concert pitch is off. This is already reported as #21744: Actual notes are changed if transposition properties are changed with Concert Pitch off.
Even if you turn concert pitch on before the instrument change, you still get the octave error.
1) new score for clarinet, C major, 4/4
2) enter A B C D
3) turn concert pitch off
4) staff properties, change instrument to alto sax
5) turn concert pitch back on
Result: first two notes display an octave too high.
Transposition is incorrect, too - notes are still A B C D as they were for clarinet.
Thanks for validating this issue.
Btw, I'm surprised with your comment about my "old build", I just rebased it and my local build should be up-to-date (following the workflow instructions ). Could simply the version number be wrong?
Could be. I just followed the link in your original problem report, and it took me to a commit message from July of last year.
See http://musescore.org/en/node/19884#comment-73409, have you installed that hook?
(I have now added that to the git workflow page)
The problem happens with other instruments too. But for the banjo (for example), it's a different note that gets screwed up. Might be related to the tonality of the instruments. C instruments all seems to get the sames notes wrong, but different than Eb instruments.
BTW, thanks Jojo-Schmitz for the hook information. I didn't have it installed. Now the revision number is fine.
I'm pretty sure the problem was introduced in the commit fixes for transposing instruments , but I find it rather hard to understand those pieces of code. With all those tcp, I'm a bit puzzled...
Hello,
![banjo erreur.jpg]( "banjo erreur.jpg")
For the banjo, I think this is due to an initial error in editing strings.
As you can see, the tune displayed by default in MuseScore is G5-D3-G3-B3-D4.
However, the G5 (the higher drone string) is false. This is a G4
![wiki accord banjo.jpg]( "wiki accord banjo.jpg")
So good series is G4-D3-G3-B3-D4.
Confirm this excerpt from an article by Wiki.
This seems to be anentirely unrelated and separate issue
f87cb01aa4
and the Banjo problem had been fixed in 10d1853
Not completely solved.
1- Open attached score (or from scratch, create a score for Bb trumpet, C major key and enter D E F G A B C D with Concert Pitch OFF);
2- Right-click on staff, staff properties, change instrument to flute.
(The key is not transposed, as Werner already said) The notes in the second measure are wrong and corrupted: if you click one an repeatedly press up (or down) key, the note continues to jump in different octaves.
Linux Mint 13, f87cb01 (self-built)
Fixed in 3bfb8d783e
...due to a silly typo only the first measure was processed...
Automatically closed -- issue fixed for 2 weeks with no activity.