PG Music Home Forums PG Music Wishlists Band-in-a-Box Wishlist Specific suggestions - Chord Sheet

This thread is for suggestions regarding the Chord Sheet view. This is for specific suggestions only, not general comments. There are a few ideas extracted from the main user interface enhancements thread


robertw:
I think the Chords Timeline work great, but I would like to see perhaps, text to show 1 verse, 2,verse, etc... as well as where you have some kind of action, like Fills, Push/Hold, etc...
Maybe R1, R2, R3 for the Repeat signs, and a "F", "P", "H" and for more than 1 action in a bar "$" (used a dollar sign, could be whatever works best).
<chords_timeline>


Matt Finley:
One area not mentioned yet is the basic format of the Chordsheet. There have been good suggestions made in recent years about organizing a cell differently, so each measure has four clearly defined subdividable beats (and more or fewer beats per measure if other time signatures are implemented), so that microchords are made more straightforward and the whole idea of commas is eliminated.

1) +1 on what is called an arranger track in other DAWS. Make it easier to show flow. So, is this more than labels?
2) +1 Charlie also suggested this with ability to show changes in RTs. This adds fodder to the idea of an arranger track.
3) -1 I am OK with standard notation repeat signs. There is a whole other thread on repeat because in general they tend not to work well.
4) Don't understand. I fear an alphabet soup with decoder ring to cramp hidden meaning in. Like the idea of an arranger track to call things out clearer.

5) +1 yes, I would like to see zoom expand the bar out to see all beats in a bar.
6) Yes, see above
7) yes, see above. Micro chords need to become part of the chord view.

If you have 4/4 or any other time signature and you need a bar with different number of beats...
Currently, when you edit a specific bar through Bar Settings and set amount of beats for that bar, it changes all of the bars that follow the one being changed in Chord View.
It should only change that specific bar, leaving all the following bars time signature(s) intact.

Why design all views independently, forcing the user to choose between the ‘Chords’ view OR the ‘Tracks’ view? Wouldn't be much better if we had a main screen where the user could simultaneously see all the most important views (chords, tracks, lyrics, sections, the whole song's structure...) and edit any of them from a single place? Take a look, for example, at Song Master Pro, is a beautiful example of how different views can be integrated in a single screen in a really intuitive way:



First, you always have a view of the whole song structure, you can navigate to the different parts directly from there, and you can also zoom in/out directly from there:



Then, you have different "Tracks" (Views) that you can show / hide as you wish. No need to see the "Sections" or the "Lyrics" track? No problem, just hide them:



Want to use the mixer or any other tool? Just click on the tiny icons at the top right to show / hide the tools / browser panels:

Want to add / edit / delete / copy / paste a chord? You can do it from the main screen (in general, you can edit any element from the main screen just by clicking on it)



You can also move chords directly from the main screen, just by draggin them. Note that the chords will move accordingly to the snap setting, so it's possible to insert up to 16 chords per bar from here (no need to use commas, carets, or that counterintuitive "Micro chords" feature)



Want to loop a section? Use the standard and super intuitive method you're used to:



Want to see just the whole chord sheet? No problem, juts click on the apropriate icon. And yes, you still can edit most elements (chords, lyrics, notes...) also from this view just by clicking on them:


It's all about flexibility, modularity and coherency between the different views.

Yes/ +1

I like Cerio's points.
This conversation was breached slightly in many of the previous threads in the last week.
Which puts emphasis on a serious improvement of the Track view. Add a decent chord area with bigger editable chords. Add an Arrangement Track the show the parts of the song.

I guess another point I'd like to leave PGM with is, all of these discussions have been implemented in other music software tools. Spend more time analyzing what you like about those tools to see if it's easy to do in BIAB.

I like the concept, and looks very pretty... While I agree that inline chord entry is beneficial in some places, to insert something "fast".
+1 to have it as a timeline option...

However I love chord sheet layout. I find it very useful and easy to work with. Sure, it needs several improvements, but it is indispensable. Also, some people use that for practice, following chords - which would be not intuitive at all with inline strip.

The integrated view and the chord view do not have to be incompatible (see last image of my post)

I get it, but I like the cell view better (than over notation)
Don't get me wrong, I like the idea of inline chord entry/edit, but in other views.

Cerio, great visual presentation BTW. If PGM adopts some of these ideas, it could finally be a breakthrough for many of us and way forward for future users.

I am reminded of the statement by an older Supreme Court, rephrased to say “ I can’t define good design but I know it when I see it”. At some point we might find it useful to cite other software and what specifically we like about its design.

Micro chords Reimagined

Beats match Time Signature/Feel
Resolution defaults to beats
Beat marks only show on current selected bar
Context Menu:
- 1/8
- 1/16
-Triplet
- Insert Rest
- Insert Motif
- Add Drum Fill
- Shot
- Hold
- Exclusion Popup (drop down list)

Well, I must have blown people's minds being so obvious with my "Micro" chord's suggestion, so I will comment on my own post.

What does this have to do with the chord view? Everything.

1) It addresses one of the first abnormalities of the chord view the fact that a bar is broken into 1/2 measures. With this design the bar would be broken into the beats, so 4 segment for 4/4 and 3 segment for 3/4. This makes entering chords more intuitively obvious without having to learn some additional techniques.

2) It also introduces the idea of only showing the segmentation on the current bar keeping the look clean and familiar.

3) Micro chords by the pure name sounds like an afterthought (it was) and many people did not like or understand the design. This this incorporates in a natural workflow the most common musical chord situations, of the chance of a chord change on one of the beats in the measure and the ability to do a 1/8 note chord transition.

A more natural workflow where you don't have to explain to people about commas and micro chords.

BTW, I do believe the chord track is a nice chord sheet (printable for live musicians to follow) and show where Peters head was at in the initial days of BB, but with Chord Tracks being common in DAWs and stuck with a linear flow of DAWs a fully functional Chord track as shown in Cerio examples is the way to go for serious work on entering chords. It aligns with ideas of better (more room) showing the arrangement sections, and small changes you can make to the progression as it flows.
We are caught between two subjects here Track View and the Chord View, so I will put my examples in the track view suggestion area.

Jeff,
1) Micro chords are not really 1/16th chords, are they? They seem not, not in a traditional sense. Using MC you can create interesting musical nuances, but that will be it. If I remember correctly, you yourself had made a nice diagram showing that they are "layer" chords, over the main chord(s). If this is the case, then there is no place for them in actual Chord Sheet as they are a "side" tool and a panel would be a perfect candidate for that. Perhaps an indication that MC is present a the bar? A colored dot or such. Also, I think typing in microchords in main cells with commas is a bit overkill, as instead of arranging you do sort of coding.

2) "Chord track as shown in Cerio examples is the way to go for serious work on entering chords." For Track View, ACW - Yes. Would be great! And yes, suggestion belongs in Track View thread. Chord Sheet is a different view and serves a different purpose.
3) I agree that 4/4 should have 4 cells, 3/4 -3, etc. Absolutely.

FWIW - why not have a grid like a lot of DAWs have. Set the grid to whole notes for one chord per cell. Set it for 8th notes for up to 8 chords per cell, etc. Have it so if you change from say a quarter note to a 16th note grid cell the quarter note chords and all other note chords still line up perfectly. This could work for all time signatures. YMMV

1) Yes, currently up to 1/16. in practice it rare for a chord to be less than 1/8. (I actually think they should reduce its complexity to 1/8)
2) Hmm, you may have missed the power of Micro Chords. I used them immediately to add syncopated transitions chords in a song I was working on when they were introduces.
They are real chords and rests and motifs that will render in the track even in the plugin.
3) The micro chords already show up in the chord sheet after you use the convoluted MC Window. (all the same symbols I showed)
4) Disagree, I would have loved to just enter my 1/8 syncopated chord directly into the chore track.

Yes, I was trying to make it less intrusive and less of a change for people used to using the cord track. That is why I suggested the grid only shows up when entering in chords for a particular bar. I also think 1/8th is enough granularity.

FWIW - I think we have to stop worrying about how people currently use BiaB. Some of the outstanding suggestions along with accompanying mock-ups are radical changes from the current GUI. If we keep worrying about the current GUI/workflow then nothing will change. We all are capable of change. IMHO if this is going to happen lets do it right the first time.

That is just my opinion and other may not agree with me.

Yes, I fully agree/+1.

I absolutely agree. The program really (and I mean, really) needs a complete GUI redesign. This has been discussed here extensively, at least for the last ten / fifteen years.

I would tend to agree however, to be clear, I would embark on a complete parallel rewrite including a new UI. I did it 3 times in a in a 30-year carrier and each was huge leap in UX.
I have also watched and work with PGM for over a decade. They will take small steps and add things, but rarely will they replace something.
My suggestions are all doable in 2025.

Agree. +1
However, likely it will be a challenge to do it all overnight. Even big companies with very deep pockets do it in parts. I would rather see a few most supported big concepts done very well, and if successful (cheering crowd), continue the trend going forward, than see something mediocre done as a whole.

Meanwhile back to what we agree upon.
1) Higher resolution for a bar.
2) Resolution that marches time signature.
3) Some way to easily enter chords up to 1/8 on the chord sheet.

I think the changes in Chord Sheet are very important.
You can directly refer to the most popular DAWs, such as STUDIO ONE, CUBASE.
You can create a "Chord track", below is the instrument VST, PIANO ROLL, Audio track.

After establishing the concept of chord track,
we further refined the chord track. For example, it is more convenient to input content. It is changed into multiple small grids. We removed the micro chord function. I have never used micro chords. We directly subdivided each bar.

I talked about this issue a few years ago.

https://www.pgmusic.com/forums/ubbthreads.php?ubb=showflat&Number=744720#Post744720

Everything shows an unfolded view. What about multiple choruses, tags, repeats? Band-in-a-Box has humanizing selections that are invoked when these features are used.

@MarioD,

Current users of BiaB, should really have no problem adjusting to the new GUI even if it is radically changed, and any new users should find it easier to use than it currently is.
There, will be a learning curve, and all good software has a learning curve.

That was my point.

Suggestion: Pure contextual menu for Chord Sheet.
Simplifying it to just the chords, bars and progression improve the user workflow.

Everything else is a distraction and better belong somewhere else.

My mockup was a radical change, compared to the original solution for micro chords. I like and agree with MarioD ideas as well.

"Song Master Pro, is a beautiful example of how different views can be integrated in a single screen in a really intuitive way:"

"You can also move chords directly from the main screen, just by draggin them. Note that the chords will move accordingly to the snap setting, so it's possible to insert up to 16 chords per bar from here (no need to use commas, carets, or that counterintuitive "Micro chords" feature)"

I saw Chord Sheet improvements in the Forum Tittle and I thought I would post about having the chord entry in the Tracks View and how you can zoom in to enter chords on any beat resolution without the comas and micro chords, BUT you did already, and not only that but this awesome looking and incredibly well designed GUI.
RapidComposer would enter chords the same way depending on what the snap resolution was set to, drag and resize chords.
I will have to go check this out ! thanks Cerio !

I am partially color blind and can't tell many colors. In some threads I have to highlight some areas as I can't read them. Thus any color theme in BiaB must have the option to adjust or change any color.

Yes/+1.

Summary of input on Chord Sheet:
OP: This thread is for suggestions regarding the Chord Sheet view.
This is for specific suggestions only, not general comments.

Text about Arrangement/Arranger Track:
Supporters: robertw, jpettit, Charlie

More granularity in Bars/match signature/Integrate Micro Chords:
Supporters: Matt Finley, jpettit, ~Rustyspoon#, MarioD

One Main Screen with Panels: (most popular in original UI Thread)
Supporters: robertw, Cerio, jpettit, Rustyspoon#,musocity
A bit OT: This challenges the need for a Track view and a Chord View

Editable Chords Track
Supporters: jpettit, babymusic, Cerio, musocity
A bit OT: This challenges the need for a Track view and a Chord View

Improved (clean to the context) and more context menus
Supporters: jpettit
A universal input.

If PGM really wants input form customer and want to know how popular the idea is the need to turn on voting capabilities in the Forum.
Tendency to divert from the OP and minimal customer input are common with just open-ended conversations.

+1000 to context menus, which are an essential to improve discoverability > ease of use > better user experience.

https://www.uxpin.com/studio/blog/discoverability-in-ux/

In Reaper, for example, right clicking on almost any element opens a menu with options about that element, so the user always know what is possible to do with that. Super simple, super intuitive and super effective:

https://youtube.com/shorts/OKIASspvNgs?si=0MuBZOsp_l_sji9b

"In Reaper, for example, right clicking on almost any element opens a menu with options about that element, so the user always know what is possibler to do with that element. Super simple, super intuitive and super effective:

https://youtube.com/shorts/OKIASspvNgs?si=0MuBZOsp_l_sji9b
"

I posted a video on [R*****] menus to give ideas but it just got deleted.

+1

Reaper has one of the best, well thought, user interfaces I have ever seen. I remember very well, 15 years ago the day when, working in the middle of a production, I moved all my projects from cubase to reaper after installing the program and testing it just for a few minutes. After a couple of hours of use I felt way more comfortable with Reaper than after years and years of using Cubase, Logic or Protools. And the reason of that was simply because, despite having a zillion of features, everything I needed was exactly where I thought it should be, and everything worked exactly how I thought it should work.

Precisely that is done in an awful lot of software and it works well.

If the software starts out with that philosophy, then it stays solid and consistent as it grows and evolves.

"Reaper has one of the best, well thought, user interfaces I have ever seen....."

You can't improve Biab unless you study [R*****], I have spent so much time over the years posting things to make Biab/RB/Plugin better by showing examples in [R*****], whether it's Instant Gen Play Direct, Live Arranger or so many other things.
The trouble is so many like to criticize and are offended with me posting all this info as they have not or will not try things so remain in the past. This is like the numero uno thing that keeps these products way behind other software. It's so good to see those here that understand and don't knock or delete. For me to take on the establishment has by no means been an easy thing.

Let's not over emphasize one DAW over another. It is about common UX approaches to make things more user friendly. (like all modern creative tools) Good Context menus is just one example. Remember they want specific examples vs what is already there.
The point made here was lots of smaller specific context menus dealing with each object on the screen.
So, it is the principle of right mouse click to see where you can go from here.

Other points:
1) Don't mix options with next actions. (separate place/button for local options)
2) Don't throw in paths that are not pertinent to next steps.
3) Don't do things in context menu that could be better done with supporting panels

+1

If one DAW allows you to have whatever you want in whatever menu you want this allows users to decide and create the functions and layout they need then are not stuck with what the company thinks is best for them. As I said the video I posted showed all this but was deleted. I should not have to use AutoHotkey to create up the menus I need.

To be able to enter N/C (No Chord) in Chord View.

A very old request. The puzzle is that this has always been among the shortcut chords in pgshortc.txt but it does not work.

Thanks for your summary of the main topics Jeff, it's very helpful. And thanks everyone for your great ideas.

Didn't see anything for a "new" thread, so this. Windows version 2025, here, with the latest build.

1) When setting up a tag ending, what makes the chord sheet temporarily jump back to measure one (as the tag begins), before quickly reverting back to the normal ending? Is there a simple workaround for this?

2) In working with the F5 key in muting tracks and the “back to normal” setting, might it be possible to exit the F5 view by “apply” only and not the “x”, as well? One click would save time, when doing a lot of editing.

3) When a song uses a utility track(s), shown in the mixer, the next song called-up in live play may not have utility tracks. However, the mixer continues to show the gray utility track until clicked away. Shouldn’t it revert back to the default view, if no utility track is present?

"2) In working with the F5 key in muting tracks and the “back to normal” setting, might it be possible to exit the F5 view by “apply” only and not the “x”, as well? One click would save time, when doing a lot of editing."

I don't follow this one. F5 is now non-modal. You don't need to "apply" anything for mutes/back to normal. It applies changes automatically and you can navigate chord sheet as you wish selecting any other bar and continue further with mutes/unmutes until satisfied... without closing it. I am not even sure what that "apply" button does. You are 1 click (X) away from closing the dialog.

With hope that PGM is serious about UI design for 2026, most agree that modular panels are the way to go. If that is the case, I am sure that F5 will make it there, as it is a popular item.

Wouldn't it be nice if we could drag and drop an audio track or tracks into the track view? If there are other tracks already we could align the audio with them. BiaB could either determine that audio track's tempo or match said track to BiaB tempo. If BiaB time signature were still only integers the audio track would have to be stretched or shortened accordingly. This could take the place of the ACW and all of its problems. YMMV

With the advent of many plugins allowing you to drag block chords into the DAW, PGM should seriously be considering block chords as a drag and drop feature.
Dragging chords out of a plugin such as Scaler or Toon Track Keys VST3 onto the chord track should just automatically interpret the block chords as chords recognize the chords and enter the chords names into the chord track.

I am seriously intrigued by this suggestion. I tend to work in the other direction: I make a rhythm backing track then take the WAV file created by BIAB into another program, my notation program. Thus I don't use or need many of the features others use, such as VST3 support or the ACW.

One reason I must go that way is the fact that BIAB is limited to tempos of integers only.

If BIAB supported non-integer tempos, I could match up BIAB files with other software better. Or, as I think Mario is suggesting, if BIAB could IMPORT an audio file and normalize the tempo to two decimal places, I think it could change my workflow to keep me working in BIAB longer.

I know we all keep saying this. BUT WHY? BIAB can create a "tempo map" in the ACW which will match not not only fractional tempos, but varying tempos! So if it can do this why does the BIAB app not have the ability to manage this for us with any midi and audio it or we provide?

Here’s another reason for support of non-integer tempos: it should make it possible to allow tempo changes within the measure. Right now tempo changes occur only at the beginnings of measures. Ritards or accelerandos would be smoother.

And another reason, something I encountered once in a recording studio: the integer tempo may not be what it says it is. I took an acoustic guitar track made by BIAB into a recording studio to use as a click track for other instruments to play to. My track was a Bossa Nova recorded at quarter = 140. The studio discovered it wasn’t actually 140, but a tiny fraction under. I don’t remember the exact number but we got it very close at 139.8.

I've added non-integer tempo as a feature request, id# 4993

Nice.

Thanx

Wow, what does it take to get the other dozen Feature Requests in this thread along into the FR database?

The entire thread is being watched, as we are focusing on UI improvements. The non-integer tempo request isn't a chordsheet UI thing (what this thread is specifically for), so I added it as it would likely be missed otherwise.

There's a method to my madness. Sometimes. Very rarely really.

If there was a like button on this forum as requested, I would give you a like

Thank you Simon. The support for non-integer tempos is an old request, but it came up again here in Mario’s post about workflow. Thanks for your action.

When the wind is north-north-west ... obviously

I'm pretty sure that the boss mentioned that this was going to be delivered and was on the 'todo' list a few years ago. Seems they still haven't got around to it.
RealBand can do it. I think just about every DAW imaginable can do it. I think it's been requested since about the inception of the program.

I don't believe UBB supports Like buttons sadly!

Happy to add it! I know it's a very old request lol.

South-north-west actually

Yep, but it didn't seem to be in our database so I added it. I'm sure we're all aware that it's a popular request.

Matt, Dan is correct about tempo syncing and the ACW. He's also correct that using the ACW tempo map, BIAB can import an audio file and match fractional tempos as well as varying tempos. Users can also record audio without a click track into BIAB and sync with the ACW.

In 2025, using the new Stem Splitter, users can import original audio recorded in 1955, split the recording into five tracks and BIAB using the ACW can tempo map and normalize each of those tracks and sync them with BIAB tracks. The Stem Splitter seems to work with most original or commercial tracks.

As a side note. PG Music finalizes all of the Artist Performance Sets - there's currently 18 I believe. All of their demos and tutorials as SGU BIAB songs. Their workflow has always been the reverse of your and others export to DAW workflow. They import DAW material to sync and normalize with BIAB.

Charlie, thank you for your thoughtful analysis here. As usual, I have homework to do!

To try to bring this back to the UI/UX topic, as usual Charlie and Dan are technically correct.
I thought MarioD request:
"Wouldn't it be nice if we could drag and drop an audio track or tracks into the track view? This could take the place of the ACW and all of its problems." was really a plea for improved UX.
It has at its core what I have been requesting nonstop for three years. UX user experience and workflow are really the same thing.
Hidden in the request from my perspective was the idea of making the tempo track a global thing that worked equally well in all views.
It was not a matter of can it do it?
It was a matter of improving the user experience to make the main views more of an integrated workflow process rather than a bolt on.
Make the Tempo track global along with ability to do tempo mapping. A global track on top of any view would correspond with that view whether it be audio, MIDI, or Generated players.
Another global request to Make the Arrangement a global track to better keep track of the arrangement globally in all views.

Let's not lose track of the PGM UX request for input.

Jeff, that makes perfect sense. Great job.

Yes, that was my thought but I like your idea much better. A universal tempo track is the perfect solution.

+1

If you would to see an example of a tempo track that works very well, look at the nTempo track in Presonus Notion 6 notation software.

ive requested for some time to pg the following 'special tracks'....
(so +1)

1.tempo track
2.chord track
3.markers track

all updateable...
and various other special tracks...eg drum solos track.

but i suspect that given bb is not like a traditional daw due to its special auto accompaniement features it might be difficult for the pg programmers to do this ?.
im sure that pg have thought about these needs over the years given their products often interface to and feed non pg daw apps.

my 'dream' is in the new bb track view have these special tracks at the top of the waveforms under the horizontal ruler.

om

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

Basically I disagree with most of your comments

Keith

ZeroZero, while I don't agree to all (likely my use is a bit different) , there are some very solid points you've made. Thank you for contributing.

PO

Typically when a computer takes over a task from paper base, it can be designed to emulate the task the paper did - centrally. However it soon becomes obvious that a computer can radically enhance the whole role.

In this case the "Chord Sheet", sure it's primary role is to display the chord sheet, and it does a good job of this on the whole, but I have been putting my moind in the position that is playing the song and the come to a bit where they are challenged.

Apart from solid looping of the bar(s), As a musician I would want to ensure that

A] I knew the function of the chord - Roman Numeral style.
B] I could see voicings I could a basic notated form of the chord voicing -, filtering from very basic to advanced
C] Identify any melody notes involved in the bar - perhaps utilising an improved notation window.
D] I could make a free memo, if I desired, for the bar.

I don't want to be hunting all over an interface for this. Ideally, I want to right click on my bar in question.

Generally, many right click menus in BIAB are to long and contain irrelevent items. Try right clicking on a bar, for example, and you will find no less than 27 items! This clearly needs a major redesign. Why have preferences in this menu for example? Why have preferences and display options there at all? Why have Cut and copy list at the top and insert and copy bars at the bottom? Long lists like this ad tedium to the eye. Much of this list can be binned. Toolbar Drop down menus contain such things.
I believe that optionally, in a small smart font, the chord function should be displayed either for user selected bars, or for wthe whole song. Using roman numerals something like " ii V 1 of IV, " . Right clicking this, gives options like voicings and highlights any chord tone that is also part of the melody.

Very well said.
The potential of well-written software running on today's personal computer is enormous.
Add AI into the mix and it's off the charts.

I still basically disagree with your statements.

By the way what is PO?

Keith