Originally Posted By: Matt Finley
This may help you understand the BIAB choice of chord names.

In the file, X/BB/Data/pgshortc.txt you will find this text:

; Note these are already defined in BB, and you can't over-ride these shortcuts
;sus2@2 add2@2 m+@m#5 dim7@dim 7aug@7+ sus4@sus 11@9sus 9sus4@9sus
;13sus4@13sus add9@2 7sus4@7sus s@7sus h@m7b5 d@dim J@MAJ7
; f@7b9 m7+@m7#5 NC@C. no chord l@7Alt u@(Blues) 7u@7(Blues)
; Lyd@lydian Lyd@lyd Lyd@4#

This makes it clear that BIAB considers sus2 to be 2, add2 to be 2, and add9 to be 2.

Bob is correct that they will generate differently but BIAB treats all three as a 2 chord.

Matt, I'm replying to this again because it just occurred to me that BiaB's substitution of my A2 chord with an Asus2 chord is inconsistent with what you said in your post. IOW, if BiaB considers a sus2 chord to be a 2 chord, why is it changing my 2 chord to a sus2 chord when it imports my XML file?

Tom Levan (pronounced La-VAN)
BiaB 2024 Win UltraPAK Build 1109, Xtra Style PAKs 1-11, RB 2024, Windows 10 Pro 64-bit, Intel Q9650 3 GHz, 16 GB RAM, 500 GB SSD & 2 TB HDD, Tracktion 6 & 7 (freebies), Cakewalk, Audacity, MuseScore 2.1 & 3.4, Synthesizer V