BeatBuddy Manager Online BETA

Attention all BeatBuddy Manager Online (BBMO) users, we are going to start releasing new BBMO versions as betas before they are officially on the website!

Beta versions have been tested internally but may still have bugs. We strongly recommend using a new copy of your BeatBuddy project when using a beta version of the BBMO. Simply duplicate your project folder on your computer and name it something like “BETA BeatBuddy Project”.

Go to the latest beta here, the current version is 2.0.4 (as of 12/9/2025). As of 12/15/25, 2.0.4 is live on the BBMO official site, and is no longer beta!

EDIT 12/9/25: The BeatBuddy Manager 2.0.4 version has been released. Find the full changelog below. The BeatBuddy 2 content will only be editable using the BeatBuddy 2 Mode in the BBMO. BeatBuddy 1 content is still fully compatible with the BBMO, you will just be using BeatBuddy 1 Mode. The BBMO will automatically register whether your content is in BB1 or BB2 mode when the project is loaded. Any BeatBuddy 1 Project can be converted into BeatBuddy 2 Mode.

To convert your project to BeatBuddy 2 mode:

  1. First, open your existing BeatBuddy project on the BeatBuddy Manager Online
  2. Then, hit the gear icon in the top of the screen, choose BeatBuddy 1 Mode - Convert to BB2
  3. The application will ask you to choose a location to save a backup of your current project for safekeeping, choose a location
  4. All set, welcome to BeatBuddy Manager Online v2.0!

The Project in your BeatBuddy 2 SD card does not have to be converted, it will open it as a BeatBuddy 2 project as long as you are using BBMO version 2.0.0 or later

There are various fixes and general improvements for all BeatBuddy product users, and we will continue to refine the BBMO for all users.

An updated BeatBuddy Manager Online Manual will be available soon!

As of BBMO v1.5.6, you should only use the BeatBuddy 1 on v4.1.7 or later or any BeatBuddy 2 Firmware

Explanation of changes to BBMO since 1.5.6:

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.

How to fix issues with content:

  1. The BeatBuddy must be on v.4.1.7 for the content to work correctly.

  2. Duplicate a saved backup copy of your content (as made on the BeatBuddy Manager). Call it something like “BETA BeatBuddy Project”.

    • If you have already loaded your content onto the BeatBuddy Manager Online, these small snippets have been cut off and/or caused silent playback on some files. You will need to start with a fresh file.
    • If you have used the BBMO v1.5.5 to load content, it will have incorrect start points for many files, and that project can be discarded.
  3. Go to BBMO Beta website

  4. Click Load Project button and open your “BETA BeatBuddy Project” folder file

  5. Make any minor change like renaming a folder or file or even your entire project

  6. Hit Save

  7. The issues will no longer be present on the BeatBuddy in playback when written to the SD card.

    • If you already had content loaded by BBMO v1.5.5 on your BeatBuddy, just Delete the SONGS folder inside your SD card using your computer. Syncing the project from the BBMO again will create the missing SONGS folder with the updated content

Find out more about the official BeatBuddy Manager Online here:

Please reserve this thread for questions about the beta process and any beta-relevant information, issues should be reported in the BeatBuddy Manager Online help and questions category, please make sure to use the full version name when reporting. The version number can be found in the footer of the BBMO site.

If you need more information on making a bug report, read more here:

Beta Changelogs

2.0.4 (12/9/25)

  • Added a 3rd party cookies pop-up

2.0.3 (11/25/25)

  • Fixed issue with Default Drum Set dropdown list showing as transparent in light more

2.0.2 (11/21/25)

  • Brought back the Bar Count field in the MIDI Editor for fill files
  • Fixed the error pop-up on entering the project
  • Fixed issues scrolling in the MIDI editor
  • Fixed issues importing files in various non-4/4 time signatures
  • Fixed playback starting in the wrong place if you click on the grid to place a start point for playback in the MIDI editor window
  • Fixed issues with deleting the currently open drum or drum folder
  • Fixed an issue with the virtual BeatBuddy where the last part’s transition would not wait until the end of the measure to complete the transition during playback on the BBMO
  • Fixed the issue in the virtual player where the transition would loop indefinitely
  • Fixed the issues caused by importing specific songs
  • Fixed the issue when adding several blank velocity layers, which corrupted the drum set
  • Fixed playlist numbering when some are deleted and added on the BeatBuddy 1 or 2 (only ever have playlists 1-17)
  • Fixed error reporting in drum set - now shows all errors instead of just the first error in the list
  • Required a double click for editing the project name
  • Allowed nested folders in the song editor’s drum set dropdown to support Drum Folders
  • Set fill choke delay to be set to 1/8 note by default when adding an instrument to a choke fill group for the first time
  • We now display the official icon next to official Singular Sound drum sets, these drum sets are designated internally and cannot be set by customers or third parties
  • Implemented a new start page design
  • Implemented a unified login system, login via your singularsound.com account
  • Made the selection box range’s outline in the MIDI editor more easily visible in dark mode
  • Allowed symbols (such as !#@&$><~*^%±().':;/) in the text fields on bbmo (such as song name, folder name, playlist name, drum set name, etc)
  • Allowed symbols common in other languages (e.g. áéíóú, ñ, ü, etc)
  • Fixed an issue where a note would choke itself in the virtual player
  • Fixed crash on BBMO when certain bad files are imported
  • Increased logging in case of errors
  • Fixed an issue where MIDI notes would disappear after moving them in certain cases
  • Fixed issues with searching for a song and moving it within the filtered search results
  • Fixed an issue with new blank songs where the tempo would reset to the default 120bpm if you first changed the tempo, then created/imported a MIDI file in an empty slot
  • Fixed an issue where a part with no transition file would visually display a transition on the virtual BeatBuddy before each fill in autopilot in the BBMO

2.0.1 (9/30/25)

  • Fixed issues where the HD label would not show for HD drums and improved compatibility with BeatBuddy 2

2.0.0 (9/25/25)

  • Implemented BeatBuddy 1 and BeatBuddy 2 project modes
  • Added conversion feature to convert BeatBuddy 1 projects to BeatBuddy 2 projects
  • Implemented Autopilot (in BeatBuddy 2 mode)
  • Added support for HD drum sets (in BeatBuddy 2 mode)
    • Allowed 32 samples per instrument in HD drumsets (.DRMX), non-HD drum sets (.DRM) are limited to 16 samples per instrument
  • Made improvements to the error message in the project footer
  • Made the purple playback point reset to the beginning when the track is stopped using the MIDI editor’s Stop button
  • Implemented drum folders (in BeatBuddy 2 mode, for organizing drums into folders on BeatBuddy 2)
  • Created and added support for Drum Set Folder files (.PBDF). These files can be imported to import a drum set folder the drum sets inside the folder.
  • Improved cleaning of unused files on save
  • Improved UI and MIDI editor scrolling experience
  • Made speed improvements on saving the project, exporting, and converting
  • Limited fills to being one bar only. For a multiple-bar fill, use multiple single-bar fills in a row
  • Improved conflicts between the browsers undo/redo functionality, and BBMO’s undo/redo functionality
  • Changed default choke fill delay from 1/4 to 1/8 (more commonly used)
  • Updated terms of service and now requires ‘Agree’ checkbox to be ticked before using BBMO
  • Allowed duplicating a drum set with empty instruments, to more easily make multiple drum sets from an empty template. Note, you cannot save a project if an instrument is empty
    • Before, the instruments without samples would get deleted when you copied a drum set.
    • Now you can set up all the instruments, then make copies to have different drum sets using different samples, without having to re-add all the empty instruments again

Bug Fixes

  • Fixed freeze when importing a corrupted song
  • Fixed an issue where songs could have more than 32 parts, which is the maximum number of song parts
  • Fixed bug where you could rename a song from the playlists screen
  • Fixed an issue where the MIDI editor would appear blank and be scrolled out of view
  • Fixed issue where drums would not show on the BeatBuddy 1 or 2 in the order they were saved in the BBMO
  • Fixed issues with the three-dot pop-up menus
  • Fixed errors when importing samples (only 16 samples per instrument are allowed in for a regular drum set (.drm), 32 samples in total for HD)
  • Fixed bug where you could bypass the sample limit by dragging and dropping multiple at once
  • Fixed bug where exporting a song with a new name would also rename it in the project
  • Fixed the MIDI editor incorrectly folding when adding the first note to a track of a newly created blank MIDI file
  • Fixed the issue where exporting a song folder with a newly edited name would cause a crash
  • Fixed the issue where changing the velocity of a group of MIDI notes would cause a divide by 0 error (for non-nerds, dividing by 0 is not possible, in math, this is considered “undefined”)
  • Fixed the issue where the screen kept scrolling if you deleted the currently open MIDI file
  • Fixed alignment of the beat grid in triplet subdivisions
  • Disabled changing tempo while the song is playing since it caused too many edge cases and bugs
  • Fixed issues where copying/pasting midi notes would paste unintended MIDI notes
  • Fixed the issue where if a song was imported into a project without its intended default drum set, the default would be set. Now, the standard kit is automatically set as the default drum set in this case.
  • Fixed the issue where editing the project name to be shorter wouldn’t actually rename the project file
  • Fixed the issue where, when creating a new instrument in a drum set that already uses most of the possible General MIDI instruments, the instrument list wouldn’t adjust size
  • Fixed the issue where double-clicking to add a MIDI note in a blank space of the MIDI editor grid would occasionally not work
  • Removed the unnecessary number next to the choke fill delay setting (UI glitch)

1.5.6

  • Improvements and fixes to content made using the BeatBuddy Manager Legacy edition on the BeatBuddy Manager Online
    • Pre-existing projects will import song part files to start at the correct time if there is empty space at the beginning of a measure, the MIDI File Start Point will set automatically
    • Short partial measures that used negative MIDI tick values in the BeatBuddy Manager legacy were being ignored by the BBMO in v1.5.4, and were being positioned incorrectly in v1.5.5, v1.5.6 is importing these files correctly
    • Songs playing back files silently on the BeatBuddy after editing and duplicating the file have been fixed
  • Filename management improvements
    • Exporting a BeatBuddy song with new name will not change the name of the song in your project
    • MIDI file imports will be named in your project using the name you see in your file explorer, not their original name when created by a/your DAW (if it was edited)
  • Playlist numbering issues fixed

1.5.5

  • Fixed issue with files in BeatBuddy playing back silently when edited in the BBMO and loaded on the BeatBuddy. This was caused by songs that had “negative ticks” in the BeatBuddy Manager Legacy that were then imported and edited in the BBMO. Reimport unaltered content with this version to fix the issue. Note that this will not fix any content that was corrupted originally.
  • Improved error logging capabilities
  • Added a cancel button to build an accent pop-up dialog
  • Fixed velocity dynamic range values incorrectly overlapping in drum editor
  • Fixed MIDI file exporting so it doesn’t also rename the MIDI file in the BBMO on export
  • Fixed renaming for folders and drumsets
  • Added feature to remove empty measures at the start of an imported MIDI file. This is particularly useful if you use Logic Pro to create your MIDI files.
  • Changed alphabetization feature to ignore “an”, “the”, and “a” when sorting drums or songs
  • Fixed issues with resizing MIDI notes, leaving the song, and loading it again
  • Fixed MIDI editor grid numbering, sizing, and shading for triplet divisions
  • Added a check that each song has a main beat in existing parts before allowing saving
  • Made velocity inputs safer, reset velocity if a number isn’t entered
  • Fixes to UI, spelling, and spacing (mobile background got cut off, and error message became two lines)
10 Likes

We’re cooking :tada::tada::tada::tada:

1 Like

:fireworks:

1 Like

Hi. Just wondering why my imported MIDI files don’t show the file name I gave them? Instead it shows as “New MIDI Track”. I’m running macOS 15.5 and Google Chrome 138.0.7204.101. 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.

Thanks Daniel. Issue addressed in this post: BBMO BUG: importing a MIDI file does not use the MIDI file name
…so I won’t pursue it any further here. Thanks.

New beta 1.5.6 has been posted!

2 Likes

Brennan—don’t know if you want any feedback on BBMO Beta v1.5.6 here but it’s technically working fine however it’s very laggy. I’ve tried quitting Google Chrome and opening BBMO Beta again but I get a popup like this over and over again. Does not happen with BBMO v1.5.4

Hey there, is there any sequence you are doing that causes this to happen? We are not seeing this on our end, it could be related to your internet connection

Let us know thanks for reporting

Opened Chrome and I clicked on “Delete browsing data”—what I should’ve done before posting here earlier! :roll_eyes:

Everything appears to be working beautifully now. Thanks Brennan—sorry for the false alarm.

1 Like

Glad to hear!

Sorry to be back again, but the last couple of days, still have the same laggy issues with the Beta version (v1.5.6). My internet connection is strong and fast; I tried “Delete browsing data” in Google Chrome several times; I’ve just updated Mac to macOS 15.6. But still BBMO Beta version is really slow (see screenshot I posted here earlier this week).

And when I go back to the current BBMO v1.5.4, everything’s perfect—quick, no lag, same version of Chrome (latest version), same internet connection. The only problem is the “New MIDI Track” naming when importing a file, which the Beta version has fixed. But I’m going to have to stick with v1.5.4 for now. Has nobody else had any similar issues with v1.5.6???

Can you provide any information of what kind of actions you see lagging? Even if it’s everything please list the actions you’re trying to do for us thanks!

I’m testing the beta BBMO using Vivaldi and am not running across any latency problems.

It would help to know which function you are trying to perform, e.g., Sync to SD Card, import a drum set or a .pbf, create a song, delete a song, etc. That way the developers should be able to replicate your conditions and look deeper into your symptoms.

As a general rule, I do not use Google Chrome unless I have to. My preference is for Safari however, for the BBMO, it’s the Chromium based browsers, Vivaldi, Arc and Dia.

Some things to check:

  • your anti-virus or firewall (Little Snitch) rules to see if there’s anything odd going on there.
  • is your project folder located on your computer, SD card or in iCloud? If on iCloud or on your SD card, copy your project folder to your computer and open it from your computer in the BBMO beta.

Hi Brennan and Persist.

  • Antivirus and firewall do not appear to be blocking anything.
  • Main project folder is on my computer—always has been.

Functions—all I’m doing is opening BBMO beta—opening my BB project—and clicking on a song title. First, second and third songs—no problem; usually the fourth song I click on and it takes between 22 and 28 seconds for the song to be highlighted. And this lag remains for all subsequent songs I choose. Similar issues if I choose to add/update a MIDI file. And again waiting for the green button “Save Project” to illuminate so I can save my project. So I’m not really doing anything crazy within BBMO.

However, I’ve installed Vivaldi (thanks Persist) and so far, the beta version seems to be running without any (maybe a tiny bit) lag. So I suppose the moral of the issue is don’t use Google Chrome?

Not at all what I’m saying. If you like Chrome, you should use it (after you get your latency issue sorted out). If you continue to use Vivaldi, you’ll probably find some minor annoyances in how it works with the BBMO.

Vivaldi performs exactly the same as Chrome—lots of latency. As I explained, I’m not doing anything unusual in BBMO beta—just clicking on song titles.

So if I’m the only person having such issues, it must be me and therefore I guess I’ll stick with BBMO v1.5.4—No latency—No issues (other than file naming when importing a MIDI).

Thank you Brennan and Persist. I only wanted to provide some feedback.

1 Like

If and when BBMO v1.5.6 goes live out of beta it will replace the v1.5.4 as the only version you’ll be able to access. Hopefully a solution is found for the problem either on their end or yours.

1 Like

Beta is live on https://bbmo.singularsound.com/

:tada:

3 Likes

Working beautifully. Thanks all SS folks. :+1:

1 Like