Originally Posted By: Mark Hayes
Originally Posted By: Cerio
Originally, mgu was for songs with melody (midi data on the melody track), and sgu was for some without melody.

In my opinion, this differentiation doesn't make any sense nowadays and it's actually confusing, since you can use the melody track to generate any kind of track, not only midi melodies.


Indeed. I particularly don't like being in the middle of editing an SGU file, causing the "melody" track to be generated, then being asked what I would like to name my new "untitled" file when I go to save it. Then, when I tell it the same name, I wind up with an SGU and an MGU to keep track of.

FYI, this is on a Mac.


Yes, I had exactly the same problem with prior BIAB versions, but now it seems to be fixed. In 2019, if you were working with an SGU file, then used the melody track to generate, for example, a RT, and clicked on "Save", the program incorrectly asked to save your file in MGU format, which was kinf of confusing

I've just made a quick test with 2022: the program seems to detect now that a RT is not a Melody, and only ask to save in MGU format if you record some MIDI notes to the Melody track.

Great!

Latest BIAB version, latest build.