Note incorrectly shown on part
I have a score in which some notes are not the same on parts that what is displayed in the score. The score shows this:
The Alto 1 part shows this:
The problem is in measure 7, where the G on the Alto Sax part is one octave lower than in the score. This is not the only place where it happens. There is the same problem in measures 11, 23, 27, 47, and 51. Even worse, measures 14 to 20 are all one octave lower in the part than in the score, except for the last note of measure 20, which is correct! Strangely, the playback is correct, even when played from the Alto Sax 1 part.
Changing the note in the Alto sax 1 part (rising the G by one octave) makes it wrong in the score. Has anyone any idea of what is happening?
| Attachment | Size |
|---|---|
| Screenshot from 2022-05-10 12-10-31.png | 30.7 KB |
| Screenshot from 2022-05-10 12-10-57.png | 69.11 KB |
| 458_Meditation_Florence.mscz | 209.27 KB |
Comments
Your Alto Sax 1 part, amongst other things, lost its transpositioning, best to delete and regenerate that part, it seems corrupt.
In reply to Your Alto Sax 1 part lost… by Jojo-Schmitz
Sure, it is best to recreate the part. Adding a new Alto Sax part and copying the content from the old one in the score view is OK. The problem is that I don't know for how long it will last before being corrupted again. By the way, most of my scores have this kind of problem at some point.
This said, I don't think it has lost its transpositioning. As I said, the playback is OK, even from the part page. Furthermore, no notes are really untransposed. Some of the notes have shifted one octave, but besides this, they still are the correct transposed notes.
In reply to Sure, it is best to recreate… by Pierre-Yves Saumont
No need to copy at all. Just use File > Part to remove and regenerate it
In reply to Sure, it is best to recreate… by Pierre-Yves Saumont
And if you check the staff/part properties on the pat and compare with this on the main score, you'll see the lost transposition settings
In reply to And if you check the staff… by Jojo-Schmitz
Thanks!
In reply to And if you check the staff… by Jojo-Schmitz
Something is indeed wrong with the transposition of that part. While in the part, if you hit the Concert Pitch button, the only change key-wise that I see is at bar 54 where you have an instrument change to alto sax. Change from alto sax to alto sax?
That in itself doesn't explain the octave notation jump. Yet it could point to something in the way you deal with input methods in general.
In reply to Something is indeed wrong… by bobjp
If the transposition oddness occurs at or after an instrument change is it perhaps an example of #320828: Change Instrument Palette Text does not recognise current instrument leading to incorrect transpositions?
In reply to If the transposition oddness… by SteveBlower
Yes, it seems very similar. Thanks for the link.
In reply to Something is indeed wrong… by bobjp
The score is copied from a paper version in witch the alto sax 1 part starts originally with a flute, then switch to alto sax. It is then transposed to alto sax only (because we have no flute!) by changing the instrument for the staff to alto sax. Of course, the later switch to alto sax might then be removed, but still, switching from alto sax to alto sax shouldn’t cause such problem. The reason to not delete it is that we might found a sax player playing the flute later and want to switch back. I have change the process now, keeping two separate staves, one being hidden, but still generating both parts (with and without flute)
In reply to The score is copied from a… by Pierre-Yves Saumont
It should work to switch transpositions, and normally it does. I think we've already seen that in at least one case with one of your scores, something about the specific process you went through in attempting to set this up caused a corruption of some kind. This could be another side effect of that same issue, or a related issue. As always, steps to reproduce this corruption from an uncorrupted score would be needed in order to investigate. And best to also check with a recent build of MuseScore 4 to see if the problem is already fixed.
In reply to It should work to switch… by Marc Sabatella
Although it happened to many of my scores, I couldn't find a simple way to reproduce it systematically!