Skip to content

Conversation

@lucyydotp
Copy link

Resolves: https://musescore.org/en/node/284198

This PR updates the steel pan/steel drum family to closer represent the range of instruments that actually exist.

There is quite a lot of variation in individual instrument ranges, as layouts are not standardised - each panmaker builds pans with a slightly different layout. I've used the amateur range for notes that are there on most pans, with less common notes in the professional range.

I should also mention that pan music is traditionally learned by rote and often isn’t notated at all, but when it is, it’s very common for pans to share parts (3 and 4 cello, and tenor/5/6/7 bass) and just adjust the octaves played based on the range of the individual pan. There are also more exotic pans that are too seldom used to warrant including here, for example single seconds, quadraphonics, and other bass variants (5/7/9/12).

I have also replaced the term "steel drum" with "steel pan" as this is what the instrument is more commonly known as. Steel drums tend to refer to the "raw" oil drum, which then gets turned into a steel pan. Additionally, an instrument made of more than one physical drum is referred to as a singular pan.

D Tenor
Also known as “high C tenor”, or “D lead” in the US. Despite the name, the tenor pan is closer to a soprano orchestral voice.
D4 to E6-F#6

C Tenor
Also known as “low C tenor”, or “C lead” in the US. A less commonly used variant of the D tenor, more popular in the US. Bands typically use either C or D tenors.
C4 to Eb6-E6

Double Tenor
F3 to Bb5-C6

Double Seconds
E3-F#3 to A5-B5

Double Guitar (or just "guitar" for short, single guitar does not exist)
C#3 - Ab4

Three Cello
Bb2-C3 to B4-C#5

Four Cello
Bb2 - C#5

Tenor Bass
F2-C4

Six Bass
Bb1 - Eb3

See also https://discord.com/channels/818804595450445834/939880479887327302/1439333125065806085.

  • I signed the CLA
  • The title of the PR describes the problem it addresses
  • Each commit's message describes its purpose and effects, and references the issue it resolves
  • If changes are extensive, there is a sequence of easily reviewable commits N/A
  • The code in the PR follows the coding rules
  • There are no unnecessary changes
  • The code compiles and runs on my machine, preferably after each commit individually
  • I created a unit test or vtest to verify the changes I made (if applicable) N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant