-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated Muse Strings playing back harmonics in the wrong/low octave #17483
Comments
Harmonics behavior changed to be consistent across all string instruments, see #16000 for more insight. It's still not perfect but now you get the same result on all string instruments instead of whatever happened before |
Unfortunately the file added by the OP is an MP3, so there's no way to check the notation against the playback. I think there were two feature requests in the original report (#16000) that may have obscured the path forward for the violin family. I think false harmonics depends first on a closed system for natural harmonics, which will require two noteheads for each note. Natural harmonic notation in the violin family (excluding the bass):
This system uniquely determines which natural harmonic is meant, with a single notehead. Why? Because the strings are tuned a 5th apart (and not less). For example, on the C string of the cello, there are natural harmonics at the finger positions Implementation:
The solution: A closed system for natural harmonics using diamond notation has two noteheads:
At first, the user would have to hide a lot of noteheads and stems to make it look familiar. A per-harmonic "hide fundamental" would be nice. Also, you'd have to add the °-notation. You could choose the above system ( ° + oval always refers to the halfway point), to avoid a new can of worms. It won't make everyone happy, but it's complete. From there you could decide how to implement notation variants. The conventional notation at the violin/viola/cello would then be a UI problem and not a sounding-pitch or consistency problem. One notehead for the natural harmonics, and some way of exposing and redefining the fundamental when necessary, and adding false harmonics. Internally, MuseScore would always assign a fundamental. |
Issue type
Muse Sounds bug
Bug description
23 minutes ago
So I've recently updated Muse Sounds in the Muse Hub a couple days ago. Now, I think the sounds are even better than before!
However, when I opened up the MuseScore Demo file of "Searching Four", I played it back, and realized the harmonics in the violins were an octave lower than what they previously sounded before the update.
What was the cause of the harmonics sounds to sound like that in the low octave anyway?
I've attached a zip file of the complete Searching Four audio mockup that I've rendered myself through the updated Muse Sounds. It includes the low octave violin harmonics in the beginning and towards the end.
Searching Four.mp3.zip
There's no way a violinist, including myself, would play a harmonic at a concert C#5 like it does towards the end of the piece.
Steps to reproduce
Screenshots/Screen recordings
No response
MuseScore Version
4.0.2
Regression
I don't know
Operating system
Mac OS Monterey
Additional context
No response
The text was updated successfully, but these errors were encountered: