Given that we now know that there are other files with the same filename (but different file extension), it may be an audio file that produces the error. You might try renaming the WAV or the MP3 file to something else and testing to see if you get the same error.
Tip: If a file with the same filename but a .WAV extension is in the same folder as the .MGU file, BiaB will try to load that WAV file.
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
I don't know where you are finding those "10 additional files", but I am sure they don't belong there. Did you create this files? What is the higher parent document names so we can find where your original folder is:
The original folder name of the original problem song is: 20 Beethoven Allegro (G major)
From the manual (yes, file names have cryptic meanings):
MGU Files: A Band-in-a-Box song called “My Song.MGU” will have the associated wave file called “My Song.wav.”
MGX Files: When a MIDI file is loaded onto the Melody (or Soloist) track, the Track Type for the Melody (or Soloist) gets set to Multi-Track. When the file is saved, the extension will be .MGX
The .SIB file is is a Sibelius music notation file.
The .MXL is a compressed music XML file.
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
I may do that. First I wanted to see if we are dealing with a corrupt file here. I think it would also be helpful (maybe not in this thread) to hear more about ‘corrupt files’.
Hi again Matt,
The info and tips I got from you and Simon remain at the top of my "to do" list but since my wife and I had to step away for a couple of days I've had to put executing those things off until at least the middle of next week. She insists that it is way past the time that my machine should have been backed up and cloned and I completely agree with her.
She remains out of town for now but I'm back on the Ponderosa alone trying to get caught up on the posts and other correspondence I've missed while I was away.
But getting back to the status of chasing down a solution to this nuisance window problem, I've got some great news! This case is almost over!
The info and 7-step suggestion list I got from Jim Fogle by way of Noel96 put me right on the trail of the culprit! I don't think the problem is with BIAB per se... It has something to do with the other 10 files that are in the same directory. I don't know exactly which file(s) yet but I know what to do to find out but I want to answer all of my correspondence first before I put those 10 suspects in a lineup and isolate the guilty file(s). As soon as I isolate the guilty culprit(s) I'll place the "Resolved" stamp on the thread and hopefully a virtual bottle of champagne!
I have to thank you and everyone here for your patience with me and putting up with the severe case of logorrhea I've developed over the years. Most of the time I contain it very well but when I get really frustrated, starts to get the better of me.
Anyway, thanks again for all of your input... you've been a great help!
If the issues occur on a song file you are actively working on, the song file may be slightly corrupt. If so, I may know of a solution that was originally proposed by forum member Noel96.
Save your existing song file under a new name.
Hi Jim
Although I only did one of the steps you suggested, I'm going to keep that whole process in my BIAB Affairs Folder for any possible future issue where it might be useful.
I'm really appreciative of all the effort and time that everyone spent on making comments and suggestions to help me out with the nuisance pop-up window issue I was experiencing.
Somewhere in this thread I stated that I knew the solution and answer was going to come from someone right here in this Forum community or the Support Team. Knowing how busy the PG Music people are, during this time of year in preparing things for their annual end-of-the-year new product release, I felt in my heart that the answer would come from this Forum Community before they had a chance to get back to me as the said they would.
It was definitely the input I got from you by way of Noel96 that actually put me on the trail of isolating the problem file. With the info that was revealed from doing only the first of the steps you suggested, I had a hunch that the problem was either the MP3 file or the wav file that was in the "problem directory". It turned out to be the wav file.
BAIB makes that wav file and for some reason it got corrupted and when I deleted it, BIAB simply made another one! It's kind of like when we have to sometimes delete the intrface.bbw file in the BB Preferences folder... the program just makes another one, the problem is solved, and the beat goes on!
After it made a new wav file, I pressed the Generate button 25 times in a row and there was no nuisance pop-up windows in sight! So, ding dong, the wicked witch is dead! This problem is solved!
From the manual (yes, file names have cryptic meanings):
MGU Files: A Band-in-a-Box song called “My Song.MGU” will have the associated wave file called “My Song.wav.”
I will say it again. This is just not so! There is no "My Song.wav" created when you simply regen a "My Song.mgu" file. I will go even further, if you were to intentionally Render the audio during playback, yes it would create a "My Song.wav" in the same directory, with the same name, but I always considered that a bug - not a feature, since it will confuse the heck out of new users at some point.
And finally where ever and what ever Utility tracks are doing with .wav files, I am the first to admit I have no idea.
Hope I am not hijacking this tread, but I am in a grumpy mood this morning.
sigh...i wish art would post the troublesome biab song file somewhere so the rest of us can test it for him. om
my songs....mixed for good earbuds...(fyi..my vocs on all songs..) https://soundcloud.com/alfsongs (90 songs created useing bb/rb) (lots of tips of mine in pg tips forum.)
... a "My Song.wav" in the same directory, with the same name, but I always considered that a bug - not a feature, since it will confuse the heck out of new users at some point.
It certainly confused the Hell out of me, as that .wav file will/can then be read back into BiaB and plays alongside the normal tracks, causing some very puzzling behaviours.
And if we new users don't know that's what happens, may not either be aware of that, so we may well not mention when reporting those strange behaviours.
Henry Clarke highlights this and some "good practices" to circumvent the problem in one of his (excellent, IMHO) BiaB tutorials. Ah ... here it is, there's an explanation of how he uses utility tracks and how to manage the .wav files.: https://youtu.be/XiPqQjISmb4?list=PLNGYsTA3YLQSZv0fgfcy0ukVF7zW2JSJu&t=320
Jazz relative beginner, starting at a much older age than was helpful. AVL:MXE Linux; Windows 11 BIAB2025 Audiophile, a bunch of other software. Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts .
From the manual (yes, file names have cryptic meanings):
MGU Files: A Band-in-a-Box song called “My Song.MGU” will have the associated wave file called “My Song.wav.”
I will say it again. This is just not so! There is no "My Song.wav" created when you simply regen a "My Song.mgu" file. I will go even further, if you were to intentionally Render the audio during playback, yes it would create a "My Song.wav" in the same directory, with the same name, but I always considered that a bug - not a feature, since it will confuse the heck out of new users at some point.
And finally where ever and what ever Utility tracks are doing with .wav files, I am the first to admit I have no idea.
Hope I am not hijacking this tread, but I am in a grumpy mood this morning.
Just so you fellers know..... it's not a bug. It can be useful to Mac users that don't have RealBand and users of both PC and Mac that have not upgraded to a version with Utility Tracks.
It's the only way for audio to be converted and be placed onto a Legacy Track in the BIAB Mixer. It's also an integral component of user Artist Performance Track process.
Here's a link to a post I made about Performance Tracks feature in February 2020.
From the manual (yes, file names have cryptic meanings):
MGU Files: A Band-in-a-Box song called “My Song.MGU” will have the associated wave file called “My Song.wav.”
I will say it again. This is just not so! There is no "My Song.wav" created when you simply regen a "My Song.mgu" file. I will go even further, if you were to intentionally Render the audio during playback, yes it would create a "My Song.wav" in the same directory, with the same name, but I always considered that a bug - not a feature, since it will confuse the heck out of new users at some point. ... Hope I am not hijacking this tread, but I am in a grumpy mood this morning.
Dear grumpy, you are indeed correct, and the manual (page 497) is indeed misleading. Moreover, I never thought the creation of the same-name WAV file in the background was a good idea especially as once created, it essentially interacts with the BiaB song file.
PS: Don't be grumpy It's not your style.
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
Interacts means it’s a good feature when intended.
Interferes might be a better description when not intended. The forum often has posts where users don’t understand why they are still hearing something they know they changed.
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.
Interacts means it’s a good feature when intended.
Interferes might be a better description when not intended. The forum often has posts where users don’t understand why they are still hearing something they know they changed.
Correct. 'Interferes' is a more appropriate term in this instance.
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
Interacts means it’s a good feature when intended.
Interferes might be a better description when not intended. The forum often has posts where users don’t understand why they are still hearing something they know they changed.
Correct. 'Interferes' is a more appropriate term in this instance.
Oh, I know you knew that. I'm more wondering, what do we do about it? Recommend a caution message if an audio file of the same song name exists?
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.
Oh, I know you knew that. I'm more wondering, what do we do about it? Recommend a caution message if an audio file of the same song name exists?
When anyone renders a wav file to disk he should be asked to name it and its location. Then if he wants to load it onto the audio track it should ask where is the file and what is its name. Once it is loaded and saved on a track it should remember it and load it automatically the next time the file is opened.
Oh, I know you knew that. I'm more wondering, what do we do about it? Recommend a caution message if an audio file of the same song name exists?
When anyone renders a wav file to disk he should be asked to name it and its location. Then if he wants to load it onto the audio track it should ask where is the file and what is its name. Once it is loaded and saved on a track it should remember it and load it automatically the next time the file is opened.
Pretty standard file and track management.
Well, except for the User Artist Performance Track function which does all of that automatically as part of an advanced freeze option as one of the many things it can do.
I suggest educating users to the feature is the best recommendation because knowing what it does solves more issues than it causes and once users are aware of it, there's no longer a problem with an 'unknown' track playing.
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.
Already using RealBand® 2025 for Windows®? Download Build 5 now from our Support Page to ensure you have the latest enhancements and improvements from our team.
PowerTracks Pro Audio 2025 is here! This new version introduces many features, including VST3 support, the ability to load or import a .FLAC file, a reset option for track height in the Tracks window, a taller Timeline on the Notation window toolbar, new freeze buttons in the Tracks window, three toolbar modes (two rows, single row, and none), the improved Select Patch dialog with text-based search and numeric patch display, a new button in the DirectX/VST window to copy an effects group, and more!
First-time packages start at only $49. Already a PowerTracks Pro Audio user? Upgrade for as little as $29!
Video: Summary of the New Band-in-a-Box® App for iOS®
Join Tobin as he takes you on a tour of the new Band-in-a-Box® app for iOS®! Designed for musicians, singer-songwriters, and educators, this powerful tool lets you create, play, and transfer songs effortlessly on your iPhone® or iPad®—anytime, anywhere.
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