BBMO altering note lengths after Measure 72

BBMO version 2.04 (Merry Christmas to us, not), seems to think the midi file linked above is only 72 measures long, not 97. From measure 72 forward, when the file is imported, is changes all note lengths to 1/16 note. The problem occurred on Mac Sequoia when running BBMO on both the Edge and Vivaldi browsers. Version 2.03 had no such problem.

File is attached should anyone want to try to replicate the behavior. Song is Why Me by Kris Kristofferson, using the custom Kris Why Me drum kit also attached. File was set of as an OPB with the Why Me OPBk as the intro, adn the Nil at 35 as the Main.

Confirmation would be appreciated, as woulda rollback to 2.03 which worked as expected.

1 Like

I can replicate the reported symptoms. When I imported it though, all the notes in the song were 1/16 length.

I had slightly different results today, causing me to believe the problem may be related to the time signature when it is set to a meter other than 4/4. The song I worked on today imported properly except for the last measure, which contained only my velocity 1 null note. This song should have been 112 measures of 4/4. BBMO imported it as 111 measures, and replaced the whole note in measure 112 with a 1/16 note. That was an easy fix.

FYI to everyone, setting the song length to 112 prior to import does not correct the problem. BBMO keeps changing the length to 111, and I then have to set it manually to 112, correct the note length in measure 112, and then export.

I think I’ve narrowed down the issue. Today I was working on a song with time signatures that changed from 4/4 to 2/4 for a measure and then. And, again, I experienced this odd importing behavior where measures after, in this case 71, were not imported properly. BBMO is acting as if it has some kind of check sum for total beats, and when the beats do not equal 4 times the number of measures, it screws up the import.

When I edited the song to remove the 2/4 changes and just left the song in 4/4 all the way through, it imported properly.

i have an idea for a future work around, but I’d rather they just fix the thing.

1 Like

Thank you for reporting this. I’ve forwarded it to the development team for troubleshooting.

Hi Daniel,

I am still seeing this issue with the current 2.0.5 version. A couple more details may help narrow the problem. Normally, when I build a one-press song, I start by placing a pre-made null midi in the main loop. These are all 4/4 files - I realized that today and thought that might be causing the problem. I then imported my 3/4 midi file containing the full song as the intro, and, yes, it still cut off notes after a number of bars. So, I thought, let’s make a null in 3/4 time, and import that first. I made a new song to try that, and BBMO would not accept the 3/4 null as a main loop.

I then made the song in BBM, and imported the final product into BBMO, and it worked flawlessly

Thanks for the efforts.

Phil

1 Like

Hi Phil

When you say “I then made the song in BBM, and imported…”, did you made it with a 3/4 null file as the main loop or the regular 4/4 null?

Luis

With the 3/4 null file. The 3/4 null file imported properly in BBM, and since the song was entirely in 3/4, it made more sense to use it than to force the 4/4 null into it.

Good to know.