Ocarina Ranges
OKay, so as an ocarinist, I need to mention something. Musescore has ocarinas as non-transposing, which is sometimes the case, kinda like how some brass instrument parts are occasionally written at concert pitch. However, usually, they're all written in treble clef by default. That's not a huge issue.
What is the bigger issue is you have the Bass as having the range of a contrabass, the alto having the range of a bass, the soprano as having the range of an alto. And nothing taking that soprano range.
This is a little odd, I know, as Alto is seen as the standard, and the fact that it starts at a piccolo's C (some can go down to A, or even G in rare instances) and it would be nice if this correction was just baked into the build.
Just for reference, the C Contrabass is from C3-D4 (B2-E4), the C Bass would be C4-D5(A3-E5), the Alto C is C5-D6 (A4-F6) and the Soprano C is C6-D7(A5-F7)
Double and triple Alto and bass are also fairly standard, but easy to quickly edit if the transposition and bottom range is already there.
If this could be worked on in a build, that would be awesome!
Comments
Probably no one who has worked on this knows much about the instrument, so your insight is appreciated Can you point to an authoritative reference to allow us to understand how this all works?
In reply to Probably no one who has… by Marc Sabatella
First, I play these instruments, and second, this is directly from The Ocarina Network. The "Noble, Focalink, etc." Is the terminology we use when talking to each other in ocarina forums. It's the most widely used language surrounding the instrument world-wide.
In reply to First, I play these… by AstralAstrid
Great, thanks! Are those ranges written or sounding pitches, then? And if written, which of them if any are sounding different? I take it it's the green column we should be looking at?
In reply to Great, thanks! Are those… by Marc Sabatella
The Bass is the only one written at Pitch. Sometimes the G, F, and Bb ocarinas are written at pitch, but not always. But altos are transposed at the octave, and sopranos at two ocatves, and the contrabass sounds an octave lower than written. It's also sometimes written in bass clef for some odd reason.
In reply to Great, thanks! Are those… by Marc Sabatella
I also looked at the 4.0 alpha 2, and the Soprano G and Soprano F are separate instruments from the Soprano ocarinas, rather than being a drop down like the others.
Thanks for bringing this to our attention. It's on my radar to investigate this after some other changes to instruments. I can't promise it'll make it into 4.0 but hopefully soon after. This source seem to corroborate your information about the ranges. https://pureocarinas.com/ocarina-keys-and-pitch-ranges
In reply to Thanks for bringing this to… by shoogle
I thought I would mess around with creating a custom template with some ocarinas with the proper range and octaves. I can set up the template, but I don't see in the manual how to save it to the custom template folder
In reply to I thought I would mess… by bobjp
See:
https://musescore.org/en/handbook/3/create-new-score#user-templates-fol…
In reply to See: https://musescore.org… by Jm6stringer
Thanks. I had already seen that. What I seem to not understand is how to get something into that folder. Probably simple.
In reply to Thanks. I had already seen… by bobjp
Just a perfectly normal "save" or "save as".
In reply to Just a perfectly normal … by Marc Sabatella
Thanks Marc. That works. Never having messed with templates before, I had no idea that they are just empty score files. I thought they where some special format. There is nothing in the manual about how to create a template. It starts out with where to put templates you create. I had to guess that it starts with a score I created. That's where I stopped because I didn't know what to do next. I few lines in the manual would have been all I needed.
In reply to Thanks Marc. That works… by bobjp
Well, the very first line under Templates just above the section on where to keep them says “A Template is simply a standard MuseScore file” - maybe you didn’t scroll up to see that? The link indeed was to a place a little farther up. But feel free to edit to clarify further. Note it doesn’t have to be empty; any score can serve as a template. New scores created will still be empty.
In reply to Well, the very first line… by Marc Sabatella
My initial search took me to the same place. I indeed did not scroll up and so I missed that sentence. I was expecting a section on "How to Create a Template". Not "A Template is simply a standard MuseScore file". No points for me :)
I want to bump this issue. Should be a quick fix.
I also made a separate post with a longer explanation of the ocarina range and naming issue: https://musescore.org/en/node/382361
In reply to I want to bump this issue… by bergmansson1
Bumping here won't help, instead file it on GitHub
In reply to Bumping here won't help,… by Jojo-Schmitz
I did a while back. Still hasn't been fixed.
In reply to I did a while back. Still… by AstralAstrid
Link?
In reply to Link? by Jojo-Schmitz
https://github.com/musescore/MuseScore/issues/27257
right here, from March
In reply to Bumping here won't help,… by Jojo-Schmitz
Is that how we do it nowadays? Is the forum only for straight up help questions?
It seems like an easy fix if people agrees that it should be done, so I thought the issue needed more information.
In reply to Is that how we do it… by bergmansson1
The developers work on GitHub
In reply to Is that how we do it… by bergmansson1
No, in the case of Feature Requests, the forums are for initial discussions. Perhaps the request needs to be clarified, or extended. Perhaps MuS already does the requested action. Perhaps it works in one OS, but not in another.
But once the request has been discussed, it must be filed on the GitHub site in order for the developers to see it and act on it.
In reply to Is that how we do it… by bergmansson1
Not just "straight up help questions", but any discussion with other users - verifying if a behavior seen is a bug or not, sharing tips and tricks, brainstorming ideas for improvements. Then if it iturns out after discussion here there is a reason to report something to the developers, you go to GitHub. For most users, it is best to start here to get consensus before opening an issue on GitHub.
In reply to Not just "straight up help… by Marc Sabatella
Ok, got it, then I didn't post completely in the wrong place. I took the last comment to mean that following up on here was no longer any useful at all.
I think we have consenus at least for what type of ocarina plays in which range, and that this should be updated.