Out of range colors not working on "saved as" iterations
Works appropriately when I start a new composition, but not for the instruments (eight) on a score that I wrote earlier, and one I "saved as" to try new stuff on. The out of range option is turned on under Edit/Preferences. It's possible I may have exported it to an MusicXML file and then re-imported that as a trial, but I'm not sure. Thanks.
Comments
next to impossible to help without seeing the score
In reply to next to impossible to help by Jojo-Schmitz
Here's the score, with a couple of notes for the alto sax in the third and fourth measures out of range for demonstration purposes.
In reply to Here's the score, with a by Craig Wilson
could come from imported xml, it seems to me...
from scratch with 2.0.3
In reply to could come from imported xml, by Shoichi
Right. Certainly works properly if I start a new score. No way to turn on color markings in this score or others copied from it, I presume?
In reply to Right. Certainly works by Craig Wilson
if there is a way I have not found :(
In reply to Right. Certainly works by Craig Wilson
For this score, you should change the usable pitch of the instrument. Then, the out-of-range pitches will be marked.
Right now, your score shows G9 as the highest playable note. The note in the third measure is an A6, well within the range.
See:
https://musescore.org/en/handbook/staff-properties#common-staff-propert…
and look for 'Usable pitch range'.
Regards.
In reply to Right. Certainly works by Craig Wilson
Right, the problem isn't that the warnings have been turned off - no score can do that - it is that this staff has the wrong ranges assigned. I would have thought this would be set automatically when you import a MusicXML file, but apparently not. This seems like a bug to me - could you file this officially (using "Help / Report a Bug" from within MuseScore) and attach the actual MusicXML file you started from?
Anyhow, indeed, just set the ranges via Staff Properties and you should be good to go.
In reply to Right, the problem isn't that by Marc Sabatella
Yes, that fixed things. I wasn't aware that the instrument ranges weren't hard-wired. Maybe MusicXML doesn't save the staff ranges, or maybe the programmer decided it was more work than he wanted to do (or planned to do it later), but every instrument's usable range had shifted to the max - C-1 to G9 - in the translation back to MuseScore format - which wouldn't be an issue unless someone wanted to make changes in the score. I'll sure never do it again. Thanks for your help. I will report the bug.
In reply to Right, the problem isn't that by Marc Sabatella
MuseScore would have to know which instrument is intended in the MusicXML. That can be a hard guessing work since there is no definitive answer but just a bunch of hints (the instrument long name, short name, sound id, midi program etc...)
In reply to MuseScore would have to know by [DELETED] 5
But don't we already make a call on this for the purpose of assigning the instrument as shown in Staff Properties (thus setting the sound and transposition)?
In reply to But don't we already make a by Marc Sabatella
Issue here: #122996: Importing MusicXML does not assign instrument ranges from instruments.xml
In reply to Issue here: #122996: by Isaac Weiss
What if we could extend the midi note range both lower & higher? The Nelophone Family (basically 6 string Hexagonal Basses in different registers):https://www.youtube.com/watch?v=U-4xBp1mq9g&t=1s