Notes not playing at certain section in score

• Sep 2, 2020 - 03:06

So on a score I am in the process of making, I discovered a glitch where in a certain section, the notes would refuse to play, even if I copied the notes, deleted the measures, and pasted them in new ones, even if I deleted them again and rewrote them in the section, I couldn't get it to play. I'm not sure if this is a known bug, but it's definitely an interesting one.
Here is the score I am having the problem with: https://musescore.com/moonlarke/songs-of-forests


Comments

In reply to by Moonlarke

As far as I can tell, all the notes are playing (I'm listening closely at slow speed with headphones), but a few are much quieter than I expect. The crescendo doesn't; seem to be "taking" in the top staff in bar 34. Not sure why, but the implementation of dynamics playback isn't something I am super familiar with. I'll see if I can ping someone who knows more.

In reply to by Moonlarke

Interesting. On mm34-35 of movement 3 I hear something strange. The top staff is playing but is not crecendoing at all. Each note should be louder than the last but this doesn't happen. The bottom staff has a very obvious crescendo happening as expected. There is nothing in the score that would prevent the crescendo that I see and nothing in the .mscx file that prevents it that I can see. As a test I inserted two measures before the existing m34 and reentered the notes

As can be seen in the attached file, in m35 (which MuseScore reports as m131), omitting the decrescendo makes playback correct. When I add it, I get the same results as the original and this shouldn't happen.

When I look at the xml the absence of the hairpin in m35 is the only difference I see. m34 is identical except that I put a staff text "test" so I could find it in the xml file. I had added "original" to the OP's copy with no change in results.

In reply to by mike320

Notice that If you take out the descrescendo in measure 35 after the [f] mark, all of a sudden the previous measure 34's treble clef will perform as expected: [ppp] increased to [f]. It's as if the decresc. is some how bypassing the [f] in the next measure so that there's no "end dynamic" to which the crescendo is attached. Hrm.

In reply to by Moonlarke

No problem. It doesn't really explain what the problem is though. In order to get the dynamics to be how you seemingly intended to have it, for now consider putting in a decrescendo again but this time on the bass clef, and not at the first note! but on the second note in measure 35, and then flip its direction with 'X' to be between the two staves. Again, it'll work, but it doesn't explain what's wrong with MS here.

In reply to by worldwideweary

To keep the hairpin on the top staff and allow the existing dynamics to affect the hairpins, use voice 2 to enter a 16th rest followed by what left and make everything in voice 2 invisible. You can then drag (starting in version 3.5) or use shift+arrow (all versions) to anchor the endpoint of the hairpin to the second rest in voice 2.

The problem with moving the hairpin to the lower staff is that dynamics on the top staff do not affect it even though both dynamic ranges are set to part.

In reply to by mike320

@mike320: I thought this too, but upon attempt, the hairpin does indeed bring dynamics down to measure 36's pp mark: the decrescendo @ mm 35 is affected by the pp on the upper staff of the next measure when the decrescendo is placed on the lower staff! Not trying to be argumentative, but it does work in this instance from what my ears hear, even though it is usually the smart thing to use voice-2 rests to get dynamics working well when needed. Then again, I'm not sure why this isn't working by "default".

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