If you are truly interested in the mathematics behind organ tones... while you are searching the Internet, add the term “mixture breaks” and read up on how organ tones work. It’s fascinating!

Fortunately, music is always in motion so little things like harmonic breaks, awful grinding noises and the naturally out of tune harmonics don’t prevent most humans from enjoying it. So much of musical mathematic and tone generation is a ‘bit disruptive’ when studied up-close — thankfully our ear/brain/heart are more forgiving and can relax and enjoy the overall result.

I'm not so sure. I do know about mixture breaks, but generally you can hear them subtly break back at points along the range. Here, it's a great clumsy schism when you cross C5.
I love the mosquito tone of Farfisa, but it's pretty disappointing that the mosquito flies away two thirds the way up the keyboard.

The F organs on YC are created not from samples or models but the FM synthesis engine as I've heard or thought.

IF it makes a quirky change somewhere up the scale then that would be by design because FM doesn't change for no reason unless it's programed to change.

I'll see if mine does the same thing although I've not noticed to listened for it before.

I listened to my F3 and the lower the frequency the more buzz whereas the higher the frequency the less buzz in the tone.

This is the characteristic of faster vibrations at higher frequency will be less obvious in the "buzziness" so I didn't otherwise notice anything annoying or a sudden change.

Mine was very gradual and sounded normal to me and if fact all higher frequencies sound very different from their lower tone counterparts. That's the nature of it.

Thanks David - just wondering, did you have the rotary speaker turned on when you tested yours?

For me, it only really happens when the rotary is off, and I'm using a vanilla F3 tone. Put the rotary on, and the issue becomes much less noticeable (but still somewhat there).

The difference can be heard even more starkly this way:

With the pitch stick set to range +12, play a melody in octave 5, but use the stick to push it up into octave 6.
Then release the stick and play the same melody in octave 6 naturally.

Sounds like 2 completely different instruments to me.

I have a similar issue annoying me, on most of the YC61's Rhodes piano voices. In several Rhodes voices, there's a group of 4 to 6 adjacent notes that have
a pronounced, substantial extra high harmonic "chime" like a tuning fork or a beat-up Rhodes with worn or misadjusted hammers. Does anyone else hear this little group of
notes that has a chime noise (not occurring on any of the other notes)? It happens on RD 74 Studio and several other Rhodes patches, in RD74 Studio, from B in second highest octave to E in highest octave. It happens whether you play soft or hard, and in all touch options. Real Rhodes in proper restored condition don't do that so it annoys me. Restored Rhodes have smooth consistent notes sounding essentially similar across the entire keyboard.

In several Rhodes voices, there's a group of 4 to 6 adjacent notes that have a pronounced, substantial extra high harmonic "chime"...Restored Rhodes have smooth consistent notes sounding essentially similar across the entire keyboard.

I don't have a YC to check this in particular, but in general, it is very common that sampled Rhodes (as with other instruments) are not created by sampling each key, but rather every 3rd, 4th, or 5th key, "stretching" a single sample to cover the multiple notes, which greatly reduces the sample memory required. The result is that, when playing a chromatic scale, you can often hear a tonal jump from one set to the next, even though it is not very noticeable when played in a full musical context. So when you hear a sonic characteristic that seems restricted to 4-6 keys, it is probably the sample of one particular sampled note on the source instrument that was stretched over that range.

Great to see this issue has been completely fixed in V1.2 😀

Was this issues fixed? Did someone document and test it? Just wondering.

@David it was the first thing I went and checked for after applying the update (it's been my pet gripe).

There was no mention of it in the release notes, but it's definitely fixed for me 🙂

One of those "minor fixes" line items that they never tell us about but good to know it's working right.