Sorry, you are having issues with your MODX. As rare as that is, it is not impossible.

Let’s see if we can narrow down some of the facts, and see if we can find a cause. Once something breaks it usually remains broken, your problem appears to have fixed itself with a reset and is now broken again, which leaves room for a possible actual explainable cause, which does not involve some kind of component failure.

Can you describe in a bit more depth, the actual issue. Full volume on just some, or all of the C’s and F#’s,
Does it occur on both Factory Presets as well as the User and Library Performances?
For example, does it occur on the Factory “CFX Concert” Performance?
Did the failure occur on the same Song both times?
If so, what was the Performance?

You can see where I’m going... (It is possible to “program” the response you are getting, if Factory sounds are also behaving strangely, that confirms a serious problem..., if it does occur on Factory Performances as well as your custom data, then you should have it looked at by an authorized service center.

You were programming certain percussion sounds to always occur on the lowest F# in a previous post... I’m sure it’s coincidental that F# is now a problem? (Or is it?) As you know, a single Key in a Performance could actually be programmed to play. And it could be set to play at full volume - this is done typically, to trigger an audio clip, one shot event, a drum or percussion hit... Analog synth sounds are programmed to ignore velocity, so when triggered, they play at the stored output level. (We need to eliminate those possibilities).

Any way, we’d be glad to help you troubleshoot what we can... let us know. No detail you provide is too small.

I don't use any percussion - except for a handclap and that IS programmed to the last F# on the left. It is for all C's and F#'s up and down the keyboard - has nothing to do with any particular song - no idea about the CFX Concert setting (it should be noted that I brought it in this morning and set it up in my studio and everything works fine - but that also happened yesterday - you know what they say about hubris!) One thing that is germane - when I "capo" the keyboard - it is still the C and F# that have the issue. Not sure if this is important but the other problem I have (intermittently) and this is for all octaves - you can push E but then F won't sound - or conversely you can push F and E won't sound (I guess dissonance is not recommended or something) And When I use a Bb as a grace note - it wont stop playing when you let if go - now those two problems have not reoccurred since the factory reset so I hope that did it. But the velocity issue on the C's and F#'s makes the keyboard unplayable. I have ordered a second one from ProAudio Star - hopefully it will get here before next weekend but I still have tonight and tomorrow afternoon to contend with.

I brought it in this morning and set it up in my studio and everything works fine

Okay. You’re good to go then?
You never really answered my questions... but sounds like ...it fixed itself... I simply asked when you recall a Factory Performance like “CFX Concert” did the C’s and F#’s behave oddly or not? Did it only go weird on your own programs... it’s a matter of ROM or RAM. Next time, if and when it happens, call up a preset see if it behaves strangely, too.

I don’t follow what you mean by “capo” the Keyboard ... is your description saying the physical Keys C and F# remain having the issue. Or the musical Notes C and F# have the problem no matter what Key triggers them?

My point was - I thought it had "corrected itself" yesterday but clearly it hadn't as it came back in the 2nd song. As far as your CFX - I did answer your question - I said I didn't try that.. As far as "capo" I have a couple of piano setting in live set that are up two and another down 2 - when you are using those; the physical key C and F# still sound loudly even though they are not playing those actual notes. In other words, in case of down two - Bb and E. I only use Live Set so that's all I have to compare it to. Look, I love this rig - it's easy to use and adjust, and I just bought another one - but here I am 7 months into owning it and I'm having no end of problems - I might have to dig out my old and heavy Motif's - It's tough to play with confidence when you have no idea what's going to come out. I expect it to reappear this evening during my gig. As far as my "own" programs, I'm not sure what you mean but I think you mean a setting in Live Set - My problem with that, if it was something I did, it would work or not work - it wouldn't be intermittent.

As far as my "own" programs, I'm not sure what you mean but I think you mean a setting in Live Set - My problem with that, if it was something I did, it would work or not work - it wouldn't be intermittent.

I can see you don’t understand my questions. a Live Set can point to any Performance. Some that point to Presets, some that point to User.... they all point to either a Performance made by Yamaha (Preset) or one you have edited and stored to the User Bank.

Presets are in ROM.
User Performances are in RAM.
Corrupted ROM would be quite a bit more serious...

So saying you are accessing the Performance via the Live Set is not important information... because a Live Set could be pointing at the Factory data or some Performance that you made, named and Stored. Do you see the difference? Even if you don’t it could make a huge difference (is what I’m saying).

As far as intermittent... some things can seem intermittent when they actually are not intermittent at all...

Intermittent - well it's not doing it now but it was doing it last night - and you're correct I probably don't have the jargon correct. In Live Set - I have about two dozen tabs where I've taken a sound like Rock Piano or something like that and added two or three other set sounds from the Category Search - the only modifications I've made are Pitch (as in up an octave or down an octave) and EQ. I apologize if I I'm not explaining myself very well. I did not make anything new. I just combined things from Category Search under one tab in Set List. And the fact remains - I have numerous intermittent things going on - as in two notes will not play together (and that's a piano not something that can only play one note at a time) Keys and only specifici keys like a Bb - and on all Bb's, every octave, won't let go when you go to B natural. Also not doing it now and hasn't done it since I did the factory reset.

Intermittent - well it's not doing it now but it was doing it last night - and you're correct I probably don't have the jargon correct. In Live Set - I have about two dozen tabs where I've taken a sound like Rock Piano or something like that and added two or three other set sounds from the Category Search - the only modifications I've made are Pitch (as in up an octave or down an octave) and EQ. I apologize if I I'm not explaining myself very well.

It is okay, I can decipher what you are trying to say, on most things.

I did not make anything new.

Yes, you did. Even if that’s all you did, you created a User Performance. That counts! When you combine several “other set sounds from the Category Search” — you have created a new User Performance.

User Performance is the thing I’m trying to get you to recognize. A User Performance is one where you did something and your pressed [STORE]. You can see a list of your current User Performances by doing the following:
Press [UTILITY]
Touch “Contents” > “Data Utility” > tap the “Performance” Folder... the contents of your current User Bank will be listed. It will indicate how many out of the 640 locations you’ve occupied.

Also not doing it now and hasn't done it since I did the factory reset.

When something illogical happens or you can’t figure out what caused it, a Factory Reset will usually fix the problem. What I thought we were attempting to do here is figure out the cause of the problem.. I’m trying to see if any of the symptoms appeared on KNOWN programs (those made at the Yamaha Factory) or when the issue occurred does it limit itself to *your* custom made Performance data.

Actually what I'm trying to do is find if this keyboard is usable or not. I have the issue that it will play C's and F#'s and only those notes - in all octaves - at full volume, even if you only brush over the key. This rig is only 7 months old - it shouldn't be having so many issues. Right now at 2:39 EST I have to figure out if I chance taking this to the gig tonight or dig out my Motif's. Is there a fix for this - I'm really desperate here. Yes, it's not doing it right now but it did it Thursday night - then I reset it - but it started up again last night - now here this afternoon it's not doing it - but I'm asking your very plainly - would you trust it to not do it again? It's clearly not anything I've done to it - otherwise it would do it all the time. I have made 2 dozen new Performances and have them stored under set list - and on every one of them, this occurs. Have you ever tried playing while you were avoiding hitting those two notes?

Follow up - if it happens tonight - I'll switch over to CFX and see if happens there too - but if it needs to be fixed - what do I do - it's still under warranty - I live in zip code 33477 - last question - stupid one perhaps - I use a different sustain pedal at home than on stage - is there any correlation to what I'm experiencing and that?

Actually what I'm trying to do is find if this keyboard is usable or not. I have the issue that it will play C's and F#'s and only those notes - in all octaves - at full volume, even if you only brush over the key. This rig is only 7 months old - it shouldn't be having so many issues.

You are correct, it should not be doing that, no matter how old. Usually, keys that play at full volume are due to a broken (physically broken ) Key. This would NOT, however, fix itself with a Factory Reset. So you still have a mystery.

Have you ever tried playing while you were avoiding hitting those two notes?

That’s virtually impossible since one or the other appears is in every key, and they both appear in one Key (G). That’s untenable...

...but if it needs to be fixed - what do I do - it's still under warranty - I live in zip code 33477...

I would call one of the local music stores in your area and ask where they send authorized Synthesizer repairs to in your area. They would certainly know the best person in your area. Remember not all electronic repair shops necessarily are synth specialists). You can do your own research, additionally. The usa.yamaha.com site has a Service Locator (bottom of the page “Find Servicer” )... Identify the type of product (Synthesizer), Type in your Zip Code, and it will return several that are nearest you by zip code. Compare what the local stores tell you with your own search results. If they have “authorization” from Yamaha, and local shop’s recommendation, its a good bet you’ve found the right place. Sometimes it’s worth it to travel a bit to get the right shop.

You are well under warranty, (but only an authorized service center can make that official determination). Let us know.

I can’t really see an off brand Sustain pedal causing any of the issues you have described.

If I had this issue, I would be spending all my time with factory presets ( [CATEGORY SEARCH], change bank to "Presets" - not "All" or "User" ) and pick a preset that is velocity sensitive. "CFX & FM EP" is the first one in the list - so I'd tend to use that one. I'd play the heck out of it. Different days. Keep returning to it. See if it ever exhibits the same issues. Maybe switching to some other factory preset if I just can't get that one to fail. And after a long session of trying to get it to fail -- I will have either heard it fail or not. If it didn't fail, I'd try my user Performance that has failed before and see what it does. If that one fails, I'd switch straight back to the factory preset and see if it's failing.

Note that if the problem is programming - if you make a backup (X8A) file and load it into the new MODX - you'll "infect" it with the same programming issue. But if the new keyboard never exhibits this issue with your same user content - well, then you have a fairly big clue there.

I can't fathom a velocity problem that is intermittent and only affects 2 notes (although the same 2 notes in any octave) being a programming issue but riddle me this:

1. Problems occurred in outdoor venues
2. It's Florida in July
3. Last night I played indoors in AC
4. Not a hint of a problem

Are these rigs susceptible to heat and humidity? Has anyone else ever mentioned that?

Finally - thank you for your erudite responses - this site is a very helpful tool and I appreciate it.

When computer based chips get ‘confused’ or start acting illogically, it is best to just recognize that it got confused, Reset it and move on. I’m trying to help you troubleshoot to find a possible cause.

Because some of the things you’ve mentioned could be programming ‘errors’ and some clearly cannot be ... we can only count on you and your description for what happened (but apparently has now been cured by the Reset)... and since you are not 100% sure of whether it was a Factory program (ROM) or one that you’ve programmed (RAM), our confidence on the evidence you’ve provided is not enough to draw a 100% definitive answer...

We agree, it would be quite unusual for all the C’s and all the F# to do anything all together. But I’ve had folks play a Single Part that copied from a Multi Part Performance, and then not realizing what has happened, they report that notes are dropping in and out, randomly. Sometimes it’s the Bb’s other times it’s just seems to be the G’s... etc., etc., They swear it is completely random.

But in fact, they copied a Part that only responds to Velocities up to a set amount... 1-92, for example, every time they played a note above 93, of course, the note would appear to drop out (because the Part they copied only goes 1-92). They never figured that out... so is it possible for something to seem intermittent when it really is behaving properly? Absolutely. It’s worse when they copy a Part that the Velocity Range is like 60-90... ever try to play a sound with just a narrow range of Velocities... I’ve had folks who couldn’t strike the keyboard between these two values...

Can a note be programmed to play at full volume, from just a single Key — well, yes, you programmed a percussion sound to play from your lowest F#, you know that’s possible. Some combination of the three factors and we can’t eliminate completely pilot error (as unlikely as it is). But knowing if it is a ROM error or a RAM issue might shed light on the issue.

If a problem in RAM, then as Jason points out, you’ll just reload the issue when you restore your data. We should try to avoid that, or you might start thinking the problem is following you around.

Heat? Of course, like everything on this planet, the keyboard is affected by heat. It would need to be excessive, a human being would likely pass out before the Keyboard was affected. But say you left it the backseat of a car out in the direct sunlight — much like pets and children, you shouldn’t leave your valuables in that kind of oven. (I’m sure the tolerance is up to 130+ degrees F) but a parked car left in the sunlight can easily get that hot. You would play in those conditions (the Titanic musicians would’ve taken a break in those conditions).

BTW- For those who have never been to Florida in July, that translates to extremely hot and extremely humid...

I’d expect any musical instrument, acoustic or electronic, would find that brutal... As would a human. Now take the unit out of the oven, and play a gig in direct sunlight! Yikes... I don’t get involved in the testing of such things... (I play indoors whenever possible, and never put my gear where I wouldn’t go. Outdoors, you need cover — put it in your list of must haves).

But I tend to think the unit would simply shut down under such abnormal conditions... but that’s just a guess.

The fact that you had no problems last night, may have absolutely nothing to do on your issue... it could be that once RESET, you are good to go.
Much like a computer, every once in a while a RESET or reboot clears things completely.
Every once in a while know that you will need to calibrate your touch screen, whether it’s the one on your computer, your phone, or your Synthesizer. The main thing is to know how to reset your tool.

1. the Velocity problem occurred before and after reset - the reset did help out curing some other issues but the reset and the velocity issue seem to be unrelated
2. I still maintain that if the Velocity problem is intermittent - it's not something I "programmed" - so a part that only responds to a certain level would be seem to be not applicable here (just my opinion - you obviously know scads more than me)
3. The keyboard is not stored in a hot car so that wouldn't be germane - but I do play waterfront venues a lot - and yes there is cover. I've lived 36 (out of 68) years here in Florida - I live in coastal Palm Beach County and I have never enjoyed a 100 degree day - certainly the heat index goes over 100 but never the actual temperature, also, if perhaps the drive to the gigs, caused it to heat up - I can't say that happens either as during sound checks, warmups etc., I never have the problem - I don't get it until I've played for a bit
4. I cannot make the velocity problem re-occur in my house
5. the handclap on my low f# - the volume is controlled by a slider like everything else - I'm not really certain what you were trying to explain to me there
6. Your comment about "pilot error" is likely - not the kind way you put it
7. When the velocity issue is occurring - just a brushing touch as you're reaching for the note beside it will trigger it to play at full volume
8. Turns out the warranty guy in our area - is a decent drive away BUT I know him very well - good guy good tech however I have no idea what I would tell him to fix - I surmise if he sets my rig up on his bench - it won't reproduce the issue
9. They say musicians my age - their most important stage placement is their fan - well I'm going to break the mold and point it at "Booker" (my name for this rig) and see if it makes a difference

Thank you again to both of you.