Musescore 4.2 Problems
Downloaded Musescore 4 and tried the following on it:
Three problems:
1. The crescendo line disappears as the blue playback line collides with it.
2. The trills do not play the entire duration, they're too short.
3. Trills with wavy lines do not display.
Thanks, guys! Keep up the good work.
| Attachment | Size |
|---|---|
| example.mscz | 17.24 KB |
Comments
my musescore 4.2 is constantly crashing. How can I download/install prev version?
In reply to my musescore 4.2 is… by Jack A. Zucker
Hi, I think it's here https://github.com/musescore/MuseScore/releases/tag/v4.1.1
In reply to Confirmed. Although I never… by bobjp
Indeed. It's why I still use 3.6.2. All those things worked in the version.
In reply to Indeed. It's why I still use… by FBXOPWKDOIR2
So what is more important? Playback or the look of the score? I'm not sure there is a Program out there that will play notation perfectly. MU3 doesn't. Nor does MU4.
You said trills with wavy lines don't display? They did for me.
If you remove the ties and extend the trill line over where the tie used to be, I can't think that a real player would be confused by this.
In reply to Odd. But the cresc still… by bobjp
Yeah but, I'm not involved with any real players. Just Musescore. They are my orchestra. I live in the projects for God's sake.
In reply to Yeah but, I'm not involved… by FBXOPWKDOIR2
Exactly. The three things you listed either have workarounds, or do work, just different from what you are used to.
I write for playback, also. As a result I do all kinds of things to a score to get the playback I want. That's why I asked the question. Over the many years I have used notation software for playback only, I have always done things that wouldn't work for real players.
For playback who cares if the cresc line disappears. Or the trill doesn't play over a tie, as long as extending the trill line makes the trill play the duration.
In reply to Exactly. The three things… by bobjp
I care. But then again I am nobody.
In reply to I care. But then again I am… by FBXOPWKDOIR2
You totally miss the point. Yes, the things you pointed out ought to work. But they don't. So until they do we have to find other methods.
In reply to You totally miss the point… by bobjp
I'm ready to try the keyboard-sledgehammer workaround. Here goes!
In reply to I'm ready to try the… by FBXOPWKDOIR2
I use what is called a "dead-blow" hammer. The head is heavy duty plastic filled with sand. If, for example, you hit a hard surface with a metal sledgehammer, the hammer will bounce. This deflects much of the striking force. Hit that surface with a dead-blow hammer and there is no bounce. The full force of the blow is transferred to the object that is struck. Effective and satisfying.
In reply to Indeed. It's why I still use… by FBXOPWKDOIR2
Yeah, MuseScore 4's playback is currently really buggy (I honestly think they should have waited significantly longer before releasing it).
In reply to Yeah, MuseScore 4's playback… by ThePython10110
But that's just it. For me playback is not all that "buggy".
I've got a problem with playback speeds/metronome marks in MuseScore 4.2: all scores get played at double speed. A quarter note (crotchet) set to 80 BPM, for instance, actually plays at 160 BPM. This happens when playing my old scores (created with older MuseScore versions) and also when creating new scores in MuseScore 4.2. Does anyone else have this problem? Thanks!
In reply to I've got a problem with… by musicforstrings
I have seen reports of this. You are not alone. There may be something about your setup that is causing this. You should start a new thread about this. In which you tell us about your computer and post a sample score.