I admit I have not completely understood what "letter offset" is good for. It seems that this is complicating things as E - F is a distance of one semitone, F - G is a distance of two semitones. The consequence is that transposing needs to be specified with two values like (-1 -2). Does that really work as intended for all chords in a song?
Assumption: we are in the world of "well-tempered" music where e.g. f# and gb are considered the same tone.
By now in any case I came across, one "distance" value specifies transposing (Finale, MuseScore, EasyABC, MobileSheets, ChordPro Reference Implementation). There's transposing "by key" or "by semitone". Both can be thought of being based on a closed circle with 12 positions like a clock. "by key" uses the circle of fifths. "by semitone" uses c c# d d# e f f# g g# a a# b (or its equivalent written with flats). Transposing goes the same number of steps to the left or to the right for every key or note. Both approaches lead to the same result.
Open question: shall the tone or key be written using flats or sharps.
There are conventions if flats or sharps shall be used. That's for better readybility. Music theory, music notation, personal preferences - these three might be slightly different. Keys and chords are seen as "flat" or "sharp" by most musicians, based on the main scale of the base tone. Ab is "flat", G# is "sharp". It is common to avoid mixing sharps and flat and it is common to write the bass tone of slash chords so that it matches the chord, e.g. A/C# is the normal way, A/Db is very unusual as A is a "sharp" chord a c# e, being the tonic of the key A with three sharps, the IV of key E with 4 sharps or the V of key D with 2 sharps.
There's a limitation of the current UI: the flat / sharp buttons allow specifying to use flats or sharps only for the whole song. This is sufficient for a lot of (most?) cases. I meet the limitations sometimes with songs in minor keys when I want to write down bass notes.
Example: a simple I IV V I in minor Am Dm E7 Am. I add a bass run Am/E Dm/F E7/G# Am/A
Transposing results are not nice (only) for certain keys:
Dm/A Gm/Bb A7/Db Dm/D should better be Dm/A Gm/Bb A7/C# Dm/D
Gm/D Cm/Eb D7/Gb Gm/G should better be Gm/D Cm/Eb D7/F# Gm/G
This is a constructed example, "Yesterday" by the Beatles as mentioned before is another one.
In my practical use songs where I need a destination key to which I cannot transpose nicely happen rarely. In these cases I would use a workaround: make a copy, transpose it in the text editor (supposed the reported issues are fixed) and edit manually what I want to be different.
Assumption: we are in the world of "well-tempered" music where e.g. f# and gb are considered the same tone.
By now in any case I came across, one "distance" value specifies transposing (Finale, MuseScore, EasyABC, MobileSheets, ChordPro Reference Implementation). There's transposing "by key" or "by semitone". Both can be thought of being based on a closed circle with 12 positions like a clock. "by key" uses the circle of fifths. "by semitone" uses c c# d d# e f f# g g# a a# b (or its equivalent written with flats). Transposing goes the same number of steps to the left or to the right for every key or note. Both approaches lead to the same result.
Open question: shall the tone or key be written using flats or sharps.
There are conventions if flats or sharps shall be used. That's for better readybility. Music theory, music notation, personal preferences - these three might be slightly different. Keys and chords are seen as "flat" or "sharp" by most musicians, based on the main scale of the base tone. Ab is "flat", G# is "sharp". It is common to avoid mixing sharps and flat and it is common to write the bass tone of slash chords so that it matches the chord, e.g. A/C# is the normal way, A/Db is very unusual as A is a "sharp" chord a c# e, being the tonic of the key A with three sharps, the IV of key E with 4 sharps or the V of key D with 2 sharps.
There's a limitation of the current UI: the flat / sharp buttons allow specifying to use flats or sharps only for the whole song. This is sufficient for a lot of (most?) cases. I meet the limitations sometimes with songs in minor keys when I want to write down bass notes.
Example: a simple I IV V I in minor Am Dm E7 Am. I add a bass run Am/E Dm/F E7/G# Am/A
Transposing results are not nice (only) for certain keys:
Dm/A Gm/Bb A7/Db Dm/D should better be Dm/A Gm/Bb A7/C# Dm/D
Gm/D Cm/Eb D7/Gb Gm/G should better be Gm/D Cm/Eb D7/F# Gm/G
This is a constructed example, "Yesterday" by the Beatles as mentioned before is another one.
In my practical use songs where I need a destination key to which I cannot transpose nicely happen rarely. In these cases I would use a workaround: make a copy, transpose it in the text editor (supposed the reported issues are fixed) and edit manually what I want to be different.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de