PROBLEM 1: SuperTracks
When I try to generate a Midi SuperTrack in RealBand I get this error message:
“Access violation at address 0000000000E6AEB9 in module 'bbw2_64.exe'. Read of address 0000000000000000”

When this message appears (with the header Band-in-a-Box – NONAME.SGU), another message in a yellow panel sometimes appears. It reads: “Playback already in progress. Play another song if message persists.” The Access Violation message still appears even if I play another song.
A Midi SuperTrack does generate, but it appears to be the same 3/4 track I was previously auditioning (1892: Piano, Solo-Accompaniment CountryWaltzJohn Sw 140 (John Jarvis).

When I look in my BB folder, I see this txt file: ” BBW2IsRunning”. It contains one line of text: “BBW2IsRunningTxt=1”
If I restart my PC (or close RealBand) this txt file disappears - but the original error message and the txt file reappears if I try to generate any Midi SuperTrack.

PROBLEM 2: RealTracks
For a while any RealTrack I selected generated in 3/4 time. No matter what style I choose, I got a waltz.
I rarely use Midi SuperTracks but since trying out a waltz Supertrack, I’ve had nothing but problems and now I’ve got problems with RealTRacks, which I use a lot.
I can live without SuperTracks but not RealTracks!
So far, I have tried:
• Re-installing Hi-Q Instruments for Sforzando
• Returning BIAB and RealBand to factory settings
• deleting Mysetup.dk and intrface.bbw (as instructed by PG Support)

I am running the latest versions of BIAB and RealBand and running both “as administrator”.

UPDATE: When I (again) reset BIAB and RealBand to factory settings, RealTracks worked normally again but Midi SuperTracks is still stuck in 3/4.
Any help would be greatly appreciated.

Thanks in advance,
Mike

PS I have also attached a screen shot of my BBW files from my BB folder.

OK, I'll ask the simple questions first just to eliminate them ..

Is your Realtrack Picker window filtered in any way?

Is the Meter defaulting to 3/4 when you click File - New ?
If so, do you happen to have a file named $OPTIONS.SEQ in your Realband folder?

/all of the above is a long shot in the dark, but at least it's a start
//if you want to get much more advanced; there is a file in the bb/Data folder named bbw2_RealBandLog.txt .. this appears to be the log of what happens in BiaB2 while running in RB.. with entries for bbw2_64exe and time stamps as well as reports.. if it is crashing this could lead to clues
///not sure of your computer skills (as to whether this may help), so thought I'd mention

Hi rharv, thanks for your response.
The Realtrack Picker window is only filtered by my previous instrument search (e.g. "Piano") but not by any time/meter factor.
When I click File - New, the default setting is 4/4.
I don't have a file named $OPTIONS.SEQ in my Realband folder.
I looked at the file bbw2_RealBandLog.txt but nothing stood out to my untrained eyes.
RealTracks now seem to be behaving ok, following my last factory reset.
For some reason Midi SuperTracks also seem to have escaped the clutches of 3/4 time and generate as ordered now - but with an error message (attached).
I'd love to get rid of the error message but at least I can use the Midi SuperTracks.
Thanks again,
Mike

Does that error what show up in the Log file?
Just curious.

I'd send that error message to PGMusic support as they may know what it means.
The Live Chat option at the top of the page may help jump start the request.

Hi rharv,
No, the error doesn't appear to be in the Log file.
I sent the original Windows Stack Trace Report to PG Music Support. They responded with various suggestions which I acted upon, to no avail.
I also sent a Word document to them of the Exception log containing pages of, according to the header, "detailed tech info" but Support was unable to fix the problem.
It looks like I'm stuck with the repetitive error message but at least RealTracks and Midi SuperTracks are generating correctly now.
Thanks for your suggestions. I really appreciate the help you regularly provide on this forum.
Cheers,
Mike

Thank you for the error report. We will look into this further.

Thanks Andrew.