dynamics faulty after a key change

• Sep 8, 2018 - 18:16

I've noticed that the dynamics on the vocal part of a song need to be reset on the Inspector velocity just after a key change, which is not consistent with the velocity before the key change. Also, the decrescendo hairpin does not function at all.

Of course, being new at this, I may have fouled up somewhere...
Joe


Comments

Please reply to this and click the Choose a file button that will appear and attach your score. Also, explain which items are not working correctly. Someone will be happy to tell you if you found a bug or made an error.

Attaching the score would help indeed. I really can't think of any way that key changes could possibly be relevant here. Mostly like there is something else going on, like having conflicting dynamics in different staves. As for the hairpin, you need to have dynamics before and after it in the same staff for the auto mechanism to work. You can also set the velocity change manually in the Inspector. But if the dynamics are applied properly, things should just work.

Thank you all...

To be clear, the dec. hairpin does not work ONLY in certain passages for the mezzo. I did consult the handbook several times. I'm sure I missed a step. 
At the key changes (mm 16 and 46) I had to fool with the velocity to limited satisfaction. 

Yes, the problem is with the vocal part only. I cannot seem to temper the mezzo who has a tendency to get Wagnerian on me. When the dynamics work, as with the piano part, they work wonderfully.
However, I did notice the sound dynamic (velocity) increased (vocal part) after both key changes...could this be because of the double barline?
The Musescore face looks good. I am tranfering this and other songs to it because my manuscript is illegible to all including myself. BTW - the tonal ambiguity is intentional. ( I got the hang of the note input at least.)

Attachment Size
The Dark.mscz 32.33 KB

In reply to by penne vodka

What you did not notice in the handbook is that hairpins do not work on single notes. All notes tied together are considered a single note. That's something that's supposed to be improved at some point in the future.

MuseScore makes a wonderful looking score, this is the reason it was originally created. There seems to be some recent emphasis being placed on playback, so hopefully while the known bugs for the next release are being worked out playback will also improve.

In reply to by penne vodka

I can see you have a lot of oddly-attached dynamics - dynamics that are attached to notes or rests several beats before where they appear to be. Looks like you might have entered the dynamic on one note then tried moving it to appear elsewhere. In general, you shouldn't do that. Enter the dynamic directly on the first note it applies to. If you find it necessary to adjust the position to avoid a collision with something, use the keyboard (not mouse) to adjust it, otherwise you risk detaching it from its original note. It also looks like you did a lot of manual adjustments to get the lyrics above the staff, and they aren't aligned well. That's not a good way way to do it. Much better to select them all via right click, Select / All Similar Elements in Same Staff, then use the Inspector to move them all together and stay in sync.

Anyhow, all that manual adjustment has definitely caused layout as some of your dynamics are not attached where you think they are. But I don't notice any specific playback problems, can you name a specific measure where things are not as you expect?

In reply to by Marc Sabatella

I was kinda sloppy moving things around with the mouse. I need to review the lyrics procedures. In fact, I missed the part about melisma.
One reason dynamics are out of line is because I did not notice that the hairpins do not work on a single note (as Mike320 explained above) and I tried to create a decrescendo with p's along the way tweeked with the velocity control. Bad idea. Now I know the rules.
It turned out that the mezzo had a sustained note on decrescendo after each key change and t h a t was the coincidence that made me suspect the key change.
Once again, thank you Marc.

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