Thanks for using OnSong!

We have recently corrected an issue involving F chords appearing as E# when applying capo to a song.  However some users are continuing to report the appearance of E# when viewing transposed songs that contain accidentals.

OnSong uses the enharmonic preference (sharpness or flatness) to determine the enharmonic preference of transposed chords.  For instance, the key of G is a sharp key containing an F#.  But if transposition results in an F chord required to be played, OnSong will output this as an E# to maintain the enharmonic preference of the key.  In music theory E# and F are basically the same but we believe we can do better.  We are making some updates to the transposition engine to only use E# in keys that contain a sharp in the written key signature such as C# major.

All that must theory aside, must issues can be resolved by declaring a key for your song.  For instance, your song may appear to be in the key of D and contain chords like D and A major.  But if the song has an accidental C chord, this could cause E# to appear when the song is transposed to the key of G.  The more proper key may be the Key of G which can contain the C chord.  Transposing then in the key of C will resolve the E# issue.

Let us know if you need any assistance in declaring the key of your song while we work to release OnSong 1.996.