I suspect there might not be a solution to this problem, at least up to and including v2017.

Just a few minutes ago, I was reading though a melody created by the Melodist, some of which I plan to keep. There is one spot where the notation appears incorrectly, but the program won't let me correct it.

The tune is in A major, so three sharps in the key signature. There's one spot where the harmony has modulated to a D#min7 (D#, F#, A#, C#) and the melody is playing a Gb. Oh, but it gets worse. Next, within the same measure, it displays a G -- which according to musical notation rules, must be a Gb -- but it isn't. Now, where it gets frustrating is, when I tried to plug in the correct value, namely F# instead of Gb (Rt click, Edit note, then type in the note's name and octave number), instead of it showing a Gb in the little popup window, it shows an F# -- which is what is supposed to be displayed on the staff. I right click on the plain G, which please recall directly follows the Gb, and it is showing up in the display as a G#. Since a Gb is being shown in the notation, this G# must show the # symbol but it doesn't. It's as if the staff knows what's supposed to be there and knows the F# is in the Edit box, so it doesn't see any reason for showing the # symbol before the G. I just wish I knew why it decided that Gb should be used in a key signature with sharps, the first of which is F#. So anyway, it repeats this folly in the next measure as well. Now, all that is required to dispense with this erroneous display is for the F# to be shown, as it should, instead of the Gb. But instead BiaB just took a dump right there and fouled everything up.

If BiaB will not display F#, which is indicated in the Edit Note box, and which I also tried typing in, just for good measure, I am thinking that it might not be possible, and that this is a quirk -- aka "bug" -- that I'll have to deal with on occasion.

Have you ever run into anything like this before? I don't suppose you've found a workaround, have you?




Last edited by cooltouch; 01/06/18 08:45 PM.