Dynamic does not work?
It looks like that it is ignoring dynamic, just in some places it is changing dynamics but not always according to what is entered. Is there some double hidden dynamics, or is it a bug? Am I missing something?
| Attachment | Size |
|---|---|
| Sleeping_Sun_Coro.mscz | 51.14 KB |
Comments
Could you be more specific about which dynamic(s) you're talking about by measure and staff. BTW, you should unassign yourself from this. The person assigned is the one who will fix it if it's a real bug.
If you look at the part in the file I added, where the lyrics start, I assigned 'pp' which should by default apply the velocity of 33 to that section. But if you open any note of that section in inspector, it still plays it at velocity of 64 instead of 33 although if you inspect 'pp' element, it gives you 33 as the velocity.
I mean, I can open every single note in the inspector and manually assign it the new velocity to every note (I tried, it works), but nobody would do that...
The reason your dynamics don't work is that the notes themselves are all set to override the dynamic. Not sure if you did that on purpose or if you imported the file from MIDI and those values are being used, but you need to reset the notes themselves to default velocity if you want dynamics to override them. For instance, right click a note, Select / All Similar Elements, then hit the reset button next to the velocity controls - no need to do it one at a time. but to be clear - for normal scores created within MuseScore, none of that is necessary. Notes normally start off with no velocity override. It's only because these notes have all acquired manual overrides already that you need to undo this.
In the future, when you have questions about how to use MuseScore, please use the Support forum (eg, Help / Ask for Help, from within MuseScore).
Thank you!
Is there a way to regulate the buildup intensity of cresciendos? I hardly see its effect if at all... Or it is something else that I have to reset?
Sorry, it was my first time, I will use the support forum next time.
The best way to regulate the buildup intensity of a crescendo is to put a dynamic at the end or immediately after it. If this is not the same volume you want after the crescendo is complete, make sure the volume is at the end of it and mark it invisible (just select it and press V). I usually just place the final volume on the last note and make it invisible.
This is a work around, mostly because a computer cannot guess what you want if you don't tell it. If the crescendo is entirely within a single note, there will never be a crescendo swell on that note. Perhaps in a future release this process will change, there is someone working on it.
Also you can tweak the 'velocity change' of a cresc. via the inspector. Still won't work for a single note though.
Thank you very much for the info!
I believe that the best way to define crescendos in future versions would be by initial and the final level, for e.g. you leave two fields where you put `mp' and 'f' which would mean a buildup from mp to f.
There is something else it sometimes happens to me: I open the file and I start playing it and it is completely mute. Rebooting the computer helps but I can't figure why is it happening.
But in general, we love the program since it has so many options!
For tablets with Windows, it would be useful to have a display mode with one touch page turn to use tablet instead of a score folder at concerts. (maybe it exists, I haven't seen it)
And, by the way, in android paid versions, why does piano sound so cheap?
That's already the case for dynamics - place an mp before and an f after, and MuseScore honors that same as a human musican would.
As for the muting, again, supporting forum is the place to ask for help. We'd need a score and steps to reproduce the problem in order to do see what the problem might be.
The mobile app uses a smaller soundfont to make the download/install a reasonable size. But smaller soundfont = less realistic sounds.