Percussive organ plays Ab2 and A2 wrong
Reported version
3.2
Priority
P2 - Medium
Type
Functional
Frequency
Many
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
When you play the Purcussive Organ on note G#/Ab2 and A2, they sound way too high, like D5 and D#/Eb5.
Attachment | Size |
---|---|
Organ_Ab_and_A_problem.mscz | 7.29 KB |
Fix version
3.3.3
Comments
Confirmed. It seems like not just the usual issue of overtones being too pronounced, it seems like just plain the wrong pitches, just for those two notes.
In reply to Confirmed. It seems like… by Marc Sabatella
Yes,
Root key forced to 0 (zero).
The editor may have accidentally touched that field.
In reply to Yeah, Root key forced to 0 … by Ziya Mete Demircan
Spot on Ziya Mete Demircan. 'No sound' problems with a SoundFont are usually related to the root key, and the preset (or instruments) key range of notes. You can use Polyphone to fix this easily, until a new release of the SoundFont comes out.
In reply to Yeah, Root key forced to 0 … by Ziya Mete Demircan
Ugh, when accidentally clicking to edit a field and then clicking away, Polyphone puts a value in the field rather than leaving it blank. I'm guessing this must have happened when I mass moved all root key data from the instruments to the samples. It will be fixed in the next version.
In reply to Ugh, when accidentally… by s.chriscollins
Yes indeed s.chriscollins: it seems you need to be careful and watch exactly what Polyphone puts into its value fields before your commit your changes. It looks like 'zeros' ('0's) can be inserted into blank fields when that's not exactly what you mean. The solution/workaround is to check every input field in Polyphone and confirm it contains what you mean before you commit the screen to the file, so to speak.
I've found this as a general rule with Polyphone: check every field to make sure it contains exactly what you need (e.g. blank vs. '0' for instance) before committing your change.
Tricky little things to be aware of, but nothing you can't sort out once you know what's going on - just make sure your final screen contains the exact values you want for your sound fount before you commit your changes to the file.
Came up again in #296484: Wrong note come out on A2 in bass key with percussive organ and others organs
MuseScore General: https://drive.google.com/file/d/1AdZCUWaKSqsLDBJ_Kn7NroAkJXph-Eee
and MuseScore General HQ: https://drive.google.com/file/d/1Bf1dMXljZQT___XxooiBrC9D06bRYu-p
Still happens in MuseScore version (64-bit): 3.3.2.8849, revision: 492d7ef
That's why this issue is still open ;-)
Seems fixed, at least I get the new 1.8 soundfont when building myself and the PR builds on Transifex and AppVeyor do too. So it'll be fixed in 3.3.3 (and will be in the next development build).
HQ soundfont (for updating via resource manager) will follow shortly
Got fixed for 3.3.3, but that fix got reverted for 3.3.4
In reply to Got fixed for 3.3.3, but… by Jojo-Schmitz
Because of the soundfont downgrade?
yes
the revert got reverted after some discussion on Telegram
Automatically closed -- issue fixed for 2 weeks with no activity.