The support guys can't replicate this error.

When I generate a Real Track, and remember I use Real Band, if I don't like the track, I can remove it with Track ==> Remove track.

However, if I try to get rid of it by using an undo, either from the pulldown or a ctl+z, I get a memory exception error. Yet when I say "OK" to the error box, the software performs the function. I get that same error condition on both computers. They can't replicate it on one!!

Can a few of you guys try that and see if undo to remove a generate track gives you an error?

One other thing to know is that my process is

Create the real track.
Play the song with the new track to decide if I like it or not.
Ctl-z to undo the track generate.

Exactly like that with no tweaking to the track. Just create it, play it, kill it.

So I:

Create the real track from a chord chart I input. I did not generate a style.
Play the song with the new track to decide if I like it or not.
Ctl-z to undo the track generate.

Exactly like that with no tweaking to the track. Just create it, play it, kill it.

Repeated creating a RT 4 more times and ctl-z undid the generated track each time without any error messages.

What I did not do is attempt this with a file originally created in Biab. You did not stipulate how your file originates. I will open a Biab sgu file and create a RT and report back.

REPORT BACK: I imported a Biab sgu file, played it to the end.
Generated a new RT, generated, played and used ctl-z to undo and the undo command worked with no error message.

Selected a new RT, generated and used ctl-z to undo before playing and the undo command worked with no error message.

Wow. And I get the error on 2 out of 2 computers. Strange. Might be an Ohio thing....

Yeah, I'm thinking your ground elevation.

This is the error. 2 things are strange. 1 is that it happens on 2 computers. 2 is that the memory register where the error occurs is always the same (different on 2 computers, but consistent on each computer).

This time to be sure of not having a memory conflict I rebooted so there was nothing resident in memory other than the OS and other native files. The happens with run as administrator both selected and deselected. Whether I use the pulldown menu to undo generate track or the ctl+z shortcut.



Yet nobody else seems to be reporting this. I have been deeply into computers since 1981 and I have NO idea what would cause this to happen to JUST me. If it was one computer I would replace the RAM and test, but it's both. One is an i3 and the other is an i7, both Dell. And I can't deliberately cause an error condition like this in any other software on the computer. Photoshop, MS Office, Audacity, Paint.... Also worth noting that if I OK the error, the program performs the command and goes on as if nothing happened, so it is not performance hindering. Just user annoying.

I am baffled, as is the support team. I am hoping someone else can recreate the error condition, which is why I posted, not to call out the support team.

Real Band, Charlie. Always Real Band for me.

"Real Band, Charlie. Always Real Band for me."

I know. I was trying hard and going through all the possibilities I could think of.

Since the issue is so far confined to you and your two computers you should examine all possible links between the two systems. My thought would be you are using two activations of the same download and are using the same RB.exe file.

If that's the case, I would discuss with PG staff providing a DL of that file again.

You can also change your default habit of using ctl-z to undo and use an alternate method that doesn't generate the error. If you have difficulty changing your habit, you can assign a consequence to using ctl-z that if you don't break the habit, you'll start dating again with intentions of a LTR. That should fix it good.

I was interested in your situation because I've incurred that error message before. In my case, it has always been Operator error because I would click on a command while RB was in process of executing a previous command or track generation. This does not seem to be what's happening in your case.

I'd truly rather hear "Brace for impact" before "Let's get married".

It is indeed 2 installs with the same serial, but I get three, so... and while there is a shared folder thing going on where I have the desktop of the upstairs computer mapped from the downstairs one to move those SEQ files, that's it for networking between the two. 1 is Windows 7 64 bit, the other Windows 10 64 bit, so not is it only 2 computers, it's on 2 operating systems. Using EDIT ==> TRACK ==> REMOVE TRACKS works just fine and does the same thing. Just strange to a longtime nerd that I am getting that error and hundreds of thousands of RB users are not.

Eddie,

The log file indicates you are using RB 2016, and if that’s the version you’re using, then you can update to build 10 of RB 2016, which should fix the issue according to the update page.

Jeff, what is the date of that log entry that indicates 2016? I am on 2018 Ultra. But now that you say that, I wonder is when I bought 2018 I DIDN'T remove 2016 first and the rberror.log files remained? You may be seeing the oldest entry on that log file.

I think I better set a day aside to reload this thing from scratch. If that is the problem, I swear I will give up Rocky Mountain Oysters forever.

PS I have never had a Rocky Mountain Oyster in my life. Prairie Oysters to you guys up north.

Edit: I looked at that log file again and it did indeed start in 2016 but the latest entry is in May 2018..

It does say 2018 further down in the log.

I would recommend a fresh install....or maybe erase your Realband.ini and RB.cfg files and see if that helps first....before doing fresh install.