musescore / musescore/MuseScore

Drawbar and Detuned Organs 1 and 2 are still one octave too low in MS Basic.sf3

Open
#23,659 30 comments 1 reaction 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Jul 17, 2024.

P2 playback
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

General playback bug

Description with steps to reproduce

All electronic Hammond-style organs should be one octave below concert pitch, as they are in other GM soundfonts.
Drawbar and Detuned Organs 1 and 2 as supplied in MuseScore are a further octave lower than that.

Supporting files, videos and screenshots

organ.zip

What is the latest version of MuseScore Studio where this issue is present?

4.3

Regression

No.

Operating system

Windows 10, but probably all

Additional context

I posted about this issue back in this post from 2021:
https://musescore.org/en/node/326427
and commented in this 2017 thread as well:
https://musescore.org/en/node/163756#comment-1104115

Harmonic analysis was performed.
Proof was given, complete with screen grabs and how to reproduce.

This is still the case with the newest version of the soundfont included with 4.3.
It should be an easy fix.
Replace -24 with -12 in the transposition for the Drawbar Organ instrument in the soundfont (note: instrument, not preset or sample). Then re-save. I could do this easily if granted access to MS Basic.sf2 so there would be no quality loss.

Though one could, one shouldn't simply change instruments.xml, because then MuseScore would be wrong for correctly pitched soundfonts.

I should note:
Workarounds are available.
You can either edit the soundfont yourself (and lose sf3 sizing) or transpose within MuseScore, but the optimist in me wants it to be correct out-of-the-box.

Thanks

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.