Not used to nightly builds
Recently I've been playing around with the nightly builds, and I realize I am not used to it. Firstly, I realized the note properties option has probably changed to debugger, but I cannot find all the properties I would want to set, for example velocity. Secondly, is the Palette the only way to insert dynamics now? I cannot find it under the Add tab and the L shortcut certainly does not work. Also how do you change the MIDI properties of a dynamic now?
I understand nightly builds have been around for a long time and these questions might answered before or are very obvious, but since I just used it I am really unfamiliar with it. Any help would be greatly appreciated.
Comments
Note properties, dynamic properties have been moved the inspector. View -> Inspector to display it.
Palette is indeed the only way to add dynamics. Is that a problem for you?
In reply to Note properties, dynamic by [DELETED] 5
Ok that's good, probably better with that inspector.
Not really, I just think that I am used to the old key shortcuts for dynamics, key signatures, etc.
In reply to Note properties, dynamic by [DELETED] 5
Without that L shortcut, how to get at pppppp, fffffff, etc.?
In reply to Without that L shortcut, how by Jojo-Schmitz
From the master palette maybe?
In reply to From the master palette by ChurchOrganist
checked but didn't see them there either?
In reply to checked but didn't see them by Jojo-Schmitz
Add a f to the score, double click it, add as many f you like with Ctrl+F.
In reply to Add a f to the score, double by [DELETED] 5
And the effect on playback? And why having them in the source then)
In reply to And the effect on playback? by Jojo-Schmitz
To get a non-standard dynamic like "ppppppppppp" to playback, you should be able to define the effect in Inspector. If you then add this to your palette, it is even remembered for next time you place it.
In reply to To get a non-standard dynamic by Marc Sabatella
I'm not talking about "ppppppppppp", but about "pppppp", like in https://github.com/musescore/MuseScore/blob/master/libmscore/dynamic.h#…
and
https://github.com/musescore/MuseScore/blob/master/libmscore/dynamic.cp…
or
https://github.com/musescore/MuseScore/blob/master/libmscore/dynamic.cp…
These should at least be part of the master palette, shouldn't they?
In reply to I'm not talking about by Jojo-Schmitz
Why? Non-standard is non-standard. As far as I can see, i would make just as much to remove the support code. Unless I'm missing something - is there some special reason (like SMuFL dictates a particular set of dynamics that must be supported) that we need to directly support "pppppp" but not "ppppppppppppppp" (much less "ppppfffffttt" :-)?
In reply to Why? Non-standard is by Marc Sabatella
SMuFL has support for down to pppppp and up to ffffff. We have the supporting code in MuseScore and have it ever since (well, since a long time, 1.x had it already, albeit hidden behind the L shortcut)
In reply to SMuFL has support for down to by Jojo-Schmitz
Ah, OK, then I guess that does make sense. We should continue to support up to 6 p's or f's.
In reply to SMuFL has support for down to by Jojo-Schmitz
You see you know why ;) So why are you asking? Just make a PR :)
In reply to You see you know why ;) So by [DELETED] 5
To reach a consensus. And to find out where and how the master palette gets set up ;-)
I think I found it. Do we want these additional dynamics only in the master palette or also in the advanced workspace?
Hmm, I think master palette is enough.
See PR #924
In reply to To reach a consensus. And to by Jojo-Schmitz
Fixed in a0c906cb
In reply to Without that L shortcut, how by Jojo-Schmitz
Why do composers insist on using such ridiculous dynamic markings? Even four p or f is too much, IMO.
//themetapicture.com/guy-posts-music-joke-on-facebook/
Sorry for bringing up this post again, but I have something else confused about. I understand there is this new Time Signature Properties now, which I suppose affects the auto-beaming?
Recently I was typing up my music, I did not open that dialog at any time, but suddenly the beaming of the previous section in that music I typed changed its default beaming to something weird, like all 8 quavers beamed or 6+2, which originally were all 4+4 or 2+2+2+2. I know that I can fix this manually for every single beam, but how do I fix the auto-beam? And I still do not understand how to use the new Time Signature dialog. Thanks.
It looks as if you had unwillingly changed the time signature from 4/4 to 6/8 at the beginning of the score
In reply to It looks as if you had by robert leleu
Well I didn't, and it is sometimes 6+2, sometimes all beamed. Most of the time it is all beamed.
In reply to Well I didn't, and it is by YongSee
would be clever to attach the file
In reply to would be clever to attach the by robert leleu
Sorry to contradict you, but the problem here is not just solving this beaming in this particular case, but asking how to change the auto-beam which I think attaching a file would not help much?
In reply to Sorry to contradict you, but by YongSee
Attaching the file would allow us to see what happened in this specific score - why your eighths are not beamed as you expect.
As for how to use the new time signature properties dialog, there are known issues with it - which is to say, it doesn't quite work as it should yet. So it isn't supririsng it isn't doing what you want. See #25368: Note Groups define in time signature dialog has no effect in note entry and #25367: copy time signature from one staff to another doesn't copy time signature properties, for example. Eventually, it should work to click the various notes in the display at the bottom to set beaming how you like, and right now this works sometimes, but not reliably.
In reply to Attaching the file would by Marc Sabatella
I think I know what happened. When I type some rhythms in that are more like 6+2, it changes automatically. But if I close the file and reopen it, it is back to 4+4 again. So I do not think it is easy to reproduce this, as if you open the attachment it will be in 4+4.