Today marks the release of MuseScore Piano Roll. Piano Roll is a popular and convenient method to display piano notation in a way that not only simplifies learning a new piece for novice musicians who lack a teacher, it also beautifully visualizes each score.
(Video captured from https://musescore.com/classicman/scores/33715 )
Give it a try by simply clicking on the Piano Roll icon now available on all solo piano scores. Be sure to tell us what you think in Improving MuseScore.com!
All of these improvements are designed to not only make MuseScore.com the most valuable resource online for sharing and discovering great musical works but for learning them as well.
We hope you’ll be as excited about this new feature as we were to create it for you, and as always we look forward to your feedback.
This is just the first of an exciting series of updates and releases for MuseScore PianoRoll; we're already hard at work on improving the experience!
MuseScore introduces mobile practice mode
Every day hundreds of thousands of people use MuseScore services for practicing music, learning scores or preparing for performances. The Catalog created by the MuseScore community is the biggest score library.
We’ve been recently putting a lot of effort into improving the product for performers, not only on the website but in the mobile app.
At the moment, our App processes scores the same way our desktop solution does. But mobile devices have their peculiarities (mainly because of the screen size and touch-interfaces). It’s not always convenient to read scores using our current mobile app, especially if users don’t want or don’t know how to manage more advanced app settings. Users have to turn pages all the time (even more often than when they use regular paper scores) if they’re using the Play mode. So, they can’t see the next measure when done playing the current one. Also, it’s not clear where to manage such settings as the metronome, tempo or transposing.
Taking all this into account, we’ve launched another update which is aimed at the global improvement of mobile apps for professional performers and students.
Please, welcome Practice Mode. Now you’re one click away from entering a special mode, aimed at simplifying the process of playing an instrument and learning new scores.
In this mode, users see scores in a "continuous view" shown in one line with perfect readable scaling applied. Simply by clicking the Play button, users hear the metronome intro which is followed by the convenient flow of notes. Users can always see what they’re playing, along with a couple of more measures that are coming up next.
On the same screen, users not only change the tempo, the key or turn the metronome on/off but also play the original sound of the instrument (to hear whether they’re playing it correctly).
This improvement is supposed to make the App more convenient to use, and really, get it on the next level. Now it’s becoming much easier and more comfortable to learn and perform scores from the huge MuseScore catalog.
At the moment, we’re looking for the App and the new mode beta-testers.
To join the beta-testers community, follow the link and click "Become a tester".
After we’ve released the next build supporting the new mode, you just need to install it, open any score and you’ll be immediately redirected to the needed mode. We really hope that this update will visibly improve your experience and help with the development of your musical skills.
We are open to any suggestions and appreciate your help with the development of the new mode. You’re welcome to join us!
MuseScore / Chief Product Officer
P.S. Planned date for the first beta release of the feature - the next week.
Hi! Today we’ve added a new private messages restriction due to the spam issue. Now every new MuseScorer can create only 3 new chats per day. Existing users who registered more than 1 month ago won't experience any private messages limitations.
I hope this restriction will not cause problems for the community, but will actually help us to avoid spam in PMs.
My name is Dmitriy. I’m a Product Manager of MuseScore.
Today we are launching the new group. In this group, MuseScore Team Members will make posts about changes in our products: what we are doing and how we are working.
It won’t be an official group with “dry” marketing texts. The group will contain personal messages from our team members, no matter what their specialization and English language level are. And no censorship or editing here. And, I think, it's a right time to apologize for possible grammatical and lexical mistakes in this text now =)
We are going to use this group to inform our users about all the changes in the project (not only big ones). If you are eager to know what’s going on in MuseScore, you might want to subscribe to this group. But please notice: only team members can create posts here. All posts from non-team members will be deleted: please use Improving MuseScore group for your posts.
At the moment, MuseScore team is working on development of the whole branch of MuseScore products. But, unfortunately, sometimes the importance of issues we are currently solving is pretty hard to see.
In this first post I want to share, what happened this year, with you and also to talk about our plans.
We are going to grow MU to the new level. We believe that Open Digital Technologies is the future of “musicians market”. And here we can be leaders!
Our goal is to make our products the most useful and the most functional for musicians. It means that we should develop as fast as possible: Release new features, make UI better etc.
But in order to go faster, we need to solve some issues which block further development.
Year 2018 started with a huge task: updating the technical platform of MuseScore.com
In the first quarter we implemented new search engine, all groups’ functionality, partially scores functionality. This was a very hard and important work, the result of which is sometimes not obvious for the users (and it is the best result, as usually users see the result of this kind of work only if something has been broken 🙂 )
But if we do it today, tomorrow we’ll be able to do 3 times more.
But it doesn’t mean that we stopped development of new features.
This year we’ve released some updates related to community:
- New community index page with simple search of new text content.
- New WYSIWYG editor in community posts and comments: Now you can create nice and readable messages.
- We’ve relaunched the “MuseScorer Of The Month” project.
- We are making some experiments with “Hubs”. We are trying to make scores searching simpler. This can help to raise the “view count” for content creators.
We are going to solve the spam problem in scores, and a lot of plans with the “Browse” page and “Hubs” page improvements.
We are continuing to contribute into the MuseScore notation software. In the beginning of the year version 2.2 was released. There was a lot of important improvements. Now we are developing 2.3 and focusing on development of 3.0.
Our major goal here is to make the 1st public beta version release for mass testing. We should make 3.0 as stable as possible to achieve this goal.
Here we are also having much work to do. We are moving our apps to the new technology platform which helps us to make the apps more useful and compatible with design requirements for iOS and Android. At the moment, our apps are in public beta testing, and I hope, that in near future new apps will be released in stores.
Then, we are going to improve UI of the apps. Also we are going to work on the integration of mobile functions with musescore.com (Mobile app should be a real alternative of the mobile version of the site).
We are working hard to make a lot of improvements in every product. Unfortunately, in big projects like our, sometimes shit happens and we break some of the features from time to time. We are testing all the functions before releasing, but nobody except for real users knows the real cases of using products. So real users are the best testers for us! We are fixing the bugs really quick thanks to our users’ quick feedback.
All our team members are ready to solve the issues: every staff member takes time to read and to answer our users’ questions in “Improving MuseScore” group, and to reply to some support requests.
Finally, I'd like to introduce our team responsible for the products development.
@abruhanov - our leading developer. He is responsible for the development of all new features and partially for platform updates.
@ijoy14 - Backend developer.
@jilizart - UI-developer. He is responsible for the visual part of development.
@gor42 - Lead UI/UX. She is in charge of all visual changes
@Stanislav Botev - Lead mobile developer. All changes in mobile apps is a result of his job.
@vashue - Lead Analyst. When he sleeps he thinks about the data. When he doesn't sleep he work with data. When he eats, he eats data.
@valerussk - Lead Support Engineer. She answers all your questions from the feedback form and also she can help you in support groups on the website.
And me - I’m CPO of MuseScore and responsible for all MU products development including the website.
I hope that users will be happy with the results of our work. Because all that we are doing - we are doing for you: if you are happy - we are growing.