Musescore has significant UX issues and things have been getting worse with each release. Instead of adding new complex functions that are already done better by others they should try to fix the basic things first.
What are some of the UX problems you're thinking of? Personally I've been pretty happy with it so far. (My main point of comparison is Sibelius, which I used until I went all-Linux three or four years ago.)
Oh there are some. Some of them have been fixed in MS3
The one that's almost a show-stopper to me and I realized it only recently: if you insert notes (between existing notes), it won't move the existing notes to the right, but it will instead create this "long" bar with more notes than your time signature.
There are so many weird things like that, but the one that infuriates me the most is the inability to move notes left and right. The answer is to cut and paste, which - if you have already written out multiple bars but realize one note is in the wrong place or you’re a quarter note off - becomes an exercise in frustration.
I recommended this software to someone, and my first words were: “This is a powerful program, but it has got a steep learning curve. It feels like it was designed and written by a programmer who also plays music”
The answer from this person two weeks later: “You were totally right. Very frustrating.”
Scoring directly in the software is a huge pain + buggy midi support often forces me to use a different software and then import the midi into musescore for printing.
I'm still on 2 too, mostly because I recall being unable to use the plugin interface ionsome early version of 3, in late 2018; not sure if it was being reworkwd on or whatnot, but since I had been using MS to author some books and lessons for my students, I was already relying on the scripting, with no time to learn something new or wait for the APIs to work again. Since I'm stuck in this version limbo, I use a library I wrote in Python to manipulate mscx files. I think thos is also a mini-rant on how little FOSS software seems to care about backwards conpatibility. Still, v2 still is much better than any other notation software I tried so I'm not switching.
Comments
I feel they are on the wrong path.
Musescore has significant UX issues and things have been getting worse with each release. Instead of adding new complex functions that are already done better by others they should try to fix the basic things first.
What are some of the UX problems you're thinking of? Personally I've been pretty happy with it so far. (My main point of comparison is Sibelius, which I used until I went all-Linux three or four years ago.)
Oh there are some. Some of them have been fixed in MS3
The one that's almost a show-stopper to me and I realized it only recently: if you insert notes (between existing notes), it won't move the existing notes to the right, but it will instead create this "long" bar with more notes than your time signature.
Really
There are so many weird things like that, but the one that infuriates me the most is the inability to move notes left and right. The answer is to cut and paste, which - if you have already written out multiple bars but realize one note is in the wrong place or you’re a quarter note off - becomes an exercise in frustration.
I recommended this software to someone, and my first words were: “This is a powerful program, but it has got a steep learning curve. It feels like it was designed and written by a programmer who also plays music”
The answer from this person two weeks later: “You were totally right. Very frustrating.”
Send a tweet to Martin Keary / Tantacrul. He loves to hear about people's ux issues with musescore
Scoring directly in the software is a huge pain + buggy midi support often forces me to use a different software and then import the midi into musescore for printing.
I thought v3 was a big improvement on v2.
Here I am still stuck with v2 on Linux Mint.
I'm still on 2 too, mostly because I recall being unable to use the plugin interface ionsome early version of 3, in late 2018; not sure if it was being reworkwd on or whatnot, but since I had been using MS to author some books and lessons for my students, I was already relying on the scripting, with no time to learn something new or wait for the APIs to work again. Since I'm stuck in this version limbo, I use a library I wrote in Python to manipulate mscx files. I think thos is also a mini-rant on how little FOSS software seems to care about backwards conpatibility. Still, v2 still is much better than any other notation software I tried so I'm not switching.
Why not just download the appimage?