I renamed a drum set and got an error message saying: “error reading song:” SONG TITLE.
Even after moving the kit back to the original name and many, many other songs not using the renamed kit.
This error also is now seen in past projects that haven’t touched in months!! And, I just copy the SD card over to the computer and it happened there too.
The only other thing I did differently was resort the drum list by clicking the AZ button. Could that have done it?
Exact same issue here. I did not renamed any drum kits that I can recall. Have found at least two songs that generate the “error reading song” message in BBMO but that otherwise run fine in the BeatBuddy. Hopefully the team can track and solve the issue. BBMO 2.0.4 version
I just finished testing and I can validate what Bootsy is reporting.
The suspect songs work in the BBM and it would seem that exporting the songs from the BBM and then importing them into the BBMO, that they would open and play. That’s not the case, though.
Is there a way to rollback to a previous version of BBMO?
This is a HUGE downside of online vs desktop software. With the issues I am having with 2.0.4, I would have re-installed a previous software version until things get fixed. I was planning to do a LOT of work these days and now I am worried about the software messing up my project. So I am stuck, waiting….
(Of course this will not be an issue if the folks at Singular Sound roll out a quick fix for the issues– BBMO showing the wrong number of measures and songs that can’t open in BBMO but play just fine in the BeatBuddy, among other minor issues).
Fingers crossed for a quick fix or an alternative URL with a previous version.
More details on this error. If I create or edit a song in BBMO and, for any reason (like having no internet, or troubleshooting) I open my project in legacy BBM, BBM reports that the song has to be recovered and a copy was made. THEN, if I edit any other song in BBM and then open the project in BBMO, BBMO reports the “error reading song” and then I can’t do anything with the song in BBMO. At least in BBM the song opens and, even though BBM is a major pain to edit any MIDI details in the song, at least it reads the songs and play them.
I have already lost a weekend’s worth of work done for my BB pedal because I am very afraid of these errors reported and being unable to open songs in BBMO, so I am delaying any real work for now.
In both cases (BBMO to BBM, and viceversa), the affected songs seem to play without issues in BeatBuddy pedal.
Pretty much what I’ve experienced as well. It might be helpful if you post a screen shot of the BBM message as it might offer details for the developers.
My experience is slightly different in that I had some songs that BBMO would not open or play. The same project would open in the BBM and displayed this message.
If I understood Andrew13’s post from Songs exported from BBMO 2.0.4 do not import into the BBM - #4 by persist, it indicates what could be causing the problem.
I did some additional testing with an older beta version of the BBM (that was being developed for autopilot functionality) and the error message it displayed seems to correlate with what Andrew13 mentions in his post.
Just my opinion, but I don’t think that Singular Sound will roll back to an earlier version of the BBMO (but it would be nice if they did). Although I can’t speak for Singular Sound, they probably prefer to fix the bug and release an update.
Some things that might help until we get a fixed BBMO:
avoid opening a BBMO project in the BBM, if at all possible;
I’ve noticed that BBMO 2.0.4 opens one-press songs much more slowly lately (sometimes taking 3-5 seconds before the song is ready to edit or play); I don’t know if this is because of the size of my project or that there are a lot of users using the BBMO, Internet latency (or even attributable to the BBMO code). Based on this, my suggestion is to allow the BBMO to fully load/open the song before attempting any other function in the BBMO. For me this seems to reduce the risk of corrupting a song in the BBMO.
Because I download and zip my songs for later posting to the forum, I always have a backup of each song outside of my project. When I encounter a song in the BBMO that won’t load/open, I delete the song, save the BBMO project and sync to my card, I then unzip the song I backed up and import it to the BBMO so that I have a working, editable copy of the song in my project; save and sync.
Yep. Your screenshot is basically the same as I’ve encountered. Error while parsing, the recovery and copy and a part of the file was not used by parser, more data than expected. If I open BBM again, I will post any screenshots.
I also have songs that I cannot open in BBMO.
Thanks for pointing out the thread. It makes all the sense in the world, didn’t expect BBMO to be adding Autopilot data to the songs…
I concur with you that SS will not roll back now. When I suggested it, it was a desperate measure, and would have been a great gesture, for us the be able to work in our projects the past weekend. As it stands now, with no news about this, I would expect a fix in a new version, hopefully soon. It just is very unnerving to me, with limited time as I believe most of us are, having planned a weekend of “fun”/working with BB and being stuck, not even being able to use legacy BBM.
Thanks for continuing to post. I have the same feelings and would have loved to spend time putting together songs and beats. Oh well - hopefully the fix will come soon. Or maybe even an update to this post? I did get an email from support and sent them my project.
Thank you for reporting this and for providing the files. I’ve prepared a detailed report for the dev team regarding this case so they can take a look.
