Some dynamics in MS 4.5.2 are nonfunctional
The second line of this score doesn't respond to dynamics. Can anyone tell why that is?
Do you still have an unanswered question? Please log in first to post your question.
The second line of this score doesn't respond to dynamics. Can anyone tell why that is?
Do you still have an unanswered question? Please log in first to post your question.
Comments
Hard to know without further information. What have you done to make that happen?
In reply to Hard to know without further… by Ruben Remus
This score or excerpt comes from some user on MuseScore.com. Export it in MusicXM format, and the dynamics will return as expected, see: 1Nonfunctional_dynamics__scorster.mscz
In reply to This score or excerpt comes… by cadiz1
@Cadiz1 wrote > This score or excerpt comes from some user on MuseScore.com. Export it in MusicXM format, and the dynamics will return as expected
Actually the provenance of the score is:
• A piece I originally learned by ear
• Recorded it in real-time into a sequencer (approx. 30 years ago)
• Exported to MIDI
• Imported to the Encore notation app
• Exported to from Encore to XML
• Imported the XML to MuseScore Studio 4.5.2
Upon noticing the dynamics issue I created the short score (embedded in the original post.) I added the initial line to make sure that dynamics were working. Then I pasted a phrase from the MS4.5.2 score produced by MusicXML import—then I added dynamics to that phrase and again found they do not work at all.
In reply to The provenance of the score… by scorster
In such cases, you have to ask yourself: am I able to reproduce the problem ("Some dynamics" that wouldn't work in 4.5.2?) from scratch? The answer is no: if I manually write the same line with 4.5.2, all's well. See the file: MS4-5-2_scorster(2).mscz
I don't know when something went wrong, but given the file's eventful history, it's hardly surprising :)
MusicXML export is often useful in case of doubt. It acts as a kind of file reset.
In reply to In such cases, you have to… by cadiz1
@cadiz1 > In such cases, you have to ask yourself: am I able to reproduce the problem ("Some dynamics" that wouldn't work in 4.5.2?) from scratch? The answer is no
Correct. And that's precisely why I started with a fresh score and entered the notes on line 1, which work with dynamics as expected.
> ...if I manually write the same line with 4.5.2, all's well.
Understood. Of course, manually rewriting the score is the last thing I want to do. I'd rather invest time in removing the stumbling stone so others don't stub their toe.
> MusicXML export is often useful in case of doubt. It acts as a kind of file reset.
Unfortunately exporting to MusicXML and importing back to 5.2 doesn't cure the dynamic issue.
In reply to @cadiz1 > In such cases, you… by scorster
Sketchy origins aside, I'd think MuseScore would deal with my wayfaring file more gracefully.
In contrast, here's a pristine C major scale generated today in Logic Pro X and exported to MIDI.
C scale from Logic Pro X.mid
After importing to MuseScore 4.5.2 I encounter non functional dynamics
C scale from imported from Logic Pro X MIDI export.mscz
Interesting. I also wonder why. Not just that it happened. The fix is useful, but doesn't answer the question.
In reply to Interesting. I also wonder… by bobjp
Seems like I recall something about notes with velocity applied (e.g., in MIDI format) would sometimes not recognize MuS's written dynamics. I don't recall the details and probably never really understood them, but that seems a possibility to consider?
In reply to Seems like I recall… by TheHutch
That at least was a problem with Mu3 (and before) but IIRC this isn't possible anymore with Mu4?
See How to restore correct playback of dynamics and hairpins in an imported MIDI file
(Apparently I remembered wrongly)
In reply to That at least was a problem… by Jojo-Schmitz
@Jojo-Schmitz
Thanks for this link, but the steps don't solve the reported dynamic problem in MS4.5.2.
Currently in MS5.4.5.2 Properties>Note only contains Head, Stem and Beam tabs
Velocity is now hidden (I guess because it is SO poorly supported in MS4) in General>Playback. And pressing Reset does change all values to 64, it does not fix the initially reported velocity issue. Seems that the How-to needs updating.
Indeed the score embedded in the original posed opened with velocities of User type at varying values. (Offset type is no longer a thing in MS4). I set all values to 64 to see if that alienated the dynamic anomal, but that made no difference.
In reply to @Jojo-Schmitz Thanks for… by scorster
It is still there in 4.5.2, not hidden at all
![Screenshot 2025-04-30 080443.png]( "Screenshot 2025-04-30 080443.png")
In reply to It is still there in 4.5.2 … by Jojo-Schmitz
I wish it was like that on MacOS, MS 4.5.2
Here's MS4.5.2's Properties panel on MacOS
with Playback closed
with Playback toggled open
Regarding my comment about being hidden, I was referring to the object I'll call the Playback Button-Tab
Anytime I select something other than a note or a rest:
• the Playback Button-Tab closes
• its contents remain hidden until the user reopens the Playback Button-Tab
• AND there's no checkbox to enable Playback Button-Tab "keep open" property
Users encounter a tedious workflow when editing velocities. And that's caused by automatic of closure Playback Button-Tab. This is triggered when the user clicks on anything other than a note or rest.
In reply to I wish it was like that on… by scorster
??? I do see Velocity in your 2nd image
In reply to ??? I do see Velocity in… by Jojo-Schmitz
Yes. On opening Properties>General the velocity properties are hidden in the Playback popup (I think that's the object type.) That is, the popup is closed whenever the Properties>General is opened—unless a note or rest is currently selected. That's the default behavior and no option to have the velocity properties popup display whenever the General Tab is open.
All that's needed is a keep open checkbox or property. I'd turn that on and leave it on. That would solve it. Previously requested on Github, I think.
I think MuseScore's first attempts with popups have been awkward.