I understand there is undo button but when a bunch of changes have been made and the results aren’t what I expected, I don’t want to click undo a bunch of times and not really know how many undos I need to click to get it back to where i started.
It would be good if there were a snapshot capability that we can revert to.
Thank you for your feedback! I’d recommend duplicating the song first before making any changes. This way, you can always easily reference the original beat.
If you have any further questions, feel free to reach out!
My issue with bbmo is that duplicating a default song is not efficient when I’m only initially hunting for a song choice and evaluating settings. I’ll typically try various tempos and drums during evaluations and BBMO modifies the default song on these experiments. I typically explore many songs, try it with various tempo changes, drums and decide they are not an optimal fit. Then further hunt among different default songs. Each time when using BBMO unintentionally leaving the default songs changed during my experiments. There should be a way without duplication required to only evaluate and experiment in songs to test a tempo change and drum without it destroying the original default song settings. The legacy BBM does not behave the same way for experiments and is safer in maintaining the integrity of the default songs. Meantime if I decide to use BBMO (I’m not currently for this reason), I will duplicate the default song for every single initial experiment. Terrible overhead and considerable time wasted to only briefly explore many various song choices. I typically will review many song choices with tempo experiments and drums before deciding on a song. Legacy BBM I can try many songs very quickly, actually in seconds, before seeing a potential suitable song. And without fear of corruption of the default song. Maybe an RFE to briefly put BBMO in safe read only mode during experiments in songs. Or a required save feature like BBM has when we commit from an experiment.