I am a loyal BIAB user, dating back a decade or more to early versions. I use BIAB to create great backing tracks but not an expert on music Notation. The learning curve has been frustrating to say the least. The automation algorithm is intended to save note entry time but it backfires. I waste a lot of time undoing its forecasted note durations.

The algorithm does rarely produces the right result first time, compared to other products that require the user to explicitly pre-select a note duration (i.e., quarter, eighth note).

I am starting to appreciate the rationale for BIAB's notation approach but shortening the user's learning curve and reducing early user frustation should be a PG (Pretty Good) goal:

1. If the user enters a downstream note before earlier notes, the algorithm produces a confused sequence of notes and rests. These automated notes then require time-consuming replacement. In the user’s manual and tutorial video, state the obvious importance of entering notes from left-to-right.
e.g.,
“The algorithm automatically sets the duration of each note and works best if these notes are entered sequentially from left to right.”

2. Add a simple way to delete rests (like notes). Perhaps this is disabled because the algorithm often places these rests and won’t let the user delete them!

3. An “undo” single-click button in the Notation window would very helpful.

4. A “Zoom” button in the Notation window would also be helpful. I found the scaling option (%) after a lengthy search. It’s helpful to turn off the right-hand views (e.g. Mixer) when using the Notation view. Double views take up too much useful screen space for placing notes more accurately. View-switching could be automated, at least set as initial default.

5. There are countless warnings when placing notes “almost” on a 16th-note grid lines. I eventually found the “lock to grid option” and that might help ease the frequency of these warnings? Why not make grid-locking a default?

Overall the BIAB options and user interface continues to become over-crowded. I realize that software developers have to make some hard choices. Perhaps more extensive customer beta testing is in order before release?