changing key signature without changing notes' signature
Hi all, and ..
Merry Xmas and Happy New Year to you all !!!
My score converter sometimes doesn't recognize (can you imagine?) when the key signature changes and it stays unchanged for many bars.
Today when I apply the correct key signature, MuS automatically updates the target notes.
Is there a way to tell MuS not to do that?
Thanks,
Comments
No, applying/changing a key signature does not change any existing notes. Only transposing does.
In reply to No, applying/changing a key… by Jojo-Schmitz
Well, that's not what I'm experiencing.
Please have a look at the two images, before and after I have applied the new key signature at bar 100.
In reply to Well, that's not what I'm… by Trottolina
Not a single pitch changed.
Somo notes got naturals, but they didn't change pitch, without those naturals they would have though. So you really want them to, so need to transpose.
In reply to Not a single pitch changed… by Jojo-Schmitz
Sorry, perhaps I expressed myself in an ambiguous way.
I want their graphic look not to change.
So, for instance, the first note at bar 100 was a natural G.
After it should become a sharp G, which implies that graphically nothing has changed.
In reply to Sorry, perhaps I expressed… by Trottolina
So you want to transpose. So just do it. Select range, Tools > Transpose
In reply to So you want to transpose. by Jojo-Schmitz
..and what is the correct amount to transpose for ?
In reply to ..and what is the correct… by Trottolina
Wrong question, what is the key to transpose to is the right one
In reply to Wrong question, what is the… by Jojo-Schmitz
Should I transpose before or after I change the key signature?
In reply to Should I transpose before or… by Trottolina
Should not matter
In reply to So you want to transpose. by Jojo-Schmitz
"My score converter sometimes doesn't recognize when the key signature changes and it stays unchanged for many bars"
So are you talking about OMR (optical music recognition)? If a change of key signature is missed during OMR, that needs to be corrected within the OMR software's own editor before exporting the notes as MusicXML.
The earlier passage - bars 96-99 - already has a key signature of one sharp (F#). If the missing key signature (four sharps) is not corrected at bar 100 before creating the MusicXML export, then some notes (in your case C, G, D) will be exported at the wrong pitch (i.e. as naturals). Other notes (A, B, E, F#) will be exported at the correct pitch. Unfortunately you then have a mixture of correct notes and wrong notes.
In reply to "My score converter… by DanielR
Indeed, actually it's the SmartScore64.
Unfortunately I discovered the issue once I past half my score, so going back before exporting to XML it requires me to abandon all the corrections I've done so far..
In reply to Indeed, actually it's the… by Trottolina
Don't abandon the corrections.
Keep the first half of the MuseScore file with all your corrections.
Scan the second half again, this time fixing the key signature change.
Combine the good half with the fixed half into one MuseScore file.
In reply to Sorry, perhaps I expressed… by Trottolina
Try using Alt+Shift+up (possibly followed by Alt+Shift+down) after selecting the range to apply this to. It'll transpose diatonically (within the key signature): https://musescore.org/en/handbook/3/transposition.
Another way is to right-click one such a note within the selection and select->more->same-pitch and then up/down arrow them.