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.