Ignore hairpins during playback
Is there a way to have a decrescendo be ignored during playback. The decrescendo conflicts with other dynamic changes I'm making in the measure.
Do you still have an unanswered question? Please log in first to post your question.
Comments
Conflicting dynamics are problematic. One long hairpin with shorter hairpins between some of the notes causes problems. If you use CC2, I'm not sure what you can do about it. If you use CC11 for dynamics, you can use note by note velocities, though this will prove to be a problem if you want a crescendo on a whole note.
If it's conflicting with the dynamic, what is the point of the hairpin? Something isn't making sense here. If you attach your score, we can understand an assist better.
In reply to If it's conflicting with the… by Marc Sabatella
It's really me causing myself more problems. Musescore does not have built in playback for the fade-out articulation. So, I took the liberty of making them myself. With a couple of decrescendos, and redundant dynamic markings, (all invisible) you can get decent sounding fade-outs. However, a problem arises when you also want the same line to be crescendoing. Weird dynamics ensue as a result. I was hoping I could "mute" the crescendo so I could manually put it in with dynamic markings; but alas, I cannot.
In reply to It's really me causing… by CptBraddock
Well, you can set the Velocity change to 1, when change will make the effect imperceptible.
In reply to Well, you can set the… by Marc Sabatella
I was imagining someithing like
![cresc and dim.PNG]( "cresc and dim.PNG")
which is from measure 92 of Dvorak's cello concerto 2nd movement. This is among the most obvious problematic measures, though there are others with similar ideas. The measure gets louder but each 16th note is softer than the previous 8th note. The intention is clear, but MuseScore's interpretation is unpredictable to me and never correct. I'm not complaining about how MuseScore handles this, it's up the the user to make sure the playback is acceptable in my opinion, much like it's up to the musician to play it correctly.
MuseScore has it's way of dealing with situations like this, and it selects a dynamic, probably based upon the order they were entered into the score, so setting a velocity to 1 is probably not a good solution. Usig CC11 dynamics with individual note velocities is probably a better solution.
Edit: I guess the site doesn't like my picture for some reason. It's a picture of cello solo part in measure 92 of the file at https://imslp.org/wiki/Special:ImagefromIndex/49364/hfgk
In reply to I was imagining someithing… by mike320
This site does like pictures. But not ones with an & in its name I guess
In reply to This site does like pictures… by Jojo-Schmitz
Thank you, picture fixed.