I found what appears to be an anomaly in RealBand but maybe I don't have something configured quite right, or maybe this is fixed in a version of RealBand newer than mine. My Help About window says "2015 (8)". Could someone in the forum who uses RealBand check something for me to see if you see the same...

1. create a new RealBand song with a MIDI track (any synth)

2. on my system, the key defaults to "C", so if your default is otherwise, set the song's key to "C"

3. put the track in record, play a C major scale, stop recording

4. open the Notation window for that MIDI track and confirm that it displays the following:

B# (not C)
E, F, G, A, B each have a natural sign in parenthesis

5. save the song (SEQ file)

6. open the song file saved from last step and confirm that it displays the following:

C, D, E, F, G, A, B each display without sharps/naturals



If others DON'T see this happening on their system, could you let me know?

Thanks,
Chris

I do not see this ..
Nor have I seen it in the past, so I'm not sure what the cause could be. If all you have to do is Save the song to fix it, I'd suggest saving often.
<grin>
I'd help if I could. Maybe I have somehow.

Chris
There has always been an issue with enharmonic keys and this might be related.

See this post, or search the forum for other examples.

rharv,

Thanks for looking at this. What version of RealBand are you on? Perhaps your version is newer than mine and this problem has been fixed.

Thanks,
Chris

Yes I will have a newer version, and maybe a Beta version not released yet, but this issue has not been reported for others (to my knowledge) even during testing. I watch the RB issues pretty closely, for what its worth, and this sounds unique/new to me.
Also to my knowledge the Notation feature has not been touched (changed) in many years. PGMusic said years back that it is what it is; no plans to change it for now, so I doubt is has been an issue that was fixed with a newer version. (though they did add a new Font, but that wouldn't change the behavior).

So I'm assuming the issue you have is pretty unique, especially if it is only happening on one file you had someone else work on ..
I'd suggest contacting PGMusic support using the link at the top of this page (preferably Chat if available). They may be able to look at it and correct within a few clicks .. but if it is only with one specific file, I'm not sure.

Noel
I don't think this is related to the post you reference. The OP is using a major key and playing a major scale .. no key change or enharmonic scale issues should affect that.


(emphasis mine)
I assume the Event List also shows the note as a B# (?) If Notation was different than the Event List, that would be really weird.

rharv - I remember seeing this exact thing some years ago on my old Powertracks system. Unfortunately, I can't remember which version and build it was , but I do know it was running under XP. I'm not sure if it was corrected by an up-grade, or when I changed the OS to 8.1.

ROG.

FYI -

PG Music Support responded to me yesterday and says this was a bug that they fixed in the 2016 version (yea!).

However, they also said that they just retested my scenario, and a similar problem now exists in the 2017 version (boo!).

However, they said they have passed along the problem to the developers in anticipation of a patch to the 2017 version (yea!).

Chris

Interesting, as I am definitely using a recent 2017 version and did not see it.

Many of us are anticipating a 2017 update to be released soon. It has been a while.

Just checked:
It looks like I have 2017 (7) Release 0 on this machine, so I think it is the current one.
Since I didn't replicate the issue, maybe I did something wrong <grin>.
If they can replicate it, they'll fix it. That's been my experience.
Not sure what "a similar problem" could be. Maybe they found something else.

Hi rharv,

Thanks for the info on this.

PG Music Support said, "I recorded two octaves of a C major chord, and sharp signs appeared on both Cs and the first F. Just like before, the signs went away when the song was saved and reopened."

I appreciate your handling the beta testing on this. I'll probably be updating to 2018 (assuming they do a Christmas sale again this year) so it would be nice to have this resolved once and for all.

It's not a show-stopper, since saving/reloading fixes the display problem, but it is distracting until you do save/reload.

And as you would suspect, it affects all MIDI overdubbing, too, since as you re-record a section with the MIDI controller, everything new that you created in the overdub has the same sharps/naturals problem, until you save THAT change.

It's like a summertime fly that keeps buzzing the potato salad.

Yeah, I can see it being annoying.

If support can reproduce it, it will likely get attention. Maybe I'm optimistic, but if they fixed it once previously ..