Refresh my memory. I think a lot of folks "unfold the chord sheet to 1 large song for ease. Let's say I have a song bar 1-4 is an intro. The next 12 bars are a verse. Then there's another identical verse. If I don't unfold the chord sheet and use a repeat for verse 2 will that count as 12 measures or 24.
Neither 12 or 24. The song will have 30 or 32 bars. 4 (intro) + 12 (verse 1) + 12 (verse 2) equals 28 bars. Then there is the 2 or 4 bar ending. Then there are the bars that are doubled when half, double or triple time is used.
In my analogy the program has to "unfold" the chorus to keep track of the possible preference options (middle chorus variations). But the program could just as easily have multiple counters to keep track of both bars and repeats.
I believe repeats are available more to accommodate display of the chord sheet and song file printouts than how the program keeps track of the song timeline.
Of course, all of this is conjecture as I have no way of knowing.
I'll do a test and see. Jim I don't mean the repeat at the top.l mean if the chords are entered just like sheet music with repeats, coda, return to coda etc.I think 12 bars with a repeat at bar 16 to start at bar 5 would only "count" for viab purposes as 12 bars.Just a guess.
Right click on chord call and choose repeats,do el coda etc.So I believe you can have a song that is actually more then 255 bars but you only have 255 bars to enter chords. If you look at sheet music the song is always longer then the number of written bars.
I set, at the top 1.255 bars 2. 1 chorus 3. No repeats Entered some chords 4. Entered a repeat at 200 to start at 5. It did. 5. It then played to the end. 455 bars long. The song not the chord sheet
If musikluver had entered the notation in his xml file standard I believe it would have worked.
Unfortunately, Silvertones, if you're suggesting that I could have used repeats for the verses and choruses in my song so that the chord sheet wouldn't have exceeded 255 bars in BiaB or crossed the 240/241 bar boundary in RB (and thus avoid the erroneous chord change that occurred in bar 241), I have to inform you that your suggestion won't work for this song due to the differences that exist in each verse and each chorus. For example, the first line of the first verse lasts for four measures, but the first line of the second verse lasts for only three measures. There are also some places in each verse where the melody is slightly different because of the lyrics. The same is true of the choruses. The melody in the second chorus is slightly different from the melody in the first and third chorus. The only thing that could be repeated is the musical interlude that occurs between the first chorus and the second verse and between the second chorus and the third verse. But even doing this wouldn't have been enough to not exceed 255 bars in BiaB or avoid the 240/241 bar boundary in RB because these interludes aren't very long. Plus, attempting this would be very tricky.
However, your suggestion might have been possible with my other long song that I gave to my producer a couple of months ago, but I'd have to take a close look at it to be sure.
I agree RB is still screwed.Just wanted to let you know what I found with BIAB. Yes if all your verses/choruses etc are completely unique then you are correct. It wouldn't work.
<<< I agree RB is still screwed. Just wanted to let you know what I found with BIAB. Yes if all your verses/choruses etc are completely unique then you are correct. It wouldn't work. >>>
Unless you're working with recorded audio rather than generated audio. There is no bar limitation nor will there be any erroneous chord change with recorded audio even if it was originally generated in BIAB. RB functions as any other DAW when you use audio/midi and not BIAB generations that involve those two limitations when attempting a single render. In a single render attempt in RB, it's still screwed up.
If you enter chords for 12 bars then use the repeat/coda feature and tell it to repeat from bar 5 to bar 10 a 100 times then generate it'll play 1000 bars.It only generates bar 5 thru 10 but plays it over and over for 1000 bars.
This is where it all gets confusing; it depends on when you stop relying on BiaB features/apps Once you ask RB to behave like BiaB .. it does! Once you tell it explicitly not to, it doesn't, at least in my experience. Depends on what features you use and how.
Like I said right off, it can be confusing, but FTR I think Charlie was referring to RB and not BB in his post
I do not work here, but the benefits are still awesome Make your sound your own!
The original post by musikluver yes was about RB but then the issues with RB brought biab 255 bar limit into the picture. I was clarifying that biab only sort of has a 255 bar limit. Some do a song in biab as I said then import the sgu/mug into RB and see what happens.
If musikluver had entered the notation in his xml file standard I believe it would have worked.
This is correct if an XML file is capable to do repeats/codas, etc and BIAB reads the XML file correctly. Entering chords manually works as expected.
I manually entered chords and created a 32 bar BIAB template song and set it to repeat between 5-32 10 times to create a song structure to use. It has a 4 bar INTRO, VERSE1=8 bars, CHORUS=8 bars,VERSE2=12 and a 2 bar ending so when it plays, it exceeded the 255 bar limit of BIAB just as Silvertones indicated.
I saved the file and opened the SGU file in RealBand. I had used a midi style with RealDrums in my BIAB song, so I added three RealTracks to the RB song and saved the song in RB format, SEQ. The three RealTracks and RealDrum track generated all the measures without error and specifically, no erroneous chord at bar 240-241. The 255 bar limit was no issue whatsoever.
Regarding Muziluver's comments:
"I have to inform you that your suggestion won't work for this song due to the differences that exist in each verse and each chorus."
This is incorrect. I was able to edit the RB song without any issues.
"For example, the first line of the first verse lasts for four measures, but the first line of the second verse lasts for only three measures. There are also some places in each verse where the melody is slightly different because of the lyrics. The same is true of the choruses."
I was able to delete a measure from the first line of my second verse and the RealBand program deleted the measure and seamlessly crossfaded the preceding and following bars. I also edited the chord chart for verses and chorus's and regenerated those specific sections without issue and without having to regenerate the entire song.
"There are also some places in each verse where the melody is slightly different because of the lyrics."
This should be no problem. If the melody line is midi, that's quick and easy to edit. If it's audio, that section would have to be overdubbed (punched in/out) but again, only that particular section would require editing, not the whole melody track or all the lyrics.
"attempting this would be very tricky."
Not at all. Very easy and straightforward DAW editing of copy/paste and edit/regenerate Chord changes.
Whether the song originates in BIAB or RB, the key for this to work is to structure the song and break it into sections using Part Markers. In RealBand, the Part Markers can be named to match the song structure and each individual section can be highlighted\selected to edit the chord chart, tempo, key signature, number of measures and regenerated by each individual section quickly and easily. For instance, select the last measure of VERSE 2 and Edit\Delete Bars from Song and designate the number of Bars to Delete. Insert Bars works the same way. RealBand will automatically crossfade the preceding and following bars seamlessly. If you edit any chords in a section, Highlight the section and regenerate that section.
Just an FYI. I encountered editing,rendering and multi riff RealTrack issues using Silvertone's step by step instructions that included having repeats to be only one chorus. While the regenerations did not affect the midi tracks, the whole process was cancelled so no changes were made to the midi tracks either.
But, when I changed the Chorus repeats, I did not have any problems at all editing, rendering or multi riffing RealTracks or the midi tracks anywhere along the length of the song.
so as long as Muzikluver or anyone else can keep track of where they are in their song and use part markers to mark and navigate between intro, verses, bridges, Chorus's and outro's, they should be able to accomplish creating, structuring, editing and rendering their project in RB.
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
With the release of Band-in-a-Box® 2025 for Mac, we’re rolling out a collection of brand-new videos on our YouTube channel. We’ll also keep this forum post updated so you can easily find all the latest videos in one convenient spot.
From overviews of new features and walkthroughs of the 202 new RealTracks, to highlights of XPro Styles PAK 8, Xtra Styles PAKs 18, the 2025 49-PAK, and in-depth tutorials — you’ll find everything you need to explore what’s new in Band-in-a-Box® 2025.
Band-in-a-Box® 2025 for Mac is here, packed with major new features and an incredible collection of available new content! This includes 202 RealTracks (in Sets 449-467), plus 20 bonus Unreleased RealTracks in the 2025 49-PAK. There are new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 4, two new sets of “RealDrums Stems,” XPro Styles PAK 8, Xtra Styles PAK 19, and more!
Special Offers
Upgrade to Band-in-a-Box® 2025 for Mac with savings of up to 50% on most upgrade packages during our special—available until July 31, 2025! Visit our Band-in-a-Box® packages page for all the purchase options available.
2025 Free Bonus PAK & 49-PAK Add-ons
We've packed our Free Bonus PAK & 49-PAK with some incredible Add-ons! The Free Bonus PAK is automatically included with most Band-in-a-Box® for Mac 2025 packages, but for even more Add-ons (including 20 Unreleased RealTracks!) upgrade to the 2025 49-PAK for only $49. You can see the full lists of items in each package, and listen to demos here.
If you have any questions, feel free to connect with us directly—we’re here to help!
Cari amici
È stata aggerate la versione in Italiano del programma più amato dagli appassionati di musica, il nostro Band-in-a-Box.
Questo è il link alla nuova versione 2025.
Di seguito i link per scaricare il pacchetti di lingua italiana aggiornati per Band-in-a-Box e RealBand, anche per chi avesse già comprato la nuova versione in inglese.
Band-in-a-Box® 2025 pour Windows est disponible en Français.
Le téléchargement se fait à partir du site PG Music
Pour ceux qui auraient déjà acheté la version 2025 de Band-in-a-Box (et qui donc ont une version anglaise), il est possible de "franciser" cette version avec les patchs suivants:
Band-in-a-Box 2025 für Windows Deutsch ist verfügbar!
Die deutsche Version Band-in-a-Box® 2025 für Windows ist ab sofort verfügbar!
Alle die bereits die englische Version von Band-in-a-Box und RealBand 2024 installiert haben, finden hier die Installationsdateien für das Sprachenupdate:
Update Your Band-in-a-Box® 2025 to Build 1128 for Windows Today!
Already using Band-in-a-Box 2025 for Windows®? Download Build 1128 now from our Support Page to enjoy the latest enhancements and improvements from our team.
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.