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 & RB2024 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 & RB2024 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.
... 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. Kawai MP6, Korg M50, Ui24R, Saffire Pro 40. AVL:MXE Linux; Windows 11; Win8.1: Scarletts BIAB2022 UltraPAK, Reaper, a bunch of stuff.
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 & RB2024 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 2024 Win Audiophile. Software: Studio One 6.5 Pro, Swam horns, Acoustica-7, Notion 6; Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus Studio 192, Presonus 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 & RB2024 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 2024 Win Audiophile. Software: Studio One 6.5 Pro, Swam horns, Acoustica-7, Notion 6; Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus Studio 192, Presonus 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.
User Video: Next-Level AI Music Editing with ACE Studio and Band-in-a-Box®
The Bob Doyle Media YouTube channel is known for demonstrating how you can creatively incorporate AI into your projects - from your song projects to avatar building to face swapping, and more!
His latest video, Next-Level AI Music Editing with ACE Studio and Band-in-a-Box, he explains in detail how you can use the Melodist feature in Band-in-a-Box with ACE Studio. Follow along as he goes from "nothing" to "something" with his Band-in-a-Box MIDI Melodist track, using ACE Studio to turn it into a vocal track (or tracks, you'll see) by adding lyrics for those notes that will trigger some amazing AI vocals!
Wir waren fleißig und haben über 50 neue Funktionen und eine erstaunliche Sammlung neuer Inhalte hinzugefügt, darunter 222 RealTracks, neue RealStyles, MIDI SuperTracks, Instrumental Studies, "Songs with Vocals" Artist Performance Sets, abspielbare RealTracks Set 3, abspielbare RealDrums Set 2, zwei neue Sets von "RealDrums Stems", XPro Styles PAK 6, Xtra Styles PAK 17 und mehr!
Add updated printing options, enhanced tracks settings, smoother use of MGU and SGU (BB files) within PowerTracks, and more with the latest PowerTracks Pro Audio 2024 update!
Download and install this to your RealBand 2024 for updated print options, streamlined loading and saving of .SGU & MGU (BB) files, and to add a number of program adjustments that address user-reported bugs and concerns.
Did you know... not only can you download your Band-in-a-Box® Pro, MegaPAK, or PlusPAK purchase - you can also choose to add a flash drive backup copy with the installation files for only $15? It even comes with a Band-in-a-Box® keychain!
For the larger Band-in-a-Box® packages (UltraPAK, UltraPAK+, Audiophile Edition), the hard drive backup copy is available for only $25. This will include a preinstalled and ready to use program, along with your installation files.
Backup copies are offered during the checkout process on our website.
Already purchased your e-delivery version, and now you wish you had a backup copy? It's not too late! If your purchase was for the current version of Band-in-a-Box®, you can still reach out to our team directly to place your backup copy order!
Note: the Band-in-a-Box® keychain is only included with flash drive backup copies, and cannot be purchased separately.
Handy flash drive tip: Always try plugging in a USB device the wrong way first? If your flash drive (or other USB plug) doesn't have a symbol to indicate which way is up, look for the side with a seam on the metal connector (it only has a line across one side) - that's the side that either faces down or to the left, depending on your port placement.
Update your Band-in-a-Box® 2024 for Windows® Today!
Update your Band-in-a-Box® 2024 for Windows for free with build 1111!
With this update, there's more control when saving images from the Print Preview window, we've added defaults to the MultiPicker for sorting and font size, updated printing options, updated RealTracks and other content, and addressed user-reported issues with the StylePicker, MIDI Soloists, key signature changes, and more!
A few excerpts:
"The Tracks view is possibly the single most powerful addition in 2024 and opens up a new way to edit and generate accompaniments. Combined with the new MultiPicker Library Window, it makes BIAB nearly perfect as an 'intelligent' composer/arranger program."
"MIDI SuperTracks partial generation showing six variations – each time the section is generated it can be instantly auditioned, re-generated or backed out to a previous generation – and you can do this with any track type. This is MAJOR! This takes musical experimentation and honing an arrangement to a new level, and faster than ever."
"Band in a Box continues to be an expansive musical tool-set for both novice and experienced musicians to experiment, compose, arrange and mix songs, as well as an extensive educational resource. It is huge, with hundreds of functions, more than any one person is likely to ever use. Yet, so is any DAW that I have used. BIAB can do some things that no DAW does, and this year BIAB has more DAW-like functions than ever."
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