In my opinion the whole of gthe interface needs a complete rewrite.

Loose the Win 95 look and employ a consistent modern design across the whole interface.
Make it possible to have a view of the interface where useless buttons can be hidden
Forget silly icons, or relegate them.
Why have two icons for Notation and chord sheet when one button does both?
Don't have invisible buttons (yes it's really true). Imagine a user trying to find the button to change a transposing instrument to Eb. Tip - top quarter of change key button - unindicated.
Loose silly long menus like the the change key button. This can be done clearly in a small space.
Demote hardly buttons like the juke box buttons to menus
Make the preference menu far more useable and visually attractive - it's cluttered and has the user friendliness of a 1960 Welsh telephone book.
Make all menus consistent with eachother, creating a native feel and use more spin buttons.

Looping is a function I use every day. It's notoriosley unstickable. For example, if you touch a space bar (and a lot of other functions, the loop is forgotten even though it appears to be there. This is URGENT as it ruins basic daily experience. I say use two virtual visible pins, green for start, red for end of loop. Make them stay clicked until unclioked!!!!

The Chord Sheet window needs a lot of work. It should be possible to see both the chord name and the Roman Numeral for every chord, by default. Not a hover over, but maybe the Roman numeral in small, botton rhs of bar. This can be tremendously educational - on an habitual basis.
Make it possible to create a note for every bar (hover over).


I would like to see the ability to take any loop and bring it through stand cycles - without having to write everything. A right click "cycles" list - 4ths, wholetones, minor thirds, etc with no trouble of writing it all out. Again, if you store the next generation in the next key (according ot user definitions), this would stop the rebuild lag - IMO.

The whole song also needs to be able to change keys, and no it does not work quickly enough at the moment it splutters. Use a memory dump to store the generated song of the next key (according to cycle settings)

We should be able to make a hover over note for every chord.

We should be able for users to colorise bars in the window according to whim - example intro chords in pink, drum fills in blue, vocal intro by Fred in purple.
Go through all the right click menus trying to minimise clutter, relegate silly functions to the drop downs.
Assuming we get a tempo track (and please make this accesible to pedal input), then make this visible in an improved time line.
Make use of hover over tooltips - for example the eyeball button should have a hover over tooltip "hide or reveal tracks".

The notation window - when revealed, should show a customisable quantized view. Although the current overcluttered view is useful when working out a particular phrase, it's over cluttered and unusable for sight reading.

Don't introduce out of house software and call it a new feature.
Across the whole design, be aware that when using BIAB, the user often has an instrument in their hand occupying their hands. This is why a MIDI pedal(s) - respnding to MIDI control variables, stop and start, increase tempo or ritard, increase volume or decrescendo, tempo etc should be available for live situations. Playing to a click track tempo is too restrictive.

Z

Last edited by ZeroZero; 05/31/25 09:35 AM.
Win 11 64, Asus Rog Strix z390 mobo, 64 gig RAM, 8700k