<<< The 2, sus, and add chords are the only ones I've encountered any problems with that have forced me to manually make changes to the chords in the chord sheet.>>>
For multiple chord errors and if BIAB recognizes both the correct and incorrect chords, you can search and replace multiple chord errors in the following manner:
Thanks for the tip, Charlie. I didn't know that capability was available. I've already used it several times today and really like the fact that it retains the previously entered chord change info so that I don't have to enter it again.
Glad that helped you out a bit. I've found it's a useful utility in cleaning up songs analyzed by the Audio Chord Wizard. The ACW seems to read a chord erroneously over and over in an analysis and this utility makes short work in correcting to the right chord.
Glad that helped you out a bit. I've found it's a useful utility in cleaning up songs analyzed by the Audio Chord Wizard. The ACW seems to read a chord erroneously over and over in an analysis and this utility makes short work in correcting to the right chord.
Can confirm...
It drove me nuts how again and again it interpreted every instance of Fmaj7 I used in a given song as F/A.
I experimented with multiple voicings at various points on my fretboard after making sure my guitar was 100 percent in tune, (something I'm incredibly particular about anyway), and I could not get it to display a Maj7.
FWIW, I now recall this was before the revamped ACW so I don't know if that may have improved...(although as an aside, there were certain elements to the old one I preferred so I'm happy that it's still possible to use either).
Band-in-a-Box 2024. Custom Build Desktop PC W/ Windows 10 Home 64-bit. CPU: Intel Core i5-9600k @ 3.7GHz (6 core x 6 threads) RAM: 16GB DDR4. Storage 238GB SSD + 2.7 TB HDD. GPU: ZOTAC NVIDIA GeForce GTX 1050 Ti 4GB
In RapidComposer I can set the notes and aliases names for each chord. I can add a So What chord Csowhat
Pipeline, how does this relate to the problems I've discovered with BiaB's incorrect interpretation of certain chords during its importation of XML files? I'm familiar with RapidComposer, but it's an entirely different program that I don't have and don't plan to obtain any time soon.
I have never used xml, how exactly does that work in Biab? Have you already created a new song including the style then import the xml file or does the importing itself create a new song project and then you select the style? The reason for this question is my point earlier that styles many times determine how the chords are handled. Also, in my earlier reply I touched on the differences between the chords in a midi style vs an RT or hybrid style. Musickluver, are you talking midi styles or RT styles here?
Fundamentally if you want exact chord voicings then you need to write midi notation for that, it won't do anything for RT's because you get whatever voicing that was recorded in the studio so that's midi only. When you talk about your Add 2 chord, for every note in it you can have a different inversion (voicing) and if you add a slash bass note then you could have 5 or 6 appropriate voicings.
When you get into the weeds of specific chord names and voicings you really need to understand the theory behind that. Basically you think outside the box, think about what am I trying to do harmonically and find a way to get Biab to do it because as I said earlier as an AI music software, it tends to want to do things it's way. This is the whole rationale behind the program and it's name Band-in-a-Box. You get to have a virtual band of great musicians, give them the song structure and "basic chords" and they can come up with several different versions of your song for you. It's not designed to perfectly execute what you tell it to do.
Bob, I know that I had previously replied to your post, but I just wanted to also say that most of what you said here went completely over my head at the time because I didn't understand what you meant by "voicings" until some time after I had replied without really knowing where you were coming from. (DUH!) If I had looked up the word "voicings" or asked you to explain this term, my reply would have been very different from what it was.
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!
..Pipeline, how does this relate to the problems I've discovered with BiaB's incorrect interpretation of certain chords during its importation of XML files..
It has more user control that would be good in Biab so if you import/type a chord in the Biab you get it to recognize that chord as xxxx.
Biab reads the chord names in the musicxml but changes to it's equivalent, where as Reaper can't read the more complex chords in the musicxml yet.
When you say Biab changes it to it's equivalent that is similar to what I've discovered about the Stylemaker. That other thread in the Wishlist forum about all the problems with complex chords and bass lines exposed this. I just watched the only video I could find on Youtube about the Stylemaker and it's from 1997. It's exactly the same as we just talked about last week in the other thread, nothing's changed that I can see.
In the vid the guy made one telling comment almost as a quick aside. He said even though you can specify a chord type in the Stylemaker for a given instrument and give it weighting and all that stuff, Biab can and will change it depending on what Biab thinks it should be. This is the "secret sauce" we've all talked about for years. The Stylemaker does control a lot of things but still, Biab is the boss and can decide to do it's own thing.
This goes back to what I've been saying for years and I'm not defending it, it's just the way it is. Biab is not designed to take input from a user and give it back as that exact chord arrangement. It will take what you give it and "intelligently" interpret it for you similar to what a group of real musicians would do. That's how it's advertised and that's what it does.
How far the developers can go in modifying that or are willing to is completely unknown to us users and they never talk about it to us either.
Biab reads the chord names in the musicxml but changes to it's equivalent, where as Reaper can't read the more complex chords in the musicxml yet.
When you say Biab changes it to it's equivalent that is similar to what I've discovered about the Stylemaker. That other thread in the Wishlist forum about all the problems with complex chords and bass lines exposed this. I just watched the only video I could find on Youtube about the Stylemaker and it's from 1997. It's exactly the same as we just talked about last week in the other thread, nothing's changed that I can see.
In the vid the guy made one telling comment almost as a quick aside. He said even though you can specify a chord type in the Stylemaker for a given instrument and give it weighting and all that stuff, Biab can and will change it depending on what Biab thinks it should be. This is the "secret sauce" we've all talked about for years. The Stylemaker does control a lot of things but still, Biab is the boss and can decide to do it's own thing.
This goes back to what I've been saying for years and I'm not defending it, it's just the way it is. Biab is not designed to take input from a user and give it back as that exact chord arrangement. It will take what you give it and "intelligently" interpret it for you similar to what a group of real musicians would do. That's how it's advertised and that's what it does.
How far the developers can go in modifying that or are willing to is completely unknown to us users and they never talk about it to us either.
Bob
I think he's referring to what BiaB does when it creates the chord sheet, not what it does to those chords after than when it generates the tracks for each instrument, which is what you're referring to. I had one electric guitar (that I had added to a standard style) that kept playing something other than a C chord at different places in the song. Each time i regenerated the track for this instrument, that chord would move to a different place in the song and was clashing with the rest of the instruments every time. It took at least 10 re-generations of that track before I finally got BiaB to do what I wanted it to do.
Yes, I understand that but I'm looking a bit deeper. The question is why is someone using XML to import the chords into Biab? There's only two reasons.
One is so they can have good notation in Biab. Why would they need that, they already have good notation in Musescore. If they're using another music program that does not give them good notation and they want Biab for that and that's all they want, fine. Biab can provide good notation even if the written chords play differently. But, pretty much everybody also wants:
Two, the song to also play correctly. That means populating the chord grid to generate the song and have Biab play those exact chords in those exact places. That in turn leads to what I just wrote. Biab may or may not do that by design.
I don't play piano or guitar. Let's say I have a leadsheet, and I want to enter the song into BIAB so I can hear how it goes (yes, I can hear it in my head, but that's not the same). I could enter it into BIAB by hand, or try to find a more efficient way using import of Music XML.
To get the leadsheet into XML, there are several possibilities. One is, I'm using a notation program and I export it as Music XML format if supported. Another is that I have a PDF or printed sheet music, and I use a program to scan that and export it into Music XML.
If it's just a chord progression, many here have requested that BIAB allow importing of an ASCII text file or some similar format, maybe a spreadsheet, of just chords. Something like you might be able to find on many guitar chord sites.
This and related threads talk about how BIAB may interpret a chord in Music XML and change it in BIAB. I definitely want to know more about that.
-------------------
As an aside, having studied the code, my issue with Music XML is that it is a great idea with sometimes poor implementation. It's very verbose, and it's like working with a compiled language where the compiler tells you nothing about whatever the syntax error may be. You mentioned Musescore, and so far, that is the best software I've found to give me at least a clue of what (or where) the error is, rather than simply aborting the import.
BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus 192 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.
Yes, I understand that but I'm looking a bit deeper. The question is why is someone using XML to import the chords into Biab? There's only two reasons.
One is so they can have good notation in Biab. Why would they need that, they already have good notation in Musescore. If they're using another music program that does not give them good notation and they want Biab for that and that's all they want, fine. Biab can provide good notation even if the written chords play differently. But, pretty much everybody also wants:
Two, the song to also play correctly. That means populating the chord grid to generate the song and have Biab play those exact chords in those exact places. That in turn leads to what I just wrote. Biab may or may not do that by design.
Bob, neither one of your answers is a complete answer that describes my situation. I use XML to import both the chords and the melody into BiaB from a lead sheet that I created in MuseScore, which is the means by which I create a tangible representation of my songs that are in my head. For me, it isn't just about the chords because chords by themselves don't comprise a song. For me, it's primarily about the melody. However, a melody by itself is not sufficient for BiaB to generate an arrangement from because BiaB's arrangements are mostly chord based. I say "mostly" because BiaB has also used my imported melodies to create melodic motifs in the arrangement that are not on my lead sheet. My lead sheet only has the melody that goes with the lyrics---one note per syllable. This is why BiaB has been so beneficial to me in my songwriting endeavors. By importing both the melody and chords into BiaB from an XML file that was created from my lead sheet within MuseScore enables BiaB to create a very intelligent and sensible arrangement of my songs that rivals that of a professional studio---especially when I use the Bar settings function to turn various instruments on and off along with the part markers to switch the drum track from the "a" version to the "b" version and back again. So, whenever BiaB decides to "do it's own thing" with my chord progression per your explanation in a previous post, I usually have to regenerate one or more instruments that end up playing a chord or two that clash with my melody and sometimes with the other instruments as well. This happened to me on my most recent song because an electric guitar that I added to the standard style kept playing a chord other than a C chord in various places in my song. But I was able to get BiaB to make that guitar get the C chord right after about ten re-generations of that one instrument.
Ok, that's exactly what my #2 is and the good news is it's working pretty well for you. Sure, sometimes you have to do a bunch of regen's to get it to give you what you want and that's normal too. I think you already know you can save yourself those manual regen's by putting the song in Real Band and using the multiriff function or use the Biab plugin multiriffs in a DAW.
We’ve expanded the Band-in-a-Box® RealTracks library with 202 incredible new RealTracks (in sets 449-467) across Jazz, Blues, Funk, World, Pop, Rock, Country, Americana, and Praise & Worship—featuring your most requested styles!
Jazz, Blues & World (Sets 449–455):
These RealTracks includes “Soul Jazz” with Neil Swainson (bass), Mike Clark (drums), Charles Treadway (organ), Miles Black (piano), and Brent Mason (guitar). Enjoy “Requested ’60s” jazz, classic acoustic blues with Colin Linden, and more of our popular 2-handed piano soloing. Plus, a RealTracks first—Tango with bandoneon, recorded in Argentina!
Rock & Pop (Sets 456–461):
This collection includes Disco, slap bass ‘70s/‘80s pop, modern and ‘80s metal with Andy Wood, and a unique “Songwriter Potpourri” featuring Chinese folk instruments, piano, banjo, and more. You’ll also find a muted electric guitar style (a RealTracks first!) and “Producer Layered Guitar” styles for slick "produced" sound.
Country, Americana & Praise (Sets 462–467):
We’ve added new RealTracks across bro country, Americana, praise & worship, vintage country, and songwriter piano. Highlights include Brent Mason (electric guitar), Eddie Bayers (drums), Doug Jernigan (pedal steel), John Jarvis (piano), Glen Duncan (banjo, mandolin & fiddle), Mike Harrison (electric bass) and more—offering everything from modern sounds to heartfelt Americana styles
And, if you are looking for more, the 2025 49-PAK (for $49) includes an additional 20 RealTracks with exciting new sounds and genre-spanning styles. Enjoy RealTracks firsts like Chinese instruments (guzheng & dizi), the bandoneon in an authentic Argentine tango trio, and the classic “tic-tac” baritone guitar for vintage country.
You’ll also get slick ’80s metal guitar from Andy Wood, modern metal with guitarist Nico Santora, bass player Nick Schendzielos, and drummer Aaron Stechauner, more praise & worship, indie-folk, modern/bro country with Brent Mason, and “Songwriter Americana” with Johnny Hiland.
Plus, enjoy user-requested styles like Soul Jazz RealDrums, fast Celtic Strathspey guitar, and Chill Hop piano & drums!
With your version 2025 for Mac Pro, MegaPAK, UltraPAK, UltraPAK+, Audiophile Edition or PlusPAK purchase, we'll include a Bonus PAK full of great new Add-ons FREE! Or upgrade to the 2025 49-PAK for only $49 to receive even more NEW Add-ons including 20 additional RealTracks!
These PAKs are loaded with additional add-ons to supercharge your Band-in-a-Box®!
This Free Bonus PAK includes:
The 2025 RealCombos Booster PAK:
-For Pro customers, this includes 33 new RealTracks and 65+ new RealStyles.
-For MegaPAK customers, this includes 29 new RealTracks and 45+ new RealStyles.
-For UltraPAK customers, this includes 20 new RealStyles.
Look Ma! More MIDI 13: Country & Americana
Instrumental Studies Set 22: 2-Hand Piano Soloing - Rhythm Changes
MIDI SuperTracks Set 44: Jazz Piano
Artist Performance Set 17: Songs with Vocals 7
Playable RealTracks Set 4
RealDrums Stems Set 7: Jazz with Mike Clark
SynthMaster Sounds and Styles (with audio demos)
128 GM MIDI Patch Audio Demos.
Looking for more great add-ons, then upgrade to the 2025 49-PAK for just $49 and you'll get:
20 Bonus Unreleased RealTracks and RealDrums with 20 RealStyles,
FLAC Files (lossless audio files) for the 20 Bonus Unreleased RealTracks and RealDrums
Look Ma! More MIDI 14: SynthMaster,
Instrumental Studies Set 23: More '80s Hard Rock Soloing,
MIDI SuperTracks Set 45: More SynthMaster
Artist Performance Set 18: Songs with Vocals 8
RealDrums Stems Set 8: Pop, Funk & More with Jerry Roe
New! Xtra Styles PAK 20 for Band-in-a-Box 2025 and Higher for Mac!
Xtra Styles PAK 20 for Mac & Windows Band-in-a-Box version 2025 (and higher) is here with 200 brand new RealStyles!
We're excited to bring you our latest and greatest in the all new Xtra Styles PAK 20 for Band-in-a-Box! This fresh installment is packed with 200 all-new styles spanning the rock & pop, jazz, and country genres you've come to expect, as well as the exciting inclusion of electronic styles!
In this PAK you’ll discover: Minimalist Modern Funk, New Wave Synth Pop, Hard Bop Latin Groove, Gospel Country Shuffle, Cinematic Synthwave, '60s Motown, Funky Lo-Fi Bossa, Heavy 1980s Metal, Soft Muted 12-8 Folk, J-Pop Jazz Fusion, and many more!
All the Xtra Styles PAKs 1 - 20 are on special for only $29 each (reg $49), or get all 209 PAKs for $199 (reg $399)! Order now!
Note: The Xtra Styles require the UltraPAK, UltraPAK+, or Audiophile Edition of Band-in-a-Box®. (Xtra Styles PAK 20 requires the 2025 or higher UltraPAK, UltraPAK+, or Audiophile Edition. They will not work with the Pro or MegaPAK version because they need the RealTracks from the UltraPAK, UltraPAK+, or Audiophile Edition.
New! XPro Styles PAK 9 for Band-in-a-Box 2025 and higher for Mac!
We've just released XPro Styles PAK 9 for Mac & Windows Band-in-a-Box version 2025 (and higher) with 100 brand new RealStyles, plus 29 RealTracks/RealDrums!
We've been hard at it to bring you the latest and greatest in this 9th installment of our popular XPro Styles PAK series! Included are 75 styles spanning the rock & pop, jazz, and country genres (25 styles each) that fans have come to expect, as well as 25 styles in this volume's wildcard genre: funk & R&B!
If you're itching to get a sneak peek at what's included in XPro Styles PAK 9, here is a small helping of what you can look forward to: Funky R&B Horns, Upbeat Celtic Rock, Jazz Fusion Salsa, Gentle Indie Folk, Cool '60s Soul, Funky '70s R&B, Smooth Jazz Hip Hop, Acoustic Rockabilly Swing, Funky Reggae Dub, Dreamy Retro Latin Jazz, Retro Soul-Rock Fusion, and much more!
Special Pricing! Until July 31, 2024, all the XPro Styles PAKs 1 - 9 are on sale for only $29 ea (Reg. $49 ea), or get them all in the XPro Styles PAK Bundle for only $149 (reg. $299)! Order now!
XPro Styles PAKs require Band-in-a-Box® 2025 or higher and are compatible with ANY package, including the Pro, MegaPAK, UltraPAK, UltraPAK+, and Audiophile Edition.
New! Xtra Styles PAK 20 for Band-in-a-Box 2025 and Higher for Windows!
Xtra Styles PAK 20 for Windows & Mac Band-in-a-Box version 2025 (and higher) is here with 200 brand new RealStyles!
We're excited to bring you our latest and greatest in the all new Xtra Styles PAK 20 for Band-in-a-Box! This fresh installment is packed with 200 all-new styles spanning the rock & pop, jazz, and country genres you've come to expect, as well as the exciting inclusion of electronic styles!
In this PAK you’ll discover: Minimalist Modern Funk, New Wave Synth Pop, Hard Bop Latin Groove, Gospel Country Shuffle, Cinematic Synthwave, '60s Motown, Funky Lo-Fi Bossa, Heavy 1980s Metal, Soft Muted 12-8 Folk, J-Pop Jazz Fusion, and many more!
All the Xtra Styles PAKs 1 - 20 are on special for only $29 each (reg $49), or get all 209 PAKs for $199 (reg $399)! Order now!
Note: The Xtra Styles require the UltraPAK, UltraPAK+, or Audiophile Edition of Band-in-a-Box®. (Xtra Styles PAK 20 requires the 2025 or higher UltraPAK, UltraPAK+, or Audiophile Edition. They will not work with the Pro or MegaPAK version because they need the RealTracks from the UltraPAK, UltraPAK+, or Audiophile Edition.
New! XPro Styles PAK 9 for Band-in-a-Box 2025 and higher for Windows!
We've just released XPro Styles PAK 9 for Windows & Mac Band-in-a-Box version 2025 (and higher) with 100 brand new RealStyles, plus 29 RealTracks/RealDrums!
We've been hard at it to bring you the latest and greatest in this 9th installment of our popular XPro Styles PAK series! Included are 75 styles spanning the rock & pop, jazz, and country genres (25 styles each) that fans have come to expect, as well as 25 styles in this volume's wildcard genre: funk & R&B!
If you're itching to get a sneak peek at what's included in XPro Styles PAK 9, here is a small helping of what you can look forward to: Funky R&B Horns, Upbeat Celtic Rock, Jazz Fusion Salsa, Gentle Indie Folk, Cool '60s Soul, Funky '70s R&B, Smooth Jazz Hip Hop, Acoustic Rockabilly Swing, Funky Reggae Dub, Dreamy Retro Latin Jazz, Retro Soul-Rock Fusion, and much more!
Special Pricing! Until July 31, 2024, all the XPro Styles PAKs 1 - 9 are on sale for only $29 ea (Reg. $49 ea), or get them all in the XPro Styles PAK Bundle for only $149 (reg. $299)! Order now!
XPro Styles PAKs require Band-in-a-Box® 2025 or higher and are compatible with ANY package, including the Pro, MegaPAK, UltraPAK, UltraPAK+, and Audiophile Edition.
Video: Band-in-a-Box® 2025 for Mac®: VST3 Plugin Support
Band-in-a-Box® 2025 for Mac® now includes support for VST3 plugins, alongside VST and AU. Use them with MIDI or audio tracks for even more creative possibilities in your music production.
Band-in-a-Box® 2025 for Macs®: VST3 Plugin Support
Video: Band-in-a-Box® 2025 for Mac®: Using VST3 Plugins
One of our representatives will be happy to help you over the phone. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday, and 8:00AM to 4:00PM PST Saturday. We are closed Sunday. You can also send us your questions via email.
One of our representatives will be happy to help you on our Live Chat or by email. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday; 8:00AM to 4:00PM PST (GMT -8) Saturday; Closed Sunday.
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean