BBMO BUG: importing a MIDI file does not use the MIDI file name

Tested on a Mac Mini M2 using Sonoma 14.6.2b. Symptoms can be replicated n both Arc (1.49.0) and Google Chrome (125.0.6422.113).

Also tested on a Mac Mini (intel) using Catalina 10.15. Symptoms can be replicated in Google Chrome.

EXPECTED BEHAVIOR:
That a MIDI file when imported to the BBMO will use the MIDI file name.

WHAT IS HAPPENING:
The song part takes on the name of the MIDI file region when exported from a DAW.

This brings up a related issue, Most of the Default Content 2.1 midi_sources files use Groove Agent SE 01 in the name of the DAW MIDI region (instead of the beats actual title.

2 Likes

Hi persist,

Thank you for sharing this information. We will look into it.

1 Like

I am having this same problem using a PC running Google Chrome. Additionally, the midi file name is not the only thing incorrect, different data is also input. I have a video I can share privately of what worked in BBM and is NOT working in BBMO. Gig Tonight, Songs are F* up. Will try to fix using original BBM and hope it works. If there is a fix, please advise ASAP! :slight_smile:

Hi Scottchacha,

We’re sorry to hear about the issues you’re facing. Please send the video and any relevant details to support@singularsound.com, and we’ll do our best to assist you as soon as possible. Thank you! :blush:

Hi. I’m having the same issue Persist reported in July 2024—imported MIDI file doesn’t show the actual name I gave it when it was created. Persist said his BBMO was reflecting the software he uses to create his MIDIs. Mine is simply showing in BBMO as “Untitled”. I’m using the latest macOS and latest Google Chrome browser. What is it that I might be doing wrong???

Regardless, the MIDI plays perfectly once loaded onto the SD card and plugged into my BB—so technically not a problem—but it’s a bit weird.

I’m late to the game because I’ve doggedly been using BBM, which I love and have no problems with! It shows all my MIDI file names correctly—been using this process/style for seven years. I was reluctant to switch to BBMO, but I want to try and make it work. Thanks.

If the issue persists, please try renaming the file in your DAW before exporting it. If the issue continues, kindly attach the files in an email to support@singularsound.com.

A workaround in the BBMO is to select the MIDI file you just imported and rename it by double-clicking “Untitled” and typing the new name. The other option is to rename the MIDI region in your DAW before exporting it but I find that to be slightly more difficult than renaming within the BBMO.

Daniel—I tried renaming the MIDI on export from my DAW and I also tried renaming the file post-export. Same result. And I’ve done this process a dozen times—always “New MIDI Track” is what appears in BBMO. I’ll email an example MIDI to support. Thank you.

Persist—Renaming the MIDI in BBMO is a good workaround—thanks. Although I was double-clicking the actual MIDI location and nothing happened—then I realized I should double-click the title above the “running/playing”(?) area and it worked great. Still a PITA compared to BBM but it worked. Cheers.

Issue has been fixed in the Beta version of BBMO. :+1:

1 Like