Violin Solo MuseSound playback is messed up
Reported version
4.0
Type
Performance
Frequency
Few
Severity
S4 - Minor
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
While playing back a score with a MuseScore violin solo part, the playback doesn't sound right:
1) Often the tone of the instrument sounds more akin to a saxophone or bagpipes than a violin.
2) There are a number of times where is sounds like two violins playing the part rather than just one (as though two separate audio files are being played back simultaneously).
3) There are a lot of slides being added to the part that are neither written nor tasteful.
The extent to which I noticed these problems varied a bit depending upon the exact material being played. However, many cases in which I experience these phenomena happened in normal string writing in a comfortable range and dynamic.
Comments
Would like to add: Dynamics are not working very well. There are sudden changes in dynamics even that they are not written in the score. Exactly same passage worked fine with section violins when I tried.
I am also finding that the MuseSounds solo violin sometimes sounds like multiple violins.
This has been a longstanding problem even in the beta, it has persisted into the 1.0 release. The portamento issue is better but not completely fixed. It is also a problem for myself as well.
Four (and Five) is still few
In reply to Four (and Five) is still few by Jojo-Schmitz
Similar problems with solo strings. Sometimes the dynamic dissapears completely at the start of phrase. Sometimes inside a note weird increase in dynamic. Sounds like someone is learning to play.
Also viola and violoncello more orchestral (in dynamic) than solo. Boosting on mixer can do only that much.
Many stuttering that seem time-related (can not quite seem to have enough time). Would be interesting to hear if it would be OK in export audio but it crashes after 1%.
Five is still few...
In order for someone to investigate a specific problem, there would need to be a sample score and a precise description of how to reproduce the problem (eg, which notes are not playing properly).
There are several different and completely unrelated things being discussed here, best also to have separate issues for each problem - each with sample score and precise steps to reproduce.
In reply to In order for someone to… by Marc Sabatella
SO, you're saying that in order for you to... DO YOUR JOB and fix the product that you're providing, we have to do your entire job for you and investigate exactly how to recreate the issue. How about YOU do the investigation as it is not the responsibility of us composers to fix your program for you. Musescore 4 altogether feels like a rushed User Interface overhaul that muddies up the composition process with pointless, elementary flaws in its design while delivering no real benefit to composers. All we heard about is how great the playback will be on 4. Now that we have received it and rightfully complain because it's bugged or non-functional, you throw your hands in the air and act like somehow were responsible for finding out WHY it's broken. Nonsense
Sorry I am OT but: I am quite tired of hearing complaints. An open source lives on the participation and collaboration of users in general. Paraphrasing an old Latin fable: If you are not satisfied with the product abandon it, we will give you back the price paid.
Please refrain from the personal attacks.
Again, the violin is working fine for me and for others So if you have a specific score where some specific note is giving you trouble, please attach it. Takes but a few seconds and helps us all out, just as we are all volunteering our time to help you out.
You mention some sort of "elementary flaw", but it isn't clear what you mean by that. Please be sure to open a separate issue to discuss the specific flaw you have noticed, again with complete information that would be needed to understand the problem you are perceiving.
We all do our best to help each other out here, that's how open source software works.
we have to investigate exactly how to recreate the issue is the price to pay for using Free and Open Source Software!
That’s even true for commercial software. Developers don’t magically gain mind-reading powers when working on proprietary software. They remain incapable of fixing problems no one tells them how to reproduce. It’s really just plain common sense.
I've been having this issue for a while now. Some intervals, at some speeds, sound weird on Violin 1.
I've managed to narrow it down to legato.
I believe that any note interval within 1 octave use legato for violin 1, but sometimes this legato is not desired.
Also, if the note is too short, it doesn't play the legato long enough to play the correct pitch before stopping the note, so it just sounds weirdly out of tune.
Attached to this comment is a file with the more pronounced intervals and speeds that this happens using Violin 1 (Solo) of MuseSounds Strings (I don't know how to check the version for MuseSounds Strings).