MuseScore 2.0.1 is released

• 2 years ago

A month after the release of MuseScore 2.0, we are pleased to announce the availability of MuseScore 2.0.1 which comes with 100+ bug fixes.

When we released 2.0, it had been more than two years since the release of 1.3. This was deliberate, as we knew 2.0 was a major undertaking and we wanted to get it right, but we also knew we wanted to have more frequent releases going forward. Today we are taking that first step with MuseScore 2.0.1. This release fixes more than 100 bugs. We focused on addressing all the crashes and score corruption issues that we could, and also a number of problems where the results of certain commands could be lost upon save and reload. Quite a few other less serious but still annoying bugs were fixed as well.

While the MuseScore 2.0.1 release was all about increasing stability, we are also working on new features and other improvements and hope to have another release to present before the end of the year

The response to MuseScore 2.0 has been overwhelmingly positive so far, and we hope this 2.0.1 update demonstrates our commitment to justifying that excitement and making sure MuseScore remains the choice of so many musicians around the world.

musescore-2.0.1.png


Comments

In reply to by shoogle

Thanks for your reply. All software upgrades had been normal until I tried to add the latest Musescore. This is what happened.

my sources list includes this line:

deb http://ppa.launchpad.net/mscore-ubuntu/mscore-stable/ubuntu trusty main

$ sudo aptitude update
$ sudo aptitude upgrade
[sudo] password for david:
Resolving dependencies...
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 20 not to upgrade.
Need to get 0 B of archives. After unpacking 0 B will be used.

I was puzzled by the "20 not to upgrade", which I have not previously seen, so I did

$ sudo aptitude full-upgrade
The following NEW packages will be installed:
libqt5clucene5{a} libqt5help5{a} libqt5xmlpatterns5{a}
qml-module-qtquick-localstorage{a} qml-module-qtquick-window2{a}
qml-module-qtquick2{a} qml-module-qtwebkit{a}
The following packages will be upgraded:
libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5opengl5
libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5sql5 libqt5sql5-sqlite
libqt5svg5 libqt5test5 libqt5webkit5 libqt5webkit5-qmlwebkitplugin
libqt5widgets5 libqt5xml5 musescore qtdeclarative5-localstorage-plugin
qtdeclarative5-qtquick2-plugin qtdeclarative5-window-plugin
20 packages upgraded, 7 newly installed, 0 to remove and 0 not to upgrade.
Need to get 27.8 MB of archives. After unpacking 26.7 MB will be used.
The following packages have unmet dependencies:
webapp-container : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
libqt5organizer5 : Depends: qtbase-abi-5-2-1 which is a virtual package.
qtdeclarative5-dialogs-plugin : Depends: qtbase-abi-5-2-1 which is a virtual package.
Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
webbrowser-app : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
qtdeclarative5-privatewidgets-plugin : Depends: qtbase-abi-5-2-1 which is a virtual package.
libqt5multimedia5 : Depends: qtbase-abi-5-2-1 which is a virtual package.
libqt5positioning5 : Depends: qtbase-abi-5-2-1 which is a virtual package.
liboxideqtquick0 : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
qtdeclarative5-ubuntu-ui-toolkit-plugin : Depends: qtbase-abi-5-2-1 which is a virtual package.
Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
libqt5sensors5 : Depends: qtbase-abi-5-2-1 which is a virtual package.
appmenu-qt5 : Depends: qtbase-abi-5-2-1 which is a virtual package.

I looked a bit further and found that musescore:I386 is available to be installed, but the dependencies for that are basically all 386 libraries plus the removal of some things, so I decided that's a bad idea. See following:


$ sudo aptitude install musescore:i386
The following NEW packages will be installed:
libatk1.0-0:i386{a} libcairo2:i386{a} libdatrie1:i386{a} libegl1-mesa:i386{ab} libegl1-mesa-drivers-lts-utopic:i386{a}
libegl1-mesa-lts-utopic:i386{ab} libgbm1:i386{a} libgbm1-lts-utopic:i386{a} libgdk-pixbuf2.0-0:i386{a} libgraphite2-3:i386{a}
libgtk2.0-0:i386{a} libharfbuzz0b:i386{a} libicu52:i386{a} libjasper1:i386{a} libopenvg1-mesa-lts-utopic:i386{a} libpango-1.0-0:i386{a}
libpangocairo-1.0-0:i386{a} libpangoft2-1.0-0:i386{a} libpixman-1-0:i386{a} libportaudio2:i386{a} libqt5clucene5:i386{a}
libqt5core5a:i386{a} libqt5dbus5:i386{a} libqt5gui5:i386{a} libqt5help5:i386{a} libqt5network5:i386{a} libqt5opengl5:i386{a}
libqt5printsupport5:i386{a} libqt5qml5:i386{a} libqt5quick5:i386{a} libqt5sql5:i386{a} libqt5sql5-sqlite:i386{a} libqt5svg5:i386{a}
libqt5webkit5:i386{a} libqt5widgets5:i386{a} libqt5xml5:i386{a} libqt5xmlpatterns5:i386{a} libthai0:i386{a} libvorbisfile3:i386{a}
libwayland-client0:i386{a} libwayland-egl1-mesa-lts-utopic:i386{a} libwayland-server0:i386{a} libxcb-icccm4:i386{a} libxcb-image0:i386{a}
libxcb-keysyms1:i386{a} libxcb-randr0:i386{a} libxcb-render-util0:i386{a} libxcb-render0:i386{a} libxcb-shape0:i386{a}
libxcb-shm0:i386{a} libxcb-util0:i386{a} libxcb-xfixes0:i386{a} libxcb-xkb1:i386{a} libxcomposite1:i386{a} libxcursor1:i386{a}
libxinerama1:i386{a} libxkbcommon-x11-0:i386{a} libxkbcommon0:i386{a} libxrandr2:i386{a} musescore:i386{b}
The following packages will be upgraded:
libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5opengl5 libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5sql5 libqt5sql5-sqlite
libqt5svg5 libqt5webkit5 libqt5widgets5 libqt5xml5
14 packages upgraded, 60 newly installed, 0 to remove and 6 not to upgrade.
Need to get 60.9 MB of archives. After unpacking 159 MB will be used.
The following packages have unmet dependencies:
libegl1-mesa:i386 : Conflicts: libegl1-x11 which is a virtual package.
Conflicts: libegl1-x11:i386 which is a virtual package.
webapp-container : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
libqt5organizer5 : Depends: qtbase-abi-5-2-1 which is a virtual package.
qtdeclarative5-dialogs-plugin : Depends: qtbase-abi-5-2-1 which is a virtual package.
Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
webbrowser-app : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
qtdeclarative5-privatewidgets-plugin : Depends: qtbase-abi-5-2-1 which is a virtual package.
xserver-xorg-lts-utopic : Conflicts: libegl1-mesa:i386 (>= 0~) but 10.1.3-0ubuntu0.4 is to be installed.
libqt5multimedia5 : Depends: qtbase-abi-5-2-1 which is a virtual package.
qtdeclarative5-window-plugin : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
qtdeclarative5-qtquick2-plugin : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
libqt5positioning5 : Depends: qtbase-abi-5-2-1 which is a virtual package.
qtdeclarative5-localstorage-plugin : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
liboxideqtquick0 : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
qtdeclarative5-ubuntu-ui-toolkit-plugin : Depends: qtbase-abi-5-2-1 which is a virtual package.
Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
musescore : Conflicts: musescore:i386 but 2.0.0+dfsg1-0ubuntu~trusty1 is to be installed.
musescore:i386 : Depends: musescore-common:i386 (>= 2.0) which is a virtual package.
Conflicts: musescore but 1.3+dfsg-1 is installed and it is kept back.
libegl1-mesa-lts-utopic : Conflicts: libegl1-mesa:i386 but 10.1.3-0ubuntu0.4 is to be installed.
Conflicts: libegl1-x11:i386 which is a virtual package.
libegl1-mesa-lts-utopic:i386 : Conflicts: libegl1-mesa:i386 but 10.1.3-0ubuntu0.4 is to be installed.
Conflicts: libegl1-x11:i386 which is a virtual package.
libqt5webkit5-qmlwebkitplugin : Depends: qtdeclarative-abi-5-2-1 which is a virtual package.
libqt5sensors5 : Depends: qtbase-abi-5-2-1 which is a virtual package.
appmenu-qt5 : Depends: qtbase-abi-5-2-1 which is a virtual package.
The following actions will resolve these dependencies:

Remove the following packages:
1) appmenu-qt5
2) checkbox-gui
3) liboxideqt-qmlplugin
4) liboxideqtcore0
5) liboxideqtquick0
6) libqt5feedback5
7) libqt5multimedia5
8) libqt5organizer5
9) libqt5positioning5
10) libqt5sensors5
11) libqt5webkit5-qmlwebkitplugin
12) libunity-webapps0
13) qtdeclarative5-accounts-plugin
14) qtdeclarative5-dialogs-plugin
15) qtdeclarative5-localstorage-plugin
16) qtdeclarative5-privatewidgets-plugin
17) qtdeclarative5-qtfeedback-plugin
18) qtdeclarative5-qtquick2-plugin
19) qtdeclarative5-ubuntu-ui-extras-browser-plugin
20) qtdeclarative5-ubuntu-ui-toolkit-plugin
21) qtdeclarative5-window-plugin
22) ubuntu-desktop
23) unity-webapps-common
24) unity-webapps-launchpad
25) unity-webapps-qml
26) unity-webapps-service
27) unity-webapps-youtube
28) webapp-container
29) webbrowser-app
30) xul-ext-unity
31) xul-ext-websites-integration

Keep the following packages at their current version:
32) libegl1-mesa:i386 [Not Installed]
33) musescore:i386 [Not Installed]

Leave the following dependencies unresolved:
34) indicator-appmenu recommends appmenu-qt5

Accept this solution? [Y/n/q/?]

In reply to by shoogle

thanks again for quick reply. I had always thought that aptitude and apt-get were interchangeable. Apparently I'm wrong. apt-get worked perfectly and musescore 2.0 is now installed. Thank you. Now I can have some fun playing with it.

Is there a way to edit my previous reply? I didn't realise myself how long it is!

In reply to by davidjmcq

Unfortunately you can't edit posts once someone has replied to them, but don't worry about it this time.

I thought apt-get and aptitude were equivalent too, but I did a bit a research and it seems aptitude went out of favour with Ubuntu a few years ago. It seems that aptitude is just a frontend and it is really just calling apt-get in the background, so calling apt-get yourself saves an extra step.

Musescore is the best and simplest notation software I know.
The only feature not implemented is the realtime notation, I hope that in the future it will be added.
Thanks.

In reply to by Isaac Weiss

Real time MIDI interpretation is difficult, but there is a request for a similar feature that would overcome many of these difficulties.

Basically the user enters a "record mode" where they are given an audible metronome beat. The metronome beat is used to divide measures into quantised chunks. The the timing of the user's NoteOn and NoteOff event are rounded to the quantisation level (e.g. "1/8th note") and passed to the existing algorithm used for importing .mid and .kar files. The process is equivalent to selecting the "shortest note" on MIDI import in MuseScore 1.3

Lower down that page I expanded the request to include the use of a MIDI sustain pedal to control the jump to the next quantised unit. This allows the user to control the input tempo to make it easier to enter difficult passages accurately.

In reply to by Marc Sabatella

Well, if MuseScore was set up for realtime processing there wouldn't need to be a feature request :D

You could simplify realtime processing by delaying MIDI voice/note interpretation to the end of each bar (see attached animation). Could the current MIDI algorithm (for .mid files) handle note and voice interpretation one bar at a time?

As for the issues this helps with...
Quantisation helps to solve note length issues which would arise if you were to use the raw timings of the NoteOn and NoteOff events. If a key is down when the metronome ticks then it counts as a note, otherwise it doesn't. This gets you 100% accuracy with all regular rhythms (i.e. not triplet/tuplets, but there are ways around this).

It also solves the issue of "is this a staccato crotchet or is it a quaver and a quaver-rest?". The user would be forced to enter "what you want to see" (a crotchet), not "what you want to hear" (a quaver), so any ornamentation or staccato would be added manually afterwards. (Again, there are ways around this, but the issue isn't that important.)

Using the sustain pedal to advance a quantisation step allows the user to control the pace at which they have to play the notes. In "Record mode" the user would "perform" the piece at a slow tempo to ensure accuracy, but could use the pedal to advance through an easy section very quickly, or use it to slow down while inputting a difficult section.

Attachment Size
RealTimeMIDI.gif 213.97 KB

Will scores created in 2.1 for Yosemite still be openable, readable and editable by an earlier version of Musecore? I have an older Apple aptop with OS X 10.6.5 that will run an older version of Musecore but not the latest version. I need to use the portable to work on the score when travelling and can't afford to replace the computer just to upgrade this software.

In reply to by AlrickH

No, scores created with 2.0.1 are not readable by MuseScore 1.x. But scores created with MuseScore 1.x are readable by MuseScore 2.0.1. You could try to work with MusicXML instead of native files to exchange scores from 2.0.1 to 1.3.

In reply to by Isaac Weiss

Thanks you. The problem is solved. I checked and my computer has OS X 10.7, so I have downloaded MuseScore 2. The earlier advice to transfer files via MusicXMK is still useful when one has a computer unable to run recent operating systems.

Guys, I have an issue when opening the app. When I hit the Icon, it gives me an error screen right away.
_____
Dyld Error Message:
Library not loaded: @executable_path/../Frameworks/libvorbisfile.3.dylib
Referenced from: /Applications/MuseScore 2.app/Contents/MacOS/mscore
Reason: Incompatible library version: mscore requires version 7.0.0 or later, but libvorbisfile.3.dylib provides version 6.0.0
_____

I run Maverics at the moment, so It should run. I have encountered this problem ever since version 1.3 came out, so I have run version 1.2 ever since, and it really starts to bugging me! What can I do?

It appears that a Linux release of 2.0.1 is far, far down the priority list, and I have never been able to get the instructions for compiling from source to work. However the Windows release seems to work with Wine 1.6 with no problems. It's kind of a bummer that there is no native Linux release, but what can you do.