3.0 hairpin problems

• Sep 17, 2018 - 21:33

dynamics_are_stubborn.mscz

In the attached file, moving the hairpin in measure 19 (the 9/8 measure), moving the hairpin manually so it looks like

fixed hairpin.PNG

then saving the score makes manual adjustments go away as in the attached file. There is no way to keep the hairpin moved.

BTW, the bugs I report here in the forum are because I'm not sure if there is an existing bug report, but I believe there might be.


Comments

I have also a problem with hairpin which I can't move.
Sorry for my English. I hope, I can explain it properly.

In a nearly ready score I corrected one false accidental in bar 137.
Then the crescendo-decrescendo hairpins originally belonging to bar 135 in the stave above suddenly appeared across two pages.
I could only mark one half of the hairpin (the decrescendo) to delete it. Doing this, the second hairpin went under bar 94 - totally wrong place and page ... I don't understand how, because I could not even klick on it and mark it. It reacts to nothing I tried. It does not move.
I can't even show you the first odd view with hairpins across pages. Also "undo..." has no effect on this.

I tried to close the score and saved as a pdf to check, if it is a problem of slow graphic display. But it stays – a crescendo in a wrong page under a wrong bar (94).
Ideas, what I can try next?

Thanks, auftakteule

Attachment Size
Problem with hairpin.pdf 75.42 KB

In reply to by auftakteule

The PDF doesn't help. You need to attach the actual score for us to see what is going on with it. I suspect you are using version 2.3.2 or earlier, this discussion only applies to version 3.0 which is still in pre-release. None-the-less, attach your score and we'll help you.

In reply to by auftakteule

To fix your problem, click the first note affected by the hairpin, shift+click the last note affected by the hairpin then double click the hairpin in the palette or press < or > to apply it. You can then fine tune it if you need to keep it from overlapping a dynamic or other elements.

FYI, This is the Development and Technology Preview forum. Since MuseScore is open source, which means you can download the code and do with it as you please, there are open discussions on issues with the official release. This forum is for the next release being worked on. The latest released version is 2.3.2 and the next release has been announced to be version 3.0. There are quite a few people currently testing the future 3.0 at our own peril and helping the programmers find things, like hairpins, that need to be improved.

Do you still have an unanswered question? Please log in first to post your question.