|
Log in to post
|
Print Thread |
|
|
|
|
|
RealBand
|
Joined: Apr 2013
Posts: 8,375
Veteran
|
Veteran
Joined: Apr 2013
Posts: 8,375 |
You may be correct there's no issue with the XML file. As I said, I have no experience with applying them in BIAB/RB or knowledge of using them in any manner. Also, XML files ability to be imported into PGMusic software is a fairly new feature so I was giving my best guess. Your issue with the two instances of INTERLUDE also led me in this direction. At the same time, I'm fairly confident from the various results obtained, there's no defect with RealBand regarding generations of 240 or 255 bars.
It sounds odd when I say it but I believe the issue is no more than something from somewhere has put a command around bar 240-241 since you consistently have the issue there.
You can easily select a few bars prior to bar 240 carrying the selection beyond 241 perhaps to bar 245 and manually make changes to the chords, replace instruments and only regenerate those few bars to see if completing a smaller size task makes a difference. You can do this to one instrument or to all of them at that section only.
To select a section of all the instruments -
Select the radio Snap To Grid Button in the upper left tool bar area.
Select a track, multiple tracks or all the tracks (to select multiple tracks use the control on any desired additional track or shift key between the first and last track you want to choose.)
Place your curser at bar 238 and Press F7
Place your curser at bar 245 and Press F8
The selected section (all tracks)should be highlighted in blue.
Right Click on the blue selected area or Select the large Generate Button
From the drop down menu - Generate\Regenerate All (selected region) (selected tracks) - The selection reads different in the large radio generate button than from the Right click method but the result should be the same.
Only the selected area should regenerate and apply the changes you made to the chord chart.
BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
You may be correct there's no issue with the XML file. As I said, I have no experience with applying them in BIAB/RB or knowledge of using them in any manner. Also, XML files ability to be imported into PGMusic software is a fairly new feature so I was giving my best guess. Your issue with the two instances of INTERLUDE also led me in this direction. At the same time, I'm fairly confident from the various results obtained, there's no defect with RealBand regarding generations of 240 or 255 bars.
It sounds odd when I say it but I believe the issue is no more than something from somewhere has put a command around bar 240-241 since you consistently have the issue there.
You can easily select a few bars prior to bar 240 carrying the selection beyond 241 perhaps to bar 245 and manually make changes to the chords, replace instruments and only regenerate those few bars to see if completing a smaller size task makes a difference. You can do this to one instrument or to all of them at that section only. Thanks, Charlie, for elaborating on your perspective on XML files. And thanks for your suggestion for me to experiment with the 240/241 bar boundary by making various changes to a small section of bars before and after this boundary and then regenerating those tracks. Unfortunately, I had tried this during one of my previous tests and repeatedly ran into the exact same problem. To substantiate my claim that there is indeed an issue with the 240/241 boundary during RB track generation process, I created a video that documents this entire scenario using a test song that I had created by manually entering the chords into RB's Chord Window. IOW, this test song was not created from opening a .XML file. You can watch this video on my Youtube channel at this link: https://youtu.be/khIKS_RAGHg
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2000
Posts: 21,965
Veteran
|
|
Veteran
Joined: May 2000
Posts: 21,965 |
muzikluver, Maybe try sending this to support via email, or Chat with them tomorrow. Since you can post the video file, PGMusic may be able to replicate or explain. https://www.pgmusic.com/support.htm
Last edited by rharv; 06/09/19 10:43 AM.
I do not work here, but the benefits are still awesome
Make your sound your own!
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
muzikluver, Maybe try sending this to support via email, or Chat with them tomorrow. Since you can post the video file, PGMusic may be able to replicate or explain. https://www.pgmusic.com/support.htm Thanks for the suggestion. I'll try emailing it to them first along with a link to this discussion.
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2013
Posts: 8,375
Veteran
|
|
Veteran
Joined: Apr 2013
Posts: 8,375 |
Thanks for posting the video. You're correct, there's nothing in the chords to cause the chord change and it's clearly there. Rharv's correct that it will likely be best to let support examine the file. I asked someone knowledgeable about XML files and they told me a chord change would be obviously visible and they did not think the XML file had any thing to do with your issue. This test you did seems to confirm that.
BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
I sent them an email several hours ago with links to both discussions about this issue (here and in the BiaB forum) as well as a link to my video. I'll let all of you know when they get back to me and what they say about all of this. Thanks for all the help!
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2013
Posts: 8,375
Veteran
|
|
Veteran
Joined: Apr 2013
Posts: 8,375 |
<<< I'll let all of you know when they get back to me and what they say about all of this. >>>
Please do. It's an intriguing problem.
Charlie
BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
Well, this afternoon I received a reply from Joe at PG Music to the email I sent to technical support yesterday. Before I share what Joe wrote to me, I'll share with I wrote in my email:
"Dear Technical Support,
I started using RealBand for the first time a few days ago to find out if it resolves the 255 bar limit in Band in a Box per the suggestion of another user in the Band in a Box forum. In the process, I discovered a problem that occurs repeatedly when RB reaches bar 241 during its track generation process using the BiaB engine. Rather than explain the problem in this email, I'll provide you with a link to the discussion I started in the RB forum on your website as well as a link to a video I created that documents this problem. I'll also provide you with a link to the original discussion I started in the BiaB form that resulted in my decision to try RB in order to create arrangements for two of my songs that exceed the 255 bar limit. Perhaps you could explain why this is happening and if there's anything I can do to work around it. Better yet, perhaps you could fix this problem without much effort. Thanks for your help!
(links included)
Tom"
And here is the reply I received:
"Thank you for contacting us. Although the limit for the song length in Band-in-a-Box is 255, generally speaking the closer you get to that point the more work the Band-in-a-Box engine taxes your computer and thus can create some pretty unwanted results.
As a general rule, the shorter the song the better it is. Even if you need to export smaller portions as a .wav then import them into another DAW to increase the length of it that would be a good work around.
Let us know if you require further assistance.
Cheers,
Joe
PG Music Inc.
Important Reminder: Please include all previous correspondence when replying to this message."
In my opinion, this is a strange reply. I contacted support about a bug in RB's execution of BiaB's engine to overcome the 255 bar limit, and support responded with a discussion on BiaB and a recommendation to use songs that don't get close to the 255 bar limit. Huh?
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2013
Posts: 8,375
Veteran
|
|
Veteran
Joined: Apr 2013
Posts: 8,375 |
Thanks for posting the update.
Interesting reply from Joe. It seem that although the RealBand program doesn't have a limit of 255 bars, the BIAB algorithm within the RealBand program becomes unstable when generations near the BIAB physical limit of 255 bars.
An analogy would be a rope designed to be safe under a specific load at 20' will not break when used at that load at the 20' length. The same rope braided to a length of 100' will still be designed to work at that load for 20' and may break when used at the 100' length.
It's a limitation of BIAB although it presents within RealBand.
BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
That's one way to look at it, Charlie, but I think there's more to it than that. On the one hand, RB doesn't even allow the BiaB engine to reach the 255 bar limit. This is why it only generates tracks up to 240 bars and then starts over with an additional 240 bars (or, in the case of my 320-bar song, an additional 80 bars). Although Jim Fogle's post on 6/8/19 above identified two gaps that occurred in his test song (one in all tracks at bar 240 and one in the base track at bar 272), my complaint isn't about the FIRST 240 bars. My complaint is about the SECOND 240 bars. More specifically, my complaint is about the BEGINNING of the second 240 bars, that is, the VERY FIRST bar if it doesn't have a chord assigned to it along with any subsequent bars that don't have a chord assigned to them as well.
In my test song and in a test song that Pipeline did (see his post on 6/9/19 in my BiaB forum topic "An idea to fix the dreaded '255 bar limit'"), RB inserted a C chord in the first unassigned bar, which from these two test cases appears to be a default operation within RB. Thus, on the other hand, RB's implementation of the BiaB engine for any unassigned bars in the BEGINNING of the second 240 bars is faulty because it doesn't account for the last assigned chord at the end of the first 240 bars. Or, as Pipeline put it in his post, "I would say that's a bug they need to look into as it's not stitching it correctly." This is why a glitch will sometimes occur at the 240/241 bar boundary as well as an erroneous chord change.
Regarding Jim Fogle's test, those gaps appeared only after he had changed all the rests, shots, holds in his song to whole chords. The gaps at bar 240 may have been due to a beat calculation error, which may correspond indirectly to the gap that appeared from bar 184 to bar 240 in one of my test songs with a 4/4 time signature when I used a 3/4 style. However, the gap in the base track at bar 272 could have been random and may have disappeared if he had regenerated that entire track or just a small section of that track surrounding bar 272. I say this because I had encountered a similar gap in BiaB on a finger picking acoustic guitar track in one of my songs that did not exceed or even come close to the 255 bar limit. When I regenerated the song, that gap went away.
CORRECTION: Jim Fogle's first gap appeared at bar 248, not bar 240. See my post below.
Last edited by muzikluver; 06/11/19 01:18 AM. Reason: Added a correction at the end
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
I just realized after checking Jim Fogle's post again that the gap in all the tracks of his test song was actually at bar 248, not bar 240. So, my theory about a beat calculation error for the first 240 bars is incorrect. So, perhaps this gap reinforces what I said above about RB's implementation of the BiaB engine at the BEGINNING of the second 240 bars.
I also did not point out that Jim Fogle's base track had a gap at bar 244 as well, but he didn't mention this in his post.
Last edited by muzikluver; 06/11/19 01:23 AM. Reason: Added additional statement at the end
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2003
Posts: 8,021
Veteran
|
|
Veteran
Joined: May 2003
Posts: 8,021 |
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Dec 2002
Posts: 12,017
Veteran
|
|
Veteran
Joined: Dec 2002
Posts: 12,017 |
muzikluver, I suspect you now can more appreciate what the term "baggage" means. 
BIAB – 2025, Reaper (current), i7-12700F Processor, 32GB DDR4-3200MHz RAM, 1TB WD Black NVMe SSD, 2TB WDC Blue SSD, 1TB WD Blue, 2 TB SK NVMe, 6 TB External, Motu Audio Express 6x6
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
muzikluver, I suspect you now can more appreciate what the term "baggage" means. I sure can! Obviously, as Bob (jazzmammal) pointed out, "RB isn't perfect," and I never expected it to be perfect. I just didn't know what types of issues I would be running into. This forum contains plenty of posts about such issues. Of course, BiaB has its own issues as well. But it's still a great program, and RB has the appearance of being a great program for its primary intended use as a DAW. I just haven't used it enough yet as a DAW to know that for sure from my own experience and may never know that because of my limited DAW needs.
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Dec 2015
Posts: 1,114
Expert
|
|
Expert
Joined: Dec 2015
Posts: 1,114 |
HI
Just a thought to stop the first chord in a new song coming up as C just set the key sig of the song to the chord you want.
However if you want to start on a note in a key that is not the tonic that is a problem.
But you can always change the first chord yourself anyway.
Starting a new version of song for part 2 to stitch on as a wav, I guess you would need to end part one on a key signature bar before it reaches its critical bar number for you.
At a point that makes musical sense of the arrangement currently generated.
Then create part 2 set to that key sig. the problem then being you may have to regenerate multiple times to come up with same arrangement that the software came up with in part one.
You may well struggle here a bit as what was say bar 220 of a song in part one
In your part two song will be back at bar one and may well get treated as an opening phrase, and therefore not sit well, with where the arrangement would have gone in a continuous generation of more bars.
You will also have to negate the count in at some point .
Seems a rather messy workaround to me and a bit hit and miss
Just my take
Mike
BIAB2021 UltraPlus,AsusN55S1Tbssd, W10/64,Akai EIEpro Yamaha CVP405,SquireStrat, CoolsoftVMidSynth Novatation Impulse61 Ctr kbd, Cwalk blab Kontakt http://mikesmusic.byethost16.com/
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
HI
Just a thought to stop the first chord in a new song coming up as C just set the key sig of the song to the chord you want. . . . Thanks for your suggestions and for joining the discussion, Mike. I think you misunderstood what I said. RB doesn't change the first chord in a song to C. It inserts a C chord into bar 241 if bar 241 doesn't already have a chord assigned to it. This chord won't be visible in the Chord window, but you'll definitely hear it in the arrangement. The quickest workaround for this is to simply insert a chord (the most recent chord that occurred prior to bar 241) into bar 241 before asking RB to generate all the BiaB tracks. However, even after doing this, a glitch will sometimes occur at the 240/241 bar boundary because of RB's attempt to switch to another chord first---probably the C chord.
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
I just sent Joe at PG Music support the following reply to his email:
"Hi Joe,
Thanks for your reply to my email and for the comments you made about the behavioral characteristics of the 255 bar limit in Band in a Box. While I do appreciate this information, I have to tell you that the email I sent you was not about problems I was having with this limit in Band in a Box. Instead, my email was about the problems I was having in RealBand because of how it had implemented the Band in a Box algorithm/engine to generate BB tracks for several songs that contained more than 255 bars. This is why I was using RealBand in the first place---as a workaround to the 255 bar limit. But rather than take the time to go into those problems in this email, I strongly encourage you to read through the discussions I started on the "255 bar limit" in your Band in a Box and RealBand Windows product forums. I also shared a video in the discussion on the RealBand forum that shows the main issue I had contacted you about. The links to this video and to both discussions are at the end of my original email below, but I'll provide them again here:
(links included)
Thanks for revisiting this issue.
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Dec 2002
Posts: 12,017
Veteran
|
|
Veteran
Joined: Dec 2002
Posts: 12,017 |
You are persistent, I will give you that, but what about buggy do you not understand? <said with a big smile  >
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Apr 2018
Posts: 266
Apprentice
|
|
OP
Apprentice
Joined: Apr 2018
Posts: 266 |
You are persistent, I will give you that, but what about buggy do you not understand? <said with a big smile > I sure am! And I hope that's a good thing---especially in this case. Are you asking me about "buggy" or "baggage"? I suspect that you're using both terms interchangeably. As I mentioned above, my primary intended use of RB is to generate arrangements for my songs that exceed the 255 bar limit and to save those arrangements as instrumental demos that I can share with other people. But after Pipeline suggested in a reply to my discussion of this issue on the BiaB forum that I check out the VST plugin for using two instances of BiaB within Tracktion, I'm thinking of pursuing that option instead of RB when I have the time to set it up and try it out, which I haven't done yet. Nevertheless, I'm not done pursuing a resolution of this issue in RB yet and won't until I'm sure that I've "beaten this horse" completely to death.
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
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Dec 2002
Posts: 12,017
Veteran
|
|
Veteran
Joined: Dec 2002
Posts: 12,017 |
But after Pipeline suggested in a reply to my discussion of this issue on the BiaB forum that I check out the VST plugin for using two instances of BiaB within Tracktion, I'm thinking of pursuing that option instead of RB when I have the time to set it up and try it out If you had fun exploring RB, you are going to have a blast with the BIAB VST. I can't wait for all the drama to come. ...until I'm sure that I've "beaten this horse" completely to death Not the first time I have heard this expression here in the forum.
BIAB – 2025, Reaper (current), i7-12700F Processor, 32GB DDR4-3200MHz RAM, 1TB WD Black NVMe SSD, 2TB WDC Blue SSD, 1TB WD Blue, 2 TB SK NVMe, 6 TB External, Motu Audio Express 6x6
|
|
|
|
|
|
|
|
|
|
|
|
Ask sales and support questions about Band-in-a-Box using natural language.
ChatPG's knowledge base includes the full Band-in-a-Box User Manual and sales information from the website.
|
|
|
|
|
|
|
|
|
|
|
Update your Band-in-a-Box® 2025 for Windows® Today!
If you’ve already purchased Band-in-a-Box® 2025 for Windows®, great news—a new update is now available! This update introduces a handy new feature: a vertical cursor in the Tracks window that shows the current location across all tracks, and more.
Discover everything included in this free update and download it now at https://www.pgmusic.com/support_windowsupdates.htm#1124
Video: Band-in-a-Box® 2025 for Windows®: Boot Camp: The AI Lyrics Generator
With Band-in-a-Box 2025® for Windows®, we've introduced an exciting new feature: the AI Lyrics Generator! In this video, Tobin guides you step-by-step on how to make the most of this new tool.
Band-in-a-Box® 2025 for Windows®: Boot Camp: The AI Lyrics Generator video.
Check out the forum post for more information.
Video: Band-in-a-Box® 2025 for Windows®: Using VST3 Plugins
Band-in-a-Box 2025® for Windows® now includes support for VST3 plugins, bringing even more creative possibilities to your music production. Join Simon as he guides you through the process in this easy-to-follow demonstration!
Video: Band-in-a-Box® 2025 for Windows®: Using VST3 Plugins
Join the conversation on our forum.
Video: Band-in-a-Box 2025 for Windows: Using The BB Stem Splitter!
In this video, Tobin provides a crash course on using the new BB Stem Splitter feature included in Band-in-a-Box 2025® for Windows®. During this process he also uses the Audio Chord Wizard (ACW) and the new Equalize Tempo feature.
Video: Band-in-a-Box® 2025 for Windows®: Using the BB Stem Splitter
Check out the forum post for some optional Tips & Tricks!
Congrats to Misha (Rustyspoon)…downloaded/installed a full Audiophile 2025!
Breaking News!
We’re thrilled to announce that Rustyspoon has made PG history as the very first person to successfully complete the download and install of the full Band-in-a-Box 2025 Windows Audiophile Edition (with FLAC files)—a whopping 610GB of data!
A big shoutout to Rustyspoon for stepping up to be our test "elf!"
Thank you for your support, Rustyspoon!
Band-in-a-Box 2025 for Windows Videos
With the launch of Band-in-a-Box® 2025 for Windows, we're adding new videos to our YouTube channel. We'll also share them here once they are published so you can easily find all the Band-in-a-Box® 2025 and new Add-on videos in one place!
Whether it's a summary of the new features, demonstrations of the 202 new RealTracks, new XPro Styles PAK 8, or Xtra Styles PAKs 18, information on the 2025 49-PAK, or detailed tutorials for other Band-in-a-Box® 2025 features, we have you covered!
Reference this forum post for One-Stop Shopping of our Band-in-a-Box® 2025 Videos - we will be updating this post as more videos are added!
Band-in-a-Box 2025 for Windows is Here!
Band-in-a-Box® 2025 for Windows 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 with savings of up to 50% on most upgrade packages during our special—available until December 31, 2024! 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 Windows 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!
|
|
|
|
|
|
|
|
|
|
|
|
Forums65
Topics83,517
Posts758,774
Members39,140
| |
Most Online3,932
Nov 19th, 2024
|
|
|
|
|
|
|
|
|
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean