PG Music Home Forums PG Music Product Forums RealBand "Problem running bbw2.exe" when initializing accompaniment

Tried to bring up RealBand for the first time (2024).

I get a small error box that says "Problem Running BBW2.EXE"

I click the OK of that box and a yellow message appears "Initializing accompaniment functions...Please wait..."
Then that goes away and the error comes back "Problem Running BBW2.EXE"

Click. Click. Several times.

A portion of 1 RT loads (there should be several).

What now?

hmmm...not had that here.

an idea..assuming you have the pg upak drive shipped...
run direct off drive...do you get same problem ?
or are you download only.

merry x

om

Hi Floyd,

Go to Options | Preferences | Song Generation | Paths for BBW....
Make sure that "Select path for Band-in-a-Box" is pointing to your 2024 Band-in-a-Box folder. This should fix the problem. While you're in that dialog, make sure the RealTracks and Drums are set correctly as well.

You can also access the paths folder from the toolbar (see attached image, bottom menu item). Normally RealBand will prompt for the paths when running RealBand the first time (and automatically fill in each path in that dialog from a special .txt created when BB is installed), so if the Select Folders dialog did not display when running RB for the first time, it's an unusual situation.

That did not fix it (but thanks!)

Hi floyd,

Given your experience with BIAB 2024 and that it was forcing the program to create new setup files that solved the problem, I suggest that you do the same with RB.

Try renaming REALBAND64.INI file and RB64.CFG to something like REALBAND64.INI.OLD and RB64.CFG.OLD. This will force new versions of those files to be created when you start RB. If the problem is not solved by doing this, you can always delete the newly created files and then return the original files to their original names.

--Noel

Why so early ?

Thanks.

Did Not work.

I have to click the below error message 7 times and then the program shows the picture below.

The Only reason I use RealBand (and what I'm trying now) is to generate harmonies for a vocal of a song I am working on.
In it's current state, it allowed me to import my vocal track, select it and bring up the harmony dialog.
I entered what I wanted there and then got the same error message.

floyd,

Out of curiosity (and if you can be bothered)... If you have the USB drive for your Audiophile version, do you get the same error if you Navigate to \Realband on the USB drive and then run REALBAND.EXE from there? If the option for location of Realtracks, Realdrums and BIAB comes up, point the program to X:\bb, X:\bb\Realtracks, X:\bb\Drums where X is the USB drive.

Regards,
--Noel

noel.

yep i suggested that upthread.
i dont bother installing on c drive like i once did as i find the shipped upak drive works great just operating off that. I just back up the shipped drive.
now the upak can be ordered on fast ssd even better.

with this 2024 release im gonna load upak onto el cheapo m.2 uber fast ssd and see the performance.
currently off upak drive bb only takes a couple of secs to load anyway according to the bb log off 2023 drive.

merry x to all.

om

Thanks for the suggestion. Noel.

I tried that.
Symptoms were slightly different , but basically, the same.
This time I was able to get the "send to support email" generated (had trouble with that in the earlier attempts).

Once I click through the errors, I've got a perpetually spinning blue donut (been at least ten minutes now...)

This is really very strange.

You've probably already tried this. I'll just mention it in case you haven't, though.

So that you can work on your song, it should be possible to open BIAB from the USB drive of a previous version of the program if you still have the drives. This would, at least, let you finish your song.

I just tried my drive from last year and Realband 2023 started and worked fine even though I have 2024 installed on my computer. Again, just make sure to point to the the program and the Realtracks and Realdrums on the 2023 USB drive.

Thanks for another suggestion, Noel (I don't know what we would do without you!)
I'll give that a try.
In fact, that gives me an idea I had not thought of. I miss the harmony function that got replaced. I think 2020 was the last time the old one worked. I might try the 2020 version to see if I can get the old harmony engine....
I'll let ya know...

Although I didn't use it too much, I like that old harmony function too.

floyd,

Something you might need to keep in mind is that unless you have updated the USB drives, the version of the program that they contain would be the first publicly released version. If something doesn't work right, it would pay to download the final update for that version of RB from the link below.

https://www.pgmusic.com/support.realband.htm

Installing it is straight forward, all that needs to be done is to set the paths for Realdrums, Realtracks and BIAB to the USB drive when you reach that part of the update installation.

--Noel

I connected the 2023 drive.
Loaded RealBand.
Loaded the song I'm working on.
Tried to generate. Got errors (yellow). They disappear too fast to grab. I assume they are saved somewhere, but I cannot find an error log.

Tried a different style (which did load). It got the same errors when I tried to generate.

BUT. I loaded the vocal that I want harmony for and the harmony function worked.

Since THAT is all I do in RealBand - I, at least, have a work around.

BUT. Something is rotten in the state of Denmark Florida.

Found the "display log" function:

Error #-7, Invalid trackNumber or RealTracks Soloist Number in line #21 is the first error I see.
You will also see I tried to load a style that did not exist (not sure how that could be, but not my concern at the moment).
Loaded a different style and continued...


- Acid info successfully written to D:\Recording\Metal\Harmony 2 - High 1 (1)_0.WAV [RealBand 2023.1.0 (64-bit), 12/19/2023 9:06:48 AM]
- Successfully rendered the file D:\Recording\Metal\Harmony 2 - High 1 (1)_0.WAV. [RealBand 2023.1.0 (64-bit), 12/19/2023 9:06:46 AM]
- Acid info successfully written to D:\Recording\Metal\Harmony 1 - Low 1 (1)_0.WAV [RealBand 2023.1.0 (64-bit), 12/19/2023 9:06:36 AM]
- Successfully rendered the file D:\Recording\Metal\Harmony 1 - Low 1 (1)_0.WAV. [RealBand 2023.1.0 (64-bit), 12/19/2023 9:06:32 AM]
- Converting file... [RealBand 2023.1.0 (64-bit), 12/19/2023 9:05:57 AM]
- Converting file... [RealBand 2023.1.0 (64-bit), 12/19/2023 9:05:57 AM]
- Converting file... [RealBand 2023.1.0 (64-bit), 12/19/2023 9:05:46 AM]
- Converting file... [RealBand 2023.1.0 (64-bit), 12/19/2023 9:05:46 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:05:01 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:04:51 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:04:34 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:04:34 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:04:34 AM]
- BBOutput.txt reported an error: Error=-7 (;Error #-7, Invalid trackNumber or RealTracks Soloist Number in line #22 :ForceBBRealTrack=2,4492,0,0,0,0,0) [RealBand 2023.1.0 (64-bit), 12/19/2023 9:04:34 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:04:33 AM]
- Typical tempo for this style is: 150 [RealBand 2023.1.0 (64-bit), 12/19/2023 9:04:15 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:53 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:53 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:52 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:52 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:52 AM]
- BBOutput.txt reported an error: Error=-7 (;Error #-7, Invalid trackNumber or RealTracks Soloist Number in line #21 :ForceBBRealTrack=2,4492,0,0,0,0,0) [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:52 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:51 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:51 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:49 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:22 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:22 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:02 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:02 AM]
- BBOutput.txt reported an error: Error=-5 (;Error #-5, Style is not found:_SWAGGER.STY) [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:02 AM]
- BBOutput.txt reported an error: Error=-5 (;Error #-5, Style is not found:_SWAGGER.STY) [RealBand 2023.1.0 (64-bit), 12/19/2023 9:01:01 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 9:00:56 AM]
- BBOutput.txt reported an error: Error=-5 (;Error #-5, Style is not found:_SWAGGER.STY) [RealBand 2023.1.0 (64-bit), 12/19/2023 9:00:56 AM]
- BBOutput.txt reported an error: Error=-5 (;Error #-5, Style is not found:_SWAGGER.STY) [RealBand 2023.1.0 (64-bit), 12/19/2023 9:00:55 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 9:00:55 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:52 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:52 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:52 AM]
- BBOutput.txt reported an error: Error=-7 (;Error #-7, Invalid trackNumber or RealTracks Soloist Number in line #22 :ForceBBRealTrack=2,4492,0,0,0,0,0) [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:52 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:51 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:21 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:21 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:21 AM]
- BBOutput.txt reported an error: Error=-7 (;Error #-7, Invalid trackNumber or RealTracks Soloist Number in line #22 :ForceBBRealTrack=2,4492,0,0,0,0,0) [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:21 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:20 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:04 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:04 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:03 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:03 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:03 AM]
- BBOutput.txt reported an error: Error=-7 (;Error #-7, Invalid trackNumber or RealTracks Soloist Number in line #21 :ForceBBRealTrack=2,4492,0,0,0,0,0) [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:03 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:02 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 8:59:02 AM]
- BBW2 init time in ms: 22770 [RealBand 2023.1.0 (64-bit), 12/19/2023 8:58:54 AM]
- Initializing accompaniment functions... please wait... [RealBand 2023.1.0 (64-bit), 12/19/2023 8:58:31 AM]
- PAIsStarted = false [RealBand 2023.1.0 (64-bit), 12/19/2023 8:58:29 AM]
- PAIsStarted=true [RealBand 2023.1.0 (64-bit), 12/19/2023 8:58:09 AM]
- Input & output devices are set in Windows to different sample rates. Input will be disabled. Please select audio devices that have the same sample rates, or visit Control Panel | Sound , right click on each device & set sample rate in advanced tab
- Registered Power Notifications:FPowerNotify=114187984 [RealBand 2023.1.0 (64-bit), 12/19/2023 8:57:33 AM]
**** New Session started at : 12/19/2023 8:57:33 AM [RealBand 2023.1.0 (64-bit)]

I wonder if some of the Realtracks, Realdrums or base style you used were from the later version of the program. That might create these kinds of errors. While SGU and MGU files are backwards compatible, I think that the more recent Realtracks/drums require a recent version of the program. Unfortunately, I haven't experimented with how the various version inter-relate. I'm glad you got the tracks you needed. To do that, only the chord sheet and an audio file is necessary. Generating the song is a useful bonus from an audio perspective but not necessary from a work perspective.

Hopefully someone from PG Music reads these notes of yours and helps connect the dots!

That MIGHT be a separate problem. So you are running RealBand 2023 to check if it works... and you are getting this error with the song you loaded in. Need to be careful here:

* Verify that the RealBand 2023 program is pointing to a Band-in-a-Box 2023 folder. Double-check the folder paths (Prefs button | Paths for BB and RealTracks), and then go into those folder paths in Explorer, right-click | Properties on the .exe and look at the version details.
* The log shows that it is build 1 of 2023, that needs to be updated before running your test.
* There is a SECOND log file that should have more information. You will find it in the bb folder path, in Data\Logs (bbw2_64_flashmessage_log.txt). This SHOULD show you all those messages that went by really quickly.
* Please send us the song file that triggers this error, and we can see if we can duplicate. Send it attn Andrew and refer to this forum thread.

Back to the original problem of loading 2024, that second log file I mentioned above would be useful here as well... Find it in the 2024 bb folder in Data\Logs

It might have been a mistake to include the 2023 errors in this thread.
I was using it just as a test.
We should probably focus on just the 2024 version - because so far, I can't use it for anything.


Some new info....

I created a new song in RealBand (instead of loading the SGU I had been trying)
The new song sort of worked, but errors flashed
I will send you the Log file.
It says that it can't find a RealDrums folder - but it loaded the RealDrum from the style I selected. And, yes, I set it to the right place. BIAB can find them...and RealBand seems to find them in spite of itself.

I'll also send you the problem SGU. It runs fine in BIAB.