How do I debug dynamics not working?
First, the tech stuff: OS: macOS Mojave (10.14), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.22425, revision: e26f7c4.
Now the situation: I have two half notes; the first one is supposed to start piano, w/ crescendo to the second note, which is supposed to start forte and decrescendo back down to piano. I tried to accomplish this a few different ways: adding the piano and forte marks separate from the crescendo and decrescendo marks, for which I tried both the words and the hairpins; and using the palette entry that provide both the starting dynamic and the hairpin simultaneously. In all cases, the first note is piano, but there is no crescendo, the second note is not forte, and it doesn't decrescendo (and the only way I know the first note is piano is because the first note after the dynamically marked notes is played twice as loud). It feels like I'm missing something, i.e., not doing something right, but I can't find anything in the handbook that provides greater detail to know what I'm doing wrong: where in the handbook is the most detailed description of how to control part dynamics? (Note: I watched the video at https://www.youtube.com/watch?v=KnoKgja20fg--which I note is for Version 2--and according to it, I've done enough, i.e., I should should be hearing a dynamic change, but I'm not; thus either something is wrong with my system/installation, or there is more to making dynamics work than what is presented in that video--in other words, please don't refer me to it, I've already watched it and it was less than helpful.)
Comments
Please share the score
In reply to Please share the score by Jojo-Schmitz
#5.mscz
OK, I figured it out: I was confused, i.e., not really knowing what to do, by the program automatically extending the crescendo hairpin through the forte, all the way to the piano at the beginning of the next bar; some trial and error, and I figured out that if I double-click on the hairpin and then use shift+left arrow, that shortened the hairpin to just the next (forte) note, and playback changed accordingly. Not what I would call the most intuitive UX, but then I'm sure we all have our little "issues" with how certain things are done in a program this complex (or am I being too forgiving: perhaps others also see an issue with, indicative dynamic markings having already been placed, addition of a dynamic change marking just plowing right through the first, most logical dynamic marking to stop at, thus requiring one to "manually override" this default behavior). But: is there a more detailed description of how dynamic and, esp., dynamic change markings are added, and in particular, what the default behavior is when adding them?
In reply to OK, I figured it out: I was… by OlyDLG
A line with playback properties - e.g. a hairpin - relies on positioning its 'anchor' to apply the effect across notes.
See:
https://musescore.org/en/handbook/3/hairpins#adjust-length
and notice the difference to merely fine-tuning the horizontal position without affecting playback.
Also:
https://musescore.org/en/handbook/3/lines#apply_lines
and note the behavior of 'end handles'
https://musescore.org/en/handbook/3/lines#lines-playback-properties
In reply to Lines with playback… by Jm6stringer
Thanks for the links, I'll take a look!
In reply to OK, I figured it out: I was… by OlyDLG
I plan to make a "How to..." next week that will explain all of this for people in the future. I'm working on it at the moment and creating pictures that will help explain (I hope) and we will be able to simply point people to the page in the future.
You may ask why a how to rather than putting it in the handbook? While the handbook has some examples for clarifications, dynamics requires knowledge from various parts of the handbook to be put together, so a How to... is the best method in my opinion. I do plan to link to it from the handbook on several pages in the External LInks section.
In reply to I plan to make a "How to..."… by mike320
Excellent, thanks! (No, I agree that a "How-to" is appropriate; I look forward to seeing it!)
In reply to Excellent, thanks! (No, I… by OlyDLG
I was replying to you, but others have specifically asked why certain things like this aren't in the handbook, so I was covering that question for others who will see this as well.
In reply to I was replying to you, but… by mike320
No worries, I was just expressing my support! (Feel free to run a draft by me if you want it proofread before submission; no obli, just offering.) And thanks again!
In reply to No worries, I was just… by OlyDLG
Once I post it, it becomes a community effort and anyone can edit it. People will no doubt beatify it and fix any errors I didn't notice myself. I'm doing pre-release work to make it better this week so perhaps it will require fewer fixes than my previous efforts.