Different Dynamics Between Two Staves
I'm making a score for a Geometry Dash song I really like. There is a saw synthesizer, and I need the right hand to be forte while the other hand is mezzo-piano and fading out. I used "Dynamic range: staff" for all dynamics, but the right hand seems to be fading out with the left hand. Please help figure this out :D
| Attachment | Size |
|---|---|
| Hexagon Force.mscz | 15.7 KB |
Comments
Click on each hairpin and, in the Inspector set 'Velocity change' to a larger number -- try 50.
Each mf will begin with velocity = 80, then drop off until the next mf is encountered. At that point. the velocity resets to 80 and drops off again.
FWIW...
If you want the velocity to continuously drop across measures 1 - 4 without resetting to 80, then you could use a single hairpin spanning all 4 measures, starting at mf and ending with, say, pp.
In reply to Click on each hairpin and,… by Jm6stringer
Wouldn't it depend on how it's implemented - e.g. if it uses the midi "expression" controller for the hairpin, then it will affect both staves as it's channel-wide.
However this doesn't seem to be the only problem - even the mf's are affecting both staves despite being set to "dynamic range = staff", so that seems to be a bug? In fact I got some very weird behaviour using "dynamic range = staff", it seemed to be trying to play the note at full volume then instantly drop back to the dynamic of the 2nd staff. But it's related to the fact it's trying to use the same MIDI channel for both hands - unfortunately so far the only way I've found to change this is to edit the mscx file directly, but it can be done (you add the 2nd channel in the mscx file then you actually need to use a hidden staff text element that triggers the channel change).
Alternatively obviously you can just have the LH and RH of the synth as separate instruments.
I'd expect MuseScore would do this automatically if you use "dynamic range=staff" though, so fair to say it's a bug.
BTW the other alternative is to use a synth sound that has a waveform with a built-in decay, such that it's not observable in the 1/8th notes in the right hand. There's a good chance that's how the effect was created in the first place. I don't know what tools (if any!) MuseScore provides for editing synth waveforms (adding decay is one of the simplest things to do though!). I suspect there's no direct way in v3.6 but there's a chance there might be in v4.0 or later. I'd say that's going rather beyond what I'd expect notation software to be able to do though! (I was more thinking that there's just be a way to replace the built-in samples with your own, which I gather you can do with soundfonts, but I haven't played around with that at all)