Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove velocity settings for dynamics and hairpins #13858

Closed
Tantacrul opened this issue Oct 21, 2022 · 9 comments · Fixed by #14092
Closed

Remove velocity settings for dynamics and hairpins #13858

Tantacrul opened this issue Oct 21, 2022 · 9 comments · Fixed by #14092
Assignees
Labels
P1 Priority: High
Milestone

Comments

@Tantacrul
Copy link
Contributor

Task description
This is a step we need to take to have a simpler, universal system for velocity change in MuseScore 4. In MuseScore 3, there are competing velocity parameters which the user then needs to be able to learn to either combine or prioritise. It is too complex and unworkable for the future.

So for MS4, velocity can only be placed on notes themselves.

Hence, these options need to be removed of hairpins and dynamics:

image

image


Moreover, we now should also remove the tab in 'playback' that distinguishes between 'General' and 'Dynamics'
image

@Tantacrul Tantacrul added the P1 Priority: High label Oct 21, 2022
@Tantacrul Tantacrul added this to To triage in [MU4.0 RELEASE] via automation Oct 21, 2022
@Tantacrul Tantacrul added this to To do in [MU4.0 - INSPECTOR] via automation Oct 21, 2022
@Tantacrul Tantacrul added this to To do in [MU4 - MPE] via automation Oct 21, 2022
@Tantacrul
Copy link
Contributor Author

@HemantAntony - you think you could take this one?

@RomanPudashkin RomanPudashkin moved this from To triage to Release blockers in [MU4.0 RELEASE] Oct 21, 2022
@HemantAntony
Copy link
Contributor

@Tantacrul Yeah I'll take a look at it

@Tantacrul
Copy link
Contributor Author

@Tantacrul Yeah I'll take a look at it

Thanks! Let me know and I'll test

@vpereverzev vpereverzev assigned Eism and unassigned vpereverzev and HemantAntony Oct 24, 2022
@vpereverzev vpereverzev added this to the Sprint 75 milestone Oct 24, 2022
@HemantAntony
Copy link
Contributor

@Tantacrul Just to clarify, I should be deleting the entire Dynamics section, right? After that, only the General section is to remain?

@Tantacrul
Copy link
Contributor Author

Tantacrul commented Oct 24, 2022

@HemantAntony - yes.

Which means we also no longer need these tabs:
image

@HemantAntony
Copy link
Contributor

@Tantacrul check #14092

@RomanPudashkin RomanPudashkin moved this from Critical to In progress in [MU4.0 RELEASE] Oct 27, 2022
HemantAntony added a commit to HemantAntony/MuseScore that referenced this issue Nov 2, 2022
RomanPudashkin added a commit that referenced this issue Nov 2, 2022
…tings_for_hairpins_dynamics

Fix #13858: Removed velocity settings for dynamics and hairpins
[MU4.0 - INSPECTOR] automation moved this from To do to Done Nov 2, 2022
[MU4 - MPE] automation moved this from To do to Done Nov 2, 2022
[MU4.0 RELEASE] automation moved this from In progress to Done Nov 2, 2022
@fsgregs
Copy link

fsgregs commented Aug 2, 2023

God, I totally disagree with this thread. Dynamics MUST be editable in both dynamics marks and hairpins. The default dynamics, of "ppp", "pp", "p", "mp", etc. are just too broad. They can be 10 -15 or more velocity points. Frequently, a dynamic jump that much is just too large. We need to be able to soften some of the loud dynamics or boost some of the soft ones so that the score's instruments play at the "correct" volume. In a full orchestra, the composer or conductor will verbally tell the musicians to soften it or boost it a bit as a nuance. MS 4 should be able to mimic that, particularly if the Mixer is playing the score. The guy who objected to this existing feature in MS 3.6 was just wrong!!!

Likewise, a hairpin should by itself be editable as it was in MS 3.6, so that we can create global crescendos. For example, in this actual score posted below, the red hairpin at the top has set velocity of ALL instruments in the score 8 points higher, to create a modest global crescendo. Without it, the score, which has 24 instruments, would have to be adjusted staff by staff to boost all 25 instruments to the next highest default dynamic, which is NOT only 8 pts higher in volume but may be up to 15 points higher. That sound easily can sound awful.

image

Please restore the ability of both dynamics and hairpins to be Play editable. Many others on GitHub have also asked for the same thing. Thanks.

@cbjeukendrup
Copy link
Contributor

Don't worry. What you couldn't know, is that we're planning to build something much more usable in MuseScore 4.2, to achieve the same, and more than that. It's called "automation" (that term comes from the DAW world); it means that you will be able to specify how the dynamics level should change over time. And this won't be done using abstract numbers in the Inspector, but with a nice graphical interface.

@Tantacrul
Copy link
Contributor Author

As @cbjeukendrup says, the purpose of all of the above was to remove the highly bizarre and limited way that things were done in V3 in order to make way for a far faster and more powerful way to do it in version 4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Priority: High
Projects
[MU4 - MPE]
  
Done
Development

Successfully merging a pull request may close this issue.

6 participants