I just want to chime in here that the fix does not “fix” corrupted files. The files before version 1.5.6 in BBMO were being corrupted and will continue to be corrupted. What you need to do is import a file that was never in contact with older versions of BBMO into the BBMO now, this will properly import the file and stop the issue from ever happening.
There likely is no bug here, most probably the problem is a corrupt file.
Read more here:
Explanation of changes to BBMO in 1.5.6 (still relevant in 2.0.0 or later):
The BeatBuddy Manager Legacy uses a proprietary feature that allows “negative ticks”.
MIDI Ticks are positions in the MIDI file. There are hundreds of ticks in every measure of a MIDI File. Using Negative Ticks on the BeatBuddy Manager allowed a user to have special partial measure behaviors on the BeatBuddy. However, the BBMO was built very differently. Now we have a MIDI File Start Point to set where playback should begin for files, and we don’t make use of negative ticks.
Read more about the MIDI File Start Point in the BeatBuddy Manager Online Manual
This necessary change to the BBMO required a change to how the BeatBuddy works, it will now regard files with a partial measure + a full measure as it always did when creating content using the BeatBuddy Manager Legacy.
As far as we know, this only affects content included in our default content, and most users did not make content using negative ticks. We strongly believe the BBMO’s MIDI File Start Point behavior is overall a great improvement for customers to make their own content easily and effectively.
Version 4.1.7 on the BeatBuddy regards the BBMO’s partial measures the same way that it regarded negative ticks before. This information is not relevant if you are using the BeatBuddy 2 default content on the BeatBuddy 2.