Fixing a wrong transpose

• Oct 17, 2024 - 00:31

I got a job fixing a transpose someone did wrong. The score SOUNDED right, but they had the wrong key signature to start with, and naturally a lot of enharmonic misspellings that made the score hell to read accidental-wise, and a large number of the intervals were really wonky. Now that I FIXED it, it suddenly strikes me that there might be some short cut or some kind of AI that can just do this, because that was not fun to change almost every G# to what it should have been (Ab in the key of Eb) Is there?


Comments

Often, you can change sharps to flats just by using [UpArrow][DownArrow].

Posting the score (or a portion of it) before changes and stating what you want to happen might help people understand more.

In reply to by underquark

Thanks! That's what I ended up doing but I still had to sniff out each error and do the notes one at a time. The client wished to transpose a score up 1/2 step from F. That would be either Gb or F# of course but they somehow managed to end up with only 3 flats in the transpose no idea what they did. The score came to me with all the correct pitches and numerous enharmonic errors. It wasn't just the double flats. I explained that you often get double flats in Gb.... I'll try the plugin in 3.7 next time...

In reply to by elsewhere

thanks, too late for this time pressure gig but I'll get it for if she ever does that again. and well she might. And good to know there is a MuseScore 3.7 that reads 4.x files because some of my clients like to muck around and screw things up then hire me to fix everything and they mostly prefer vsn 3 whatever.

Do you still have an unanswered question? Please log in first to post your question.