I Do Not Think Musescore 3.0 Was Ready For Release

• Jan 5, 2019 - 16:01

So so sorry I removed 2.3. This 3.0 is too buggy... I can crash and lock it up with a half dozen operations... very frustrating. Well, back to Sib... for a while.

Yes yes, I know... "well if you don't list what's happening, how can we fix it"...
Should not be happening with an official release... and I don't have time... I have work to get done.


Comments

You are not the first to say that, in fact it was probably me. I realize that everyone doesn't have the time to test version 3 so it can be fixed, so I understand what you are saying. I continue to use version 2.3.2 for anything important to me. I also have time to use version 3 for other things so I can help to get it to the point that it will be acceptable to people like you. There was no reason to remove 2.3.2. In fact, if you didn't remove it, it's still there because installing version 3 does't automatically delete version 2.x.

You can always use MuseScore 2.3.2 until MuseScore 3 becomes good enough for you. We get hundreds of positive feedback responses about the MuseScore 3, auto-placement and other new features. So, this is the case where autoupdates will help. Just stay tuned and try updated version (like 3.0.1) when it is ready and you will find MuseScore 3 as stable as it has never been before.

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