Improvements and new features in MuseScore 2.0 stable version.

• Feb 5, 2015 - 20:52

With this forum I'd like to express my opinion about what the MuseScore 2.0 version should include and improve. I've made a similar post 2 weeks before 2.0 beta 1 was released and many of my requests became reality.
First of all I'd like to say for the record that I was a finale user 'till I found out about MuseScore in March 2014. I believe that MuseScore it's the best open-source music composition programme ever existed. It has a lot of professional features and I'm still learning something new every day, for this whole year. Second of all I'd like to say that I'm not demanding anything from anyone because my forum about beta 1 was maybe a little bit misleading about this point. I'm just giving my opinion about MuseScore.
So I'd like to begin with the articulations and ornaments that aren't play-backed (trills, glissandi, fermatas, gruppetos, prall pralls, prall mordents). What's more some of the dynamics (fp, sf, sfz, sff, sffz, sfp, sfpp, rfz, rf, fz) have no velocity, so they're useless in playback unless if you set their velocity which is kind tiring and dull. I insist on fixing the playback because I'm a youtuber and I upload sheet music on you tube. So the playback is kinda essential for me and not only. I've seen loads of sheet music videos in You tube which are made by MuseScore. Furthermore, I'm still a student and I need to hear my scores correctly before Ι hand them to my professors.
What's more I'd like to report some of the major bugs which I've found in 2.0 beta 2. the most important to me is the export as .pdf. The text appear small and the wavy lines (glissandi, arpegios) break up into pieces. Moreover, when I create the parts from an arrangement, everything is messed up. Another bug occurs when I open big scores. In these cases MuseScore is lagging very much and it becomes very slow, something that annoys me because I waste a lot of time to edit a score.
That's my advice for the developers. I'm not ordering them to do what I asked for. I'm just requesting some things, but the final decisions are theirs. It's their programme and they can do whatever the wish. Whatever happens I'll still continue to support MuseScore as much as I can. I look forward to the upcoming release of 2.0
P.S.: Sorry if I have any mistakes but English is not my mother language...

Comments

• Feb 6, 2015 - 00:41

For the record, 2.0 is not likely to get any new features beyond what it already has. If we keep adding new features, it will never release. We are focused more on fixing bugs. As mentioned, we know about the Qt bug that causes PDF export to be messed up on Windows, and it appears it will be fixed soon. It's also known, but unavoidable for now, that If you have large scores it will be slow. THat's not a "bug" per se, just limitation of the current layout algorithms. Some day this may be improved, but don't expect to see that before the release of 2.0 if you want to see it this year :-)

If you have other bugs you want to see fixed, be sure they are properly logged in the issue tracker.

New features will come in future releases, no doubt. Playback improvements will doubtless come, but as before, they are prioritized lower than notation features.

Reply

• Feb 8, 2015 - 17:31

I don't know what you mean at all. Parts work veyr well for me. If you are seeing a specific problem with a specific score following a specific series of steps, please start a new thread, and post the score you are having problems with as well as precise step-by-step instructions to reproduce the problem you are seieng. Feel free to incldue a screneshot too if you feel it would help, but most important is that you post the actual score and the precise steps to follow.

Reply

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