Dynamic marks' Velocity will not stay changed to zero when I leave F8.
My computer is Windows 7 and the Muse program is 2.0.3. Here is what happened: I noticed that some Dynamic marks were not rendering the proper volume. I tried hitting them individually and I tried doing the "Select all similar elements" and made sure they were listed as "Staff" (some were listed as "Part", but that changed when reset in F8) and that the Velocity was listed at 0. When I then checked any individual dynamic mark, they had all reverted back to their previous velocity. I found that if I changed their velocity to any number except 0, they would change to that. I set them all at 1 and they stayed there. I tried scrolling (using little arrows) the number down to 0, tried using the curved double arrows at the side, tried erasing the number and typing in the 0 but nothing sticks. This piece may have been partially composed in Allegro and brought over as a Midi file, if that is relevant.
Comments
is relevant (I think)
Right click a note-> Select all similar elements-> From Inspector reset Velocity and Velocity type;
Right click a dynamic and do the same.
If possible upgrade to 2.2.1: https://musescore.org/en/download
Can you attach the score you are having problems with?
In reply to is relevant (I think)… by Shoichi
Hi, I am not having trouble with the notes (but I did do the "Right click a note-> Select all similar elements-> From Inspector reset Velocity and Velocity type" thing, just in case).
When I try to do the same to the dynamics, that is where I have the trouble I mentioned. I do it, then come out of Inspector, go back in, and the dynamic has reverted to its previous large velocity. If I set the velocity to anything except zero, it will keep that number. All are currently set at "1". If I try to change from one to zero, they all revert, again, to that previous large velocity, not, oddly to the "one" I had reset them to.
In reply to Hi, I am not having trouble… by Beths
I attach an xml file, I'm using 2.2.1 and you couldn't open the mscz file with 2.0.3
HTH
In reply to [inline:18052309.png]… by Shoichi
Sorry, I don't understand your reply. Or what to do with the file you sent, which will not open for me.
In reply to Sorry, I don't understand… by Beths
I thought I would try doing the piece without the dynamics marking there at all, and just put a sforzato mark in their place, and that did the trick. I had had a forte, then the next note an mp, third note forte again, then 4th note mp again. The forte sounded too loud, so I changed it to mf, but the volume was just the same, did not drop from the forte volume. After some of the dinking around that I did with it, including changing the second forte to mf, they both did drop in volume, but now the two mf's were two different volumes. (??) Anyway, the sforzato has done the trick, so no more problem. Thanks for your help.
Beth
Zero is not actually a valid value for velocity - MuseScore probably should not even let you attempt to set that. Right now, we (ab)use the "0" value to mean, don't do anything - for dynamics like sfz that we have no direct way of supporting. But for "normal" dynamics like p, mp, mf, or f, setting a value of 0 would be nonsensical. What is you are actually trying to accomplish? Whatever it is, probably there is a better way.
Since you mention, here's a guess: the notes have their own velocity setting, so the value for the dyamics is being ignored. What you really need to do, instead of editing the veloctiy for the dynamics, is to edit the velocity for the notes. Do this by selecting them all - Ctrl+A, press Notes in Inspector - then hit the "Reset" button next to Velocity (which sets them to an offset of 0, very different from an actual velocity of 0).
In reply to Zero is not actually a valid… by Marc Sabatella
The notes in the Inspector are already at Offset and 0. Do the Dynamics just get to keep whatever diverse velocities they happen to have, then?
In reply to The notes in the Inspector… by Beths
Not sure what you're asking, but the dynamics set the default velocity for all subsequent notes until the next dynamic. So, an "f" with velocity 96 means all subsequent notes are played with velocity 96 unless specifically overridden (ie, if you explicitly set a new "user" velocity, or add an offset, via the Inspector). All of this normally "just works" and you don't have to mess with it at all. But as mentioned, in the case of MIDI import, all notes end up having a velocity override - their original velocity is preserved, so the Inspector will show a "user" velocity for everything. Meaning any dynamics you add will be ignored unless you reset the note velocities.
Somehow, it seems you are describing something else, so in order to understand and assist better, we'd need you to attach your score.
In reply to Not sure what you're asking,… by Marc Sabatella
Well, I thought I would try it without the dynamics marking there at all, and just put a sforzato mark in its place, instead, and that does the trick. I had had a forte, then the next note an mp, third note forte again, then 4th note mp again. The forte sounded too loud, so I changed it to mf, but the volume was just the same, did not drop from the forte volume. After some of the dinking around that I did with it, including changing the second forte to mf, they both did drop in volume, but now the two mf's were two different volumes. (??) Anyway, the sforzato has done the trick, so no more problem. Thanks for your help.
Beth
In reply to Well, I thought I would try… by Beths
@Beths... You wrote...
I had had a forte, then the next note an mp, third note forte again, then 4th note mp again.
For the ultimate control of dynamics at a granular level like this - i.e. each successive note sounding at a different velocity, you can set 'Velocity type' (in the Inspector) to 'User". This way you can independently adjust each note's velocity -- and unaffected by any of the score's dynamic markings.
So, instead of this:
The forte sounded too loud, so I changed it to mf, but the volume was just the same, did not drop from the forte volume. After some of the dinking around that I did with it, including changing the second forte to mf etc...
you would be able to set a unique velocity for each note - any number from 0 (silent) to 127 (loudest) - a more precise control compared to 'dinking around'. ;-)
P.S.: When intricate topics like this are involved, posting your score (or a snippet of it showing the issue) is often the best practice since a specific problem can have several solutions, some more effective / efficient than others.
Regards.
In reply to @Beths... You wrote… by Jm6stringer
I appreciate getting detailed info like that. It will be helpful on future pieces.
Thank you
@Beths... The term "velocity" requires two distinct considerations:
1. A dynamic mark's velocity
2. A note's velocity
Concerning dynamic marks, you wrote:
I tried doing the "Select all similar elements" and made sure they were listed as "Staff" ... and that the Velocity was listed at 0. When I then checked any individual dynamic mark, they had all reverted back to their previous velocity.
They revert back, because dynamic marks require a velocity to be heard. For example, 'forte' defaults to 96, 'piano' shows 49. (These numbers can be changed in the Inspector - e.g. to make 'forte' louder/softer than the default.)
You also wrote:
I found that if I changed their [dynamic marks] velocity to any number except 0, they would change to that. I set them all at 1 and they stayed there.
Yes, but why change all the dynamic marks to the same velocity setting by using "Select all similar elements"?
Doing so would make forte as well as piano sound the same; and, with velocity set to 1, would be inaudible.
[Although you can select all 'forte' marks, for example, to tweak them (as a group) louder/softer from the default 96 velocity.]
Regarding notes...
Notes can display a velocity of 0 in the Inspector:
1. With 'Velocity type' set to 'Offset' and 'Velocity' set at 0, the selected notes will honor the score's current dynamic.
2. With 'Velocity type' set to 'User', and 'Velocity' set at 0, the selected notes will honor the value shown in 'Velocity' as absolute. (This means they won't sound at all... zero... zilch... nada)
Read about note velocity here:
https://musescore.org/en/handbook/inspector-and-object-properties#note
You also wrote:
This piece may have been partially composed in Allegro and brought over as a Midi file, if that is relevant.
That's why selecting all notes and resetting velocities in the Inspector was already mentioned. You want to get rid of any user defined velocities generated by the midi import.
Regards.
In reply to @Beths... The term "velocity… by Jm6stringer
Somebody told me a way to fix the problem was to do the zero velocity to the dynamics--- it just got VERY quiet, haha. I finally decided that I would just drop the dynamics from the one measure that was giving me trouble and I just put in a sforzato and that achieved the effect I wanted. But thanks for all the info, I will save that for future snags.