PG Music Home Forums PG Music Product Forums RealBand RealBand 2016 Build 6 : list of styles to be rebuilt systematically ....

Hello,

It seems that it is necessary to rebuild systematically the list of styles at each utilization of RB.
Has somebody already faced that situation ?

Thanks

Daniel

Daniel
Do you mean each time you start RealBand, or each time you upgrade RealBand?

If the former: no. If the latter: yes.

Hello VideoTrack,

Thank you for your message.

It has to be done systematically, at each utilization of RB (realod, new song,.....°.

Daniel

Hmmm

I wonder if this is a privilege issue?

Are you running RealBand as Administrator?

Hello VideoTrack,

Thank you for your help and suggestion ....
Very unfortunately, it does not work.

Daniel

If "run as administrator" would fix this (follow my logic here), why would the default requirement be "run as administrator - yes" for a function that every single user ever needs? Since every single user ever and always should not be seeing the style list rebuild every time (I see it too when I start a fresh song) it would make no sense for PG to program in a tripping point like that to generate more support requests. That message is part of why I will never reset my cfg and ini files. That will ALWAYS require a style list rebuild. I called PG out on this and they had no clue why, when I see the number of styles I am supposed to see, I still get prompted to allow the style list to rebuild. Just another of the far too many bugs in 2106. We are spending more time looking for and applying band-aids than creating music. Crashing when clicking the stop button, bad display on chord sheets, anomalies when there are style changes and tempo changes within songs, the style list issue, the multi-riff function creating MIDI files when that option is turned off.... this is all stuff that should have been caught in alpha testing before it even went out for us to beat it up in a beta test. These are not obscure functions. This is every day use stuff.

I just tried it, I cannot copy that behaviour. Following the installation of the "6" patch it even did not request to build the style list after BIAB has already rebuilt it.

Hello Daniel,

No, that is not normal behaviour. What are the dates of your RealBand.exe and the \Data\bbw2.exe files?

Also, if you look in your bb folder, is there a file called RebuildStylePicker.txt?

Eddie, I think the suggestion to 'run as admin' was an attempt to understand/solve the problem, not a statement that RealBand requires this. The StylePicker should not be rebuilding every time unless something has changed (installed new styles etc). If the same thing is happening to you, then could you also answer the questions above?

Bonjour Callie,

Thank you for your post.
I did not find the file RebuildStylePicker.txt ....that you are referring to.
Can you tell me a little bit more about that file ?

Merci

Daniel

RebuildStylePicker.txt is a file that, if placed in the bb folder, tells Band-in-a-Box (and RealBand) that it should rebuild the StylePicker automatically. Band-in-a-Box / RealBand does the rebuild and then deletes the file so that it doesn't keep rebuilding. There has occasionally been situations where the program is unable to delete RebuildStylePicker.txt for some reason, usually related to wonky permissions on the file or folder.

Also, I think there was an issue with an early RealBand build that caused the StylePicker to be rebuilt unnecessarily. Maybe install the build 6 update again just to make sure, and check Help | About.

FWIW, I think these two items from Andrew may be related somehow

and

(run as Admin changes permissions)

Though the suggestions from users here may seem strange sometimes, I believe they are offered with a sincere intent to help.
Testing narrows things down.
This is how things get solved.


I deal with this stuff every day, so it stuck out to me.

Okay, I will play the role of jerk again and present this logic.

"Maybe install the build 6 update again just to make sure, and check Help | About."

Why? Did the contents of that compiled set of instructions change while it sat on his hard drive? If it didn't work the 1st time, it won't work the 7th time, or the 19th 86th or the 137th. Programs have to run the same every time. This isn't a batch file that he could have edited. When you put 12x6 into a calculator, it can't be 71 the first time and then 72 every time after. It has to be 72 every time, just like that update has to result in the same update every time.

Reset. Defrag. Run as administrator. Update drivers.

Software should never have to be reset. If it does there are bugs.

Defrag is worthless as far as RUNNING programs. It only matters to make files stored on a drive contiguous and they load into RAM a millisecond faster.

Run as administrator means nothing to a computer unless the program in question needs permissions to access administrative level operations on a computer. A DAW does not, and RB/BIAB has NEVER needed to be run as admin.

Most of the people saying to update drivers don't even really know what drivers are or what they do. NEVER update a driver just because there is a new one available. Not broke/don't fix is the rule with drivers.

The fact that user after user is reporting problems that never existed until 2016 should be the biggest red flag in history of red flags. Anything resembling software rollouts that I have been involved with included a lab with 50 or more computers configured with every possible combination of OS and hardware we could think of. Some stations ran fine. Some did not. Those that did not showed us what to fix. This is really irritating. I understand that sporadic and intermittent problems are hard to troubleshoot, but suggesting things like running an update again and such is like telling someone to change the turn signal fuse when their brakes start to squeal, the obvious reference being that the turn signal fuse has nothing to do with the brakes.

I know I sound like I am being deliberately difficult, but I have been at computers a very long time and I know when an issue is hardware and when it is software. If the computer has run 2013, 2014 and 2015 they have all run fine (like in my case) and issues surface with the installation of 2016, the computer is not the problem. My Focusrite driver did not suddenly go bad at exactly the same time I installed 2016. More like the issue is that 2016 does not interact with the Focusrite drivers correctly. I had to go back to MME drivers, which I despised, just to get 2016 to work without crashing. That should NEVER be the case.

I'm done with this. Not even going to come back and read anymore.

Hello Eddie,




The reason is, simply because I want to be convinced that he is running the program with the latest .EXE's. Because I remember that there was a problem similar to what he describes in an early RealBand build.

I know that it says build 6 in the title of this post, but there are a lot of possibilities

- perhaps he installed a patch to his C drive and is running RealBand from his external drive.
- perhaps we made a mistake in an install and didn't include the latest bbw2.exe in the data folder.
- etc.

So I'd just like to eliminate the simplest things first. So yeah I agree with you, updating drivers etc etc. not relevant to the discussion. It's probably a bug, and we need to find a way to reproduce it.

Hello,

I installed Realband patch (6)today. When I go to StylePicker the Quick Play button is missing. When I double click on a style from the list I get: "Access violation at address 005E0D2E in module BBW2.exe. Read of address 0000025C at 005E0D2E."

I have the EverythingPak on an external hard drive.

I reinstalled build (6) and the issue is still there.

The About Box shows version 2016 (6).

Not sure what is going on but it looks like a bug to me.

It looks like this has been an issue for over a week.

Any ASAP help from PG would be appreciated.

Did what you said. Rebuilds every time.

Hi VoxBox
Yes, this issue started with release 6 and was reported to PGM on April 18th, including detailed steps that demonstrated the problem. Several members reported the same bug.

To my knowledge, Nothing has still been done to resolve this.

Hi VideoTrack,

Thanks for your input. I was going crazy for a while.

I may go back to the previous version if its possible.

For the next "update" I am going to wait for the build to "stabilize" before I install it.

Do you have the same issue?

Thanks again:)

Yes, my system also broke with release 6. I'm somewhat surprised that nothing has been done still to resolve this.

WOW! You too!

When I went to WINDOWS 7 Control panel / Programs Uninstall I saw BIAB but not RealBand.

So can you uninstall just RealBand or is RealBand "joined at the hips" with BIAB?

If this is the case it is not a good omen:(

I don't think Real Band registers in Windows. One of the prop heads can answer that better than I can. I know I had to manually associate seq files with Real Band. It was not set as a default program association by Windows.