Originally Posted By: Jim Fogle
Originally Posted By: muzikluver
snip ... So, it appears that there are several bugs in the chord mapping portion of BiaB's XML file import algorithm that need to be fixed.


muzikluver,

It's great to read your observations. I believe you can tell many forum members are enjoying participating in this thread.

May I suggest you contact PG Music Support about the XML file import algorithm errors? If you attach your XML file along with a bar and beat description of the chords that are misinterpreted then they will have the content needed to correct the issue.


Jim, I finally got around to writing an email to Tech Support about this issue. The reason it took me so long is that I was in the middle of writing a new song (actually two new songs) when I discovered these problems, so I didn't want to lose my songwriting momentum by taking the time to create all the test files I would need to send to Tech Support with an explanation of these problems in an email. Below is the text of my email along with two links. One link is to this thread, and the other link is to a ZIP file of all the files I created for my tests:

"Dear Technical Support,

I recently discovered some problems with BiaB's importing of chords in XML files that affects the "2," "sus2," "sus4," and "add2" chords. There are two aspects to these problems. One aspect pertains to BiaB's interpretation (via substitution or mapping) of these chords when they are imported, and the other aspect pertains to the settings in the Display Options settings for the "2" and "sus2" chords. Because it would be difficult for me to explain all the different scenarios that have occurred during my importation of XML files with these chords into BiaB, I am providing you with a link to a ZIP file that contains all the files that I've used to perform and document my tests. The information in these files should be self-explanatory. All three of the XML files and all three of the PDF files were created from MuseScore 2.1. The PDF files will show you the lead sheets as they were created in MuseScore and exported to XML. The six BiaB MGX files correspond respectively in pairs to each of the XML files with a "b" version and a non "b" version. The "b" versions were created importing the same XML file as the non "b" version but only after changing the Display Options settings to that the "2" and the "sus2" chords will display as "sus" and "sus4" chords respectively and then saved with these settings. The RTF file contains a list of all the A chord variants that are in each XML file and what those chords ended up being in BiaB after they were imported. The notes at the bottom of the RTF file further explain the test results and the different scenarios under which those results occurred. Prior to importing these XML files, I made sure that I had selected a style that was compatible with the song settings in my lead sheet, which was the _CMPFMDS.STY with a time signature of 4/4 and an even 8 feel. If you have any questions about these files or the results of my tests, please let me know and I'll do my best to answer them. Below is a link to the ZIP file that I uploaded to my Box account and a link to the BiaB Forum thread that I started on 7/13/19 to discuss and identify the specific nature of these problems. Thanks for your help!

https://app.box.com/s/qcusj5d81fmx8s5ym3y6x90fuwnvr2nu

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

Tom"

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