04-14-2025, 08:55 PM (This post was last modified: 04-14-2025, 09:23 PM by itsme.)
Transposing works differently when it is applied on a displayed song and within the text editor:
transposing a displayed song transposes the displayed song, saves the transpose in the database and leaves the songfile source unchanged.
transposing within the text editor changes the source file as specified
This is the intended behaviour.
But: wheras transposing a displayed song works fine for lyrics & chords, ABC sections and ChordGrids, transposing in the text editor transposes lyrics & chords and ABC sections, ChordGrids remain unchanged.
I noticed a second issue here: when transposing within the text editor the "Default display localization" shall be ignored. As the name says it's only relevant for the display.
In my case "Default source localization" is "Default", "Default display localization" is "Scandinavian". MobileSheets transposes Bb to H, correct would be transposing to B.
When trying to transpose this file again MobileSheets would fail as "Default source localization" is still "Default" so H is not a valid chord.
05-03-2025, 08:39 AM (This post was last modified: 05-04-2025, 07:51 AM by itsme.)
Transposing in the text editor has some more issues that need to be discussed, even with lyrics&chords only.
When a song is opened in the text editor and "transpose" is applied, clicking "OK" in the transpose window already changes the chords in the text (even without closing the editor). But it seems that MobileSheets still assumes the original starting key.
Everytime the transpose window is re-opened and closed with OK another transposing action is applied but the starting key and the destination key that is shown in the transpose window is confusingly wrong.
In case the file contains a {key: directive the key specified there should also be changed according to the transpose action.
I've got fixes in place for all of this. I want to note that for ABC sections, I'm not going to mess with trying to transpose the actual note letters. It's too much of a mess and I don't want to get it wrong. So instead, I'm just writing in a special command (%%mstranspose <steps>) that will be removed when the file is parsed and replaced with the necessary %%transpose statement (taking into account any amount the song has been transposed outside the editor).
Yes, that is correct. I have all the new features pretty much wrapped up, and am just doing additional testing and following up on bug reports to make sure I capture all the fixes in the update.