Those kind of bugs and foibles are the reason I developed the habit of constantly using SaveAs when working up a song in BB.

I usually use accession numbers appended to the filename:

Mysong.sgu

Mysong.mgu

Mysong1.mgu

Mysong2.mgu

Mysong3.mgu

etc.

Whenever I change something in the song layout, I try to do that SaveAs.

Not only does it yield a way to "revert" to the last known working file without having to start from scratch again if a file becomes corrupted for whatever reason, a freeze, crash, or just something going bump in the dark, it has become a large part of my workflow process, when a new idea comes along it is often better to go back to one of the previous versions to try implementing that.

Even with the new 99 Undos, I will probably continue that work habit, for these and other reasons.

Incidentally, I have noticed that there have been far fewer weird instances like that happening when working up a song since I stopped using Software MIDI Output solutions like the DXi stuff and went over to almost always using the hardware MIDI solution. Except when traveling with the laptop, where the VSC DXi is just easier to carry around and all.

I think that the newly released BiaB 2010 has solved quite a few of these problems. Likely we shall have new ones, though. Update releases are your friend, always check for them on the PGMusic Updates page for your version of BB and download and install them before starting a new song project. May prevent problems before they show up for you.


--Mac

PGmusic FAQs, Tutorials and Updates! click here

You must be Audiominds.
www.audiominds.com