I've had BIAB 2018 for one week now. My setup is Windows 10 PC, 32 GB RAM, fast processor, running BIAB on the PGMusic usb hard drive.
The program has frozen twice so far. Just now I had a song playing. I tried to stop it but no methods worked: the stop icon, right clicking on the icon on the task bar & selecting close window, opening a new song, nothing worked. All menus and toolbars were locked. The tune just kept playing and playing.
Finally I had to run Windows Task Manager to force BIAB to close. All other programs worked fine.
The song is "Joy to the World", which I had downloaded from an Internet a few years ago when I ran the 2010 version.
After forcing BIAB closed with Win. Task Manager, I rebooted the PC. I opened BIAB after Windows finished loading.
I ran the same song. It played through to the end. I started play again and was able to use the STOP icon.
Maybe the first time BIAB was having an issue in the background. I had played other tunes and tried different styles, before the program locked in play.
I still wonder if anyone encountered this problem?
Do you run BIAB in "Run as administrator" mode? This is recommended by PG Music.
To do this, right-click on the start-up short-cut and select "Properties". Under the "Compatibility" tab, activate the option "Run as administrator". This will set the option permanently.
Note: this is different from logging in to Windows as Administrator.
It's also possible to select "Run as administrator" by right-click on the start-up short-cut and selecting "Run as administrator". This does not set the option permanently.
Thank you Noel. I set the BIAB shortcut icon as you suggested.
I also did the same thing for my iTunes icon, since it always needs to run in admin mode. I had been selecting Admin mode each time I ran iTunes. Now with this setup the program opens automatically. Genius!
Sadly it happened again tonight. My PC froze while one song kept playing, and wouldn't stop.
I'd been playing a few song files and trying different styles & instruments. Several songs worked perfectly, and then BIAB locked up. The song kept playing, non-stop, while no other features of the program seemed to work. All menus and icons were frozen. Finally I had to use Windows Task Manager to stop BIAB.
BIAB was running in administrator mode, on my Windows 10 PC. There were no error messages or other problems on the computer. Previous tunes played and stopped perfectly in BIAB until that last one.
I suggest you consider a few non-BIAB causes. For example, check your RAM. BIAB uses perhaps more RAM than most programs. Download MEMTEST and run it overnight.
And, there’s the ever-popular static electricity that shows up with low humidity in the late fall. Do you have a carpet under your chair? Spray it with static cling spray. Touch the metal frame of a desk before sitting down.
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.
Thanks again for your help; I appreciate it so much.
The songs I'm playing are almost all from Internet downloads. The downloads are older files, and are all MIDI. I previously played (or downloaded and not played previously) the songs through BIAB version 2010.
When I open these files in my 2018 version, BIAB suggests substituting RealTracks for MIDI, for better sound quality. I've been clicking on those messages to accept the upgrade from MIDI to RealTracks, and saving the changed files when I'n done with them.
I have a handful of songs that I created with 2018, and a couple with BIAB 2010. Most are downloads though.
There is one error message that appears every time I begin a BIAB 2018 session. It is error 9997, and appears to alert me about an error with my ability to record. Since I'm not trying to record yet, I haven't addressed these messages. Here is the full startup message from my FlahMessageLog file. It's long but maybe it will mean more to you than to my inexperienced eyes:
"Running Windows Notepad.exe to display file J:\bb\Data\Logs\FlashMessageLog.txt [2018.520.0, 11/4/2018 2:35:38 AM] Windows Audio Session error: Input and output sample rates must match. Audio input (recording) will be disabled. The error number is -9997 [2018.520.0, 11/4/2018 2:35:04 AM] Windows Audio Session error: Could not open stream. The error number is -9997 [2018.520.0, 11/4/2018 2:35:04 AM] Bootup was optimal, set to fast [2018.520.0, 11/4/2018 2:35:04 AM] Bootup time in millseconds =7,331 [2018.520.0, 11/4/2018 2:35:04 AM] Time to Count Plugins in ms =141. Plugins counted=20 [2018.520.0, 11/4/2018 2:34:59 AM]."
The error 9997 is not a serious one and it's due to using the WAS driver for audio (this is the "Windows Audio Session" driver you see listed in your log).
Have a look at the link below and setup your audio and MIDI drivers exactly as I show. These settings are the most sturdy for BIAB (they're the settings I use).
Thanks for your ongoing tech help. I began implementing your audio and midi settings, but ran into a small snag. In your diagram 2, covering midi driver setup, my choices are different than yours on the left hand side, under "MIDI Input Driver". My computer does not have the SB Adigy 2 2S MIDI IO option.
Is that your soundcard?
Two screen shots are enclosed. One shows my audio interface, an iConnectAUDIO4. The second screen capture shows my MIDI DSriver option dialog.
Thank you for posting the images, they help a great deal
In the above link I provided, I was meaning for you to follow the numbers and set everything according to the numbers. The Audigy is my indeed my soundcard and, as you can see, it's not numbered.
When I look at your MIDI set-up, using the numbers that I have in the above link, you have everything correct except for #3 and #7. If you go back to the link and compare my settings with yours, you'll see what I mean.
The most important thing is to set the audio driver to MME. Even though your audio driver settings show this, the link to the audio driver via your MIDI driver (#7 on my MIDI driver image) shows that WAS is still the audio driver. This should say MME.
In the MIDI driver setup, try clicking on #7 and then change the WAS to MME.
..........Just now I had a song playing. I tried to stop it but no methods worked: the stop icon, right clicking on the icon on the task bar & selecting close window, opening a new song, nothing worked. All menus and toolbars were locked. The tune just kept playing and playing.
Finally I had to run Windows Task Manager to force BIAB to close. All other programs worked fine.Have any of you experienced this issue?
It happened again!
This time was unique, in that it is a fresh installation, from a new BIAB hard drive.
The program is running in administrator mode. The audio drivers are set to MME, per Noel's detailed instructions.
The song playing was created and saved long ago. I had said yes to upgrading from MIDI to Real Tracks, as prompted by BIAB.
A conflict with another driver or program on my PC seems likely. I know I was running Google Chrome and possibly Microsoft Outlook at that time. The first time I might have had Spotify running at the same time, but am not certain. Spotify has had trouble sharing the volume with Ableton Live 10 Intro, before BIAB was installed. Ableton was not open this time though.
Any thoughts as to possible conflicts, on my Windows 10 PC?
Joel, sorry that you are experiencing this. It must be frustrating. However, I think it's reasonable to rule out Band In A Box as the prime cause, and as you say, there could be another conflict.
PGM staff can remotely monitor your computer (with your permission only) and possibly diagnose any potential causes.
My current recommendation would be to take that path. They are very expert in this area.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
Joel, sorry that you are experiencing this. It must be frustrating. However, I think it's reasonable to rule out Band In A Box as the prime cause, and as you say, there could be another conflict.
PGM staff can remotely monitor your computer (with your permission only) and possibly diagnose any potential causes.
My current recommendation would be to take that path. They are very expert in this area.
Hi Videotrack,
I agree, there must be a primary culprit other than BIAB.
Frustrating indeed. I'll consider your advice about PGM tracking my PC, but I'm always careful about protecting my privacy. I'll have to think about that.
They can only access with your consent, and you can see everything they do, including immediately halting the access at any time.
Only you can decide, but there has never been a known documented issue with PGM assisting by remote access. Alternatively, there are scores of people who had had their problems resolved through this method.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
When I asked, earlier in the thread, if the songs were MIDI-based or Realtracks, you replied with the following:-
Quote:
The songs I'm playing are almost all from Internet downloads. The downloads are older files, and are all MIDI. I previously played (or downloaded and not played previously) the songs through BIAB version 2010.
When I open these files in my 2018 version, BIAB suggests substituting RealTracks for MIDI, for better sound quality. I've been clicking on those messages to accept the upgrade from MIDI to RealTracks, and saving the changed files when I'm done with them.
I have a handful of songs that I created with 2018, and a couple with BIAB 2010. Most are downloads though.
Was it a downloaded file that caused the issue?
Downloading and running internet MIDI files in BIAB can sometimes cause freezes or even a sound that plays and drones on non-stop. This is why BIAB has a "PANIC!" button (see the image below -- if you need to switch screen views to access this option use CTRL+T; the shortcut is F12). This sometimes fixes the problems, sometimes not.
Also, when you mention that...
"BIAB suggests substituting RealTracks for MIDI, for better sound quality. I've been clicking on those messages to accept the upgrade from MIDI to RealTracks, and saving the changed files when I'm done with them."
...it is possible that you are not hearing those Realtrack generations. When one loads a MIDI into BIAB, all the tracks are loaded onto either the Melody track or the Soloist track as a mulitrack MIDI file. The other tracks in BIAB are reserved by BIAB for creating backings; they have nothing to do with loading MIDI files. When an external MIDI is loaded, though, by default, BIAB automatically disables styles. So unless you have enabled Styles after loading the MIDI file, you will not hear BIAB's accompaniment play.
I learnt along time ago that MIDI files on the 'net are hit and miss because I have no idea if the person who assembled the file was a MIDI expert or a MIDI novice. While these files can provide excellent starting places for songs, some MIDI files are definitely problematic and seem to be created by people who have no understanding of the ins and outs of MIDI.
Thanks for writing. Well I'm still learning about program features, and nuances of song files. I am only starting to understand some of the file attributes. I have very little experience with MIDI files. In the past I've relied on song downloads for my BIAB music.
A lot of those files have BIAB file extensions, but they are older songs. When I open these older song files in BIAB 2018, I get this type of message (copied from the LogText file in BIAB, under help / utilities):
"_PBALADM.STY is a RealTracks style that is available to sub for this MIDI style, with better sounds. Click here to load the style (or Press RealTracks button- Find Replacement to load it in or change options)."
I've been interpreting the message as saying the song is a MIDI file. Reading the log in BIAB I now see that the message refers to the style. However after I say yes to the Real Track, and I finish with the song, I am then asked if I want to save the change. I've been saying yes, to save the files.
I have some .MID songs but most of them have BIAB file extensions, and apparently MIDI styles. Here is a very small sample from my song picker list. Be gentle, I'm still learning
Just to be clear here on top of what Noel has told you. If you downloads are in fact old BIAB mgu and sgu files they are indeed BIAB file types , but because of their age probably used BIAB midi styles. This is why you get the notice. Quote: “I've been interpreting the message as saying the song is a MIDI file.”
This it is not! it as above a Biab file.
A midi file will have a .mid file type and behave as Noel says. Mike
Just to be clear here on top of what Noel has told you. If you downloads are in fact old BIAB mgu and sgu files they are indeed BIAB file types , but because of their age probably used BIAB midi styles. This is why you get the notice. Quote: “I've been interpreting the message as saying the song is a MIDI file.”
This it is not! it as above a Biab file.
A midi file will have a .mid file type and behave as Noel says. Mike
Hi Mike and Noel,
Thank you both for posting. I'm slowly getting over my knowledge gap, and am grateful for your help.
Joel: yes. BIAB is very memory-intensive. It might cause a problem other programs would not, and it could seem repeatable or random. You can rule that out.
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.
Nicely clear article. Do it in order. The first test is quick.
If you then run Memtest, let it run overnight. It runs until you stop it.
I hope your RAM tests fine. But when people report unexplainable odd behavior, it’s good to check. Now just go do it. It’s already taken longer to ask questions than to run the test.
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.
I hope your RAM tests fine. But when people report unexplainable odd behavior, it’s good to check. Now just go do it. It’s already taken longer to ask questions than to run the test.
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.
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.
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
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!"
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!
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!
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