Audition/Replace Dynamics
I often like to "audition" dynamics - that is to try one, then another until I like what I hear. Instead of having to select, delete, and re-insert dynamics, it would be really nice if it were possible to select a dynamic and replace it by simply double-clicking a new dynamic in the pallette. I know it sounds trivial, but it seems a logical way to save a few clicks in an editing session.
Comments
It is very simple to edit the velocity on a dynamic in the inspector until you get the dynamic just right. You can then enter the closest dynamic to that and adjust it's dynamic. It doesn't have to say ff for a velocity of 107 (default is 112). Along these lines, dynamics are an editable text item so if you want to change the dynamic in the text, you can also press ctrl+shift+ the letter for the dynamic and MuseScore will enter that dynamics letter. MuseScore does not use a single symbol for dynamics like ff but rather two f's like you would get when you press ctrl+shift+f twice.
In reply to It is very simple to edit… by mike320
This is all very true, Mike, but your solution, while simple, is not really a time- or click-saving operation. As I said, it IS trivial, but in the workflow, saving a click or two is often worth more than just the time it saves. (Besides, ctrl shift letter doesn't seem to work that way for me. Ctrl shift P opens the plugin creator)
The thought here is by selecting a dynamic, you are telling MS that you are working on that element, and then double-clicking a dynamic in the pallette would replace said element.
In reply to This is all very true, Mike,… by toffle
Given that currently this act does nothing, I agree it seems like nice enhancement that comes with no disadvantage I can see.
In reply to Given that currently this… by Marc Sabatella
Thanks, Marc. My worry was that adding a new double-click function to an already existing operation might somehow conflict with some OTHER operation within MS,
In reply to Thanks, Marc. My worry was… by toffle
It's good to think along these lines for sure. But here, we're safe. It's not really a new function, double-click of a palette item means a very specific thing: perform a "drop" operation of that item onto the selected score element(s). Right now, dropping a dynamic onto another dynamic does nothing, because each type of element has a list of things you can drop on, and dynamics don't you drop other dynamics onto them. So all that's needed is to change the code handling drop onto dynamics to accept other dynamics, and to make the behavior be, replace the current text & playback settings with those of the item being dropped.
In reply to It's good to think along… by Marc Sabatella
" So all that's needed is to change the code handling drop onto dynamics to accept other dynamics, and to make the behavior be, replace the current text & playback settings with those of the item being dropped."
This is exactly what I was asking, though it seems I was perhaps not as clear as I should have been.
There may be a listing in the MS documentation of operations which can be edited via "drop", but my tendency is to click first and ask questions later. Surely nothing bad could ever happen that way! :)
In reply to This is all very true, Mike,… by toffle
ctrl+shift+p opening the plugin creator shouldn't be too surprising. It's not the first time there was such a conflict. I've never noticed it and didn't get the plugin creator when I tested it. Ctrl+shift+ all of the other letters should work as far as I know. Changing velocities in the inspector is easier than double clicking a dynamic in my opinion so would be a far better method if you are trying to get the perfect velocity.
Having said all of that, I think a chord/note in one voice should only be permitted to have a single dynamic on it. I've always considered multiple dynamics on a note to be a bug.
In reply to This is all very true, Mike,… by toffle
You have to be in text edit mode for Ctrl+Shift+P to work.
In reply to You have to be in text edit… by Marc Sabatella
This wouldn't be the first shortcut in text edit mode that exists both inside and outside of text edit mode to be passed through to be executed in it's other form. When I've seen this, it happens inconsistently (randomly?) so I don't doubt toffle has experienced this while in edit mode.