Doubling Parts in Musescore 3

• May 7, 2020 - 23:37

Hello everyone,
One feature I liked in Musescore 2 was that whenever you wanted a certain part of the music to come out of the texture, you could double that section between 2 instruments (ex. Trumpet 1 and Trumpet 2 having the same exact part). In Musescore 2 this would make the sound louder but in Musescore 3 it now completely distorts the sound, and yes, I could just take out the second part but then I lose the effect that I originally had Musescore 2. Is this a feature that they removed from Musescore 2? Could anyone help me with this?


Comments

Not sure I understand what you mean there, I don't think MuseScore 2 and 3 should behave differently in that respect, can you provide a sample score?

I am on MS 2, so, I don't know for MS 3, But I use that, for example for the HIt Hat of a drum, which is very "discret" I double it on a 2nd ligne of drums , and it works very well.
For trumpets it's "violent" , when I have a section for the 4 trumpets in "unisson" it's very too loud, so with the inspector, I"mute" 2 or 3 of them , and it works also

Here is a little score I just made that shows the issue. It has a single trumpet playing a theme and both trumpets playing the same theme. Notice how the quality of the sound is distorted when both trumpets play. The distortion is not consistent, on a replay, the doubling section distorts in different places as well. Part_Doubling.mscz

In reply to by SG1230

Neither MuseScore 2 nor 3 plays games with the laws of physics. If you duplicate the same notes at the same time with the same sound sample, you get the audio artifacts you also get doing the same in using any other program. Certain samples might happen to be complex enough to not be as noticeable, or they might have sufficient flaws in their timing algorithms that the notes aren't quite as simultaneously, but this has always been a recipe for distortion. Solution is as it has always been - either displace one set of notes slightly in time, or in tuning, or mute one set, etc.

In reply to by SG1230

These artifacts were present in MuseScore 2, MuseScore 1, and are easily reproduced in pretty much any audio software. Could be you just never noticed I guess, or maybe MuseScore 2 was just slow enough on your system to introduce enough of a delay to mask the inherent problem with this, but again, there is no getting around the laws of physics on this. I certainly had no trouble hearing these problems in any version I've used.

Do you still have an unanswered question? Please log in first to post your question.