With the new äpp (this time, the correct version), when the rotation changes while a score is playing, playback continues, and 2–3 seconds afterwards, the screen representation has also caught up, but the controls are unusable: the “jump to beginning” one still works, for example, but the “pause” one becomes a “play” button that does nothing, so the playback can only be stopped by hitting the back button (changing orientation back also doesn’t fix it).
The new äpp plays back songs in a way so legato that the silence between two same notes of a voice, especially when they’re of the same pitch, is almost inaudible.
Compared to that, the Songbook äpp has much better sound. (It also sounds completely differently. Which soundfonts do either use?)
I've just downloaded the new Android app and it looks very promising.
However, one of uts most useful features (at least to me) is not working properly. If you select any song, transpose it, and export it to PDF, the PDF will show original (not transposed) chords and notes.
This used to work ok in previous versions of the app.
Thanks for your wonderful work.
I create and maintain a score on my laptop. I upload the score to the musescore site. I check my account in musescore.org from my laptop and it is indeed there with my recent changes. but when I try to access it via my tablet with the app, the latest version of the score does not appear, only the original version (with missing parts).Also, many times when I navigate to MyScores in the app, I'm greeted by an empty screen. Is there a caching problem with the app? Can caching be turned off, if so?Very annoying bug in an otherwise helpful app.
• The font is still low quality (like a low resolution scan)
• Stave texts overlap with the stave and with each other
• Stems and beams are a mess, often missing hooks and dots
• Coloured fret numbers are rendered as black
These scores display perfectly on the web, in the desktop version and in Android Songbook but are a mess in Android MuseScore. On a positive note, the user interface looks good and the mini score previews look correct, (including stems, beams, dots and colour!)
In the new MuseseScore app, version 2.0.1, there are quite some rendering issues:
The lyrics dash as well as the melisma underscore are rendered too high.
Spaces in lyrics (Produced with Ctrl+Space, e.g. after a stanza number) are rendered as "?".
Lyrics moved to above the stave are rendered below.
The curly brace of a piano staff is too far left.
The measure repeat sign in a single line staff is not on the line, but below.
Also all the dialogs are in English, even though I know that translations are available.
From https://musescore.com/groups/musescore-ios/discuss/5024010 I see that localization is planned for the iOS version 2.0.4, is that true for the Android version too?
Historically, MuseScore has had two mobile apps for Android: a paid one (Songbook) and a free one (MuseScore). There's also a desktop version of MuseScore where users can have Pro accounts that are not linked to any of the apps which means they can't use their premium features there.
The vast majority of users use MuseScore Android to browse scores and in only a couple of years of its existence, about a million users have launched it at least once. These numbers inspire us to move forward and continue improving MuseScore products even further.
Today, I want to announce a significant update that will be released shortly and after which MuseScore will transition to a cross-platform Freemium model.
This means that we'll unify subscriptions and accounts of the two existing apps and the desktop version of MuseScore. This way, Pro users from desktop will finally be able to use all premium features of the mobile app which will help us concentrate our efforts on improving it.
Why are we doing this?
Our business model is 'Make products, not content'
We put a lot of effort into improving our products. Mobile apps are a direction that we deem one of the most prospective ones and where we put the most effort into.
While some companies make their apps free in stores but ask money for the access to scores, we negotiate with right holders of the scores in order to give our users free access to all public scores provided by our community.
We're searching for new competitive monetization models that will allow us to stay on par with market's powerhouses and we want to achieve this by continuously improving our services.
All scores should be available to everyone
This is our core value. Any user from any device should have the most convenient way of accessing scores. The main advantage of the freemium model is that it allows all users to explore the app and upgrade their access if they like it enough. And by 'like' we firstly mean quickly and easily finding what users need or getting a lot of views on their own scores.
Freemium works, it's how the majority of the mobile apps operate
We believe that the freemium model is the most prospective way of the mobile app development and that it'll let us accumulate more resources for turning MuseScore Android from a simple score browser to an invaluable tool for any musician.
Pro users shouldn't have any restrictions when they use our products. From the very first day of our work, we've been thinking how to give more value to pro users. Since then, we've introduced a lot of new features most important of which is being able to access all features of the mobile app. Users who previously bought MuseScore Songbook will soon get the access to the full version of the MuseScore mobile app (to get the access you’ll need to log in to your new account).
Freemium means free
We'd like to note that these changes don't mean our apps will be hidden behind a paywall. The key functions of the app such as search and playback will remain free. However, some extra features like the offline access, opening scores from the local storage and a couple of others will be paid.
We want more feedback and more ideas
We want to make our apps the best and the most useful for beginners and pros alike. That’s why we want to implement as many helpful instruments as we can and looking forward to receiving feedback from you. Bringing all products together will let us concentrate on developing them. If you have any questions or ideas, feel free to share them here or in the ‘Improving MuseScore’ group. Thanks for reading!
I have the MuseScore Songbook installed on my Android devices (tablet, Phone),version 7.0) Intentionally I have chosen to install this app instead of the MuseScore app, because the latter would not open an .mscz e-mail attachment on my Android devices.
I have a choir website where I have links to .mcsz files. When I click such I link I would expect that file to be opened in the MuseScore Songbook app. However this is not the case. The file is magically interpreted by the system as a .zip file. When renaming the file to an .mscz file and clicking it, it says it doesn't have an app associated with it.
However I can open in the Songbook app on my Android devices .mscz files that are sent as attachments with e-mail without any problem.
Opening the .mcsz file links on the choir website on my PC where I have installed MuseScore also works as expected.
I have no clue how to fix this. What is the difference between opening a file that is an e-mail attachment compared to a file in the downloads folder? Or why is there a difference in the way such a file is opened. Because apparently there is.
Probably is it is an Anroid issue, more than it is a MuseScore issue.
Best regards, Martin
Vergleiche mein offizielles PDF:
Hier kann man keine Bilder hochladen, oder?
Is there any way to change master tuning (e.g. A=442hz)?
I want to use MuseScore mobile app to practice cello because the app has many useful features for the beginner, such as ...
1. Play with Metronome and/or Count-In
2. Change Tempo ( to practice from slow to fast )
3. Editable Loop Range ( to practice the specific scale in the long scale practice score. )
4. Play with Score ( this cannot be achieved with MIDI file )
It's almost perfect for me.
If I can change the master tuning to A=442hz, it'll be totally perfect.
Only for the tuning, I have to export the score to MIDI file and play with another app...
(Frage umgezogen von Startseite > Forums > Allgemeine Fragen und Probleme)
Wenn ich unten im Musecore-Fenster (auf musescore.org) unter Apps auf Android klicke (Link: https://musescore.com/android), werde ich zum Playstore weitergeleitet und dort gibt es Musescore (für Android) und Musescore Beta, aber kein Songbook.
Nach dem, was ich bisher hier gelesen habe, brauche ich das (kostenpflichtige) Songbook, um msc-Dateien auf dem Tablet/Smartphone nutzen zu können (ohne sie von musescore herunterzuladen). Stimmt das nicht mehr? Geht das jetzt mit der Musescore-App? Geht das gar nicht mehr?
(Und ergänzt nach der Antwort im anderen Forum:)
Ich nutze zwar schon länger Musescore, aber hatte bisher, soweit ich mich erinnere, noch nie das Songbook, jedenfalls ganz sicher nicht auf dem Gerät, wo ich jetzt die msc-Dateien hören möchte. Die Musescore-App habe ich (neu) installiert.
(Do I have to translate my question?)
All I see is browse scores, my scores, favorites, songbook and settings. All empty except browse scores. Any help?
I am unable to open in MuseScore a mscz-file sent to me as an e-mail attachment. When I download it, my Samsung suggests that I open the file in FileCommander, altough FC has never been given permission to open these files.
When I locate the file and try to open it in its folder, I am told that I don't have any apps installed that can open these files, please check Google Play. Google Play suggests MuseScore, and the circle starts again. The only way to open it, is to upload it to My Scores, and find it in the app.
This happens both on my Samsung pad and my Samsung S9.
As of today (and with yesterday's update to version 2.0.2) I just get a white screen, on 3 different mobile Android devices.
Well, on my mobile phone it works sometimes (but without the German localization?!?), on my 2 10" tablets never.
What the hell is going on here? That version did work yesterday, directly after the update.
On all devices I tried reboot, didn't help.
On one device I tried deinstall and install again: didn't help either!
Please make the MuseScore/Songbook app available for Android TV too.
AFAIK this is basically just a switch to flip in your build environment, but I do see that an Ultimate Guitar app is available for Android TV, so I guess you know how to do it.
I'd love to see and listen to scores in MuseScore on my 55" Sony TV...
On one of my devices (Asus ZenPad "10) the new MuseScore app won't install, error code is -505.
On 2 other devices (aother tablet and a phone, both Android too) it installed cleanly though.
Edit: Solved, I still had the broken Songbook 1.14 installed (the Beta that overwrote Songbook 1.13), removing that and the install of the new app worked.
The sorting of songs in Songbook is case sensitive. Words beginning with an uppercase letter come before words beginning with a lower case letter. So for example "A Taste of Honey" is listed before "A blossom fell". And "Blue Train" comes before "Blue moon". I can't see any good reason for this behaviour and find it something of an irritation. Can I put in a plea for case-insensitive sorting of the song list?
The stems and beams have all but disappeared in the latest release. However, MuseScore Songbook app for Android still displays them correctly as does the website. This applies to tablature scores. Is anyone else having this issue or knows how to fix it?
App version: com.musescore.playerlite 2.0 (1766)
1. Open locale file, loading black, no white spinning circle. And loading online file the loading on the screen sometimes is not white. It takes last using scores screen cache. The title use last opened online score name, and if any settings change in last opened online score will set to the opening local file. If a solo set and the instrument the opening locale file do not have, nothing will show when local file opened until cancle solo setttings.
2. Zooming bubble is not English, it is Russian. And there is no back to original option.
3. Very fast click on settings and mixer button, will cause repeat mixer or settings layers.
4. Metronome click mute and click max will cause no metronome sound. Have to click mute and click max to make it back. And there is no prepare metronome click option.Some score first loading play metronome is on, but some first play metronome is off. It is weird… Seems to relate to last opened online file settings.
5. Songbook title take last online song name.
6. Direct open from file manager trigger open app will cause re-login problem sometimes. Sometimes cause freeze.
7. Songbook three dot menu in locale file need to remove some online options.
8. It really cause a long time to open a file than the old app core. And the lyrics is bad quality.
9.Rotate and on/off control bar bug. Off bar, rotate screen, on bar, get a black control bar.
10. Two fingers zooming on screen need to turn off! It is weird due to no any function now.
11. In search bar, select number of instrument, up to 45, the search run from 1 to 45 every click. Not just wait jump out to filter then search. Every change of number of instrument search once. it takes much time to wait the search.
12. In a 45 instrument score. Only 16 instrument show, if more than 16 instrument the below score will be cut.
13. The in zooming mode need to ignore some system/measure layout settings, especially like page break, system break.
14. the search change of settings apply when back to search list,and score change of settings and mixer apply changes when click back to score is better
15. support google account connnect?
the two scores
in new core
the two score take 2 minutes more in my 1 year old device ( Snapdragon™ 625 ), and take 6 minutes in my 6 years old device ( Exynos 4412 ).
how ever old core without cache temp file, so the two file are open in the two device in 3 seconds.
what is the problem make the slow cache? the CJK words? too many pages?
is it possible faster in new core in this kind of score?
Possibly, I'm just not finding the relevant setting here, but when I change pages within a score in the Android app (in single page mode), it trashes my zoom level every time.
As i want to change pages while playing, without having to sod about, that makes it basically unuseable.
I set it to single page, in portrait orientation, in the hope that I could see the whole page at once (I have it on a bracket, held fairly close to my face), and go to the next page just by tapping. I had to awkwardly adjust the zoom level by pinching, to get the whole page on the screen in portrait mode, without wasted space in the margins. When I've played the music on that page, I want to tap on the right to go to the next page...
When I do that, it zooms back out to show the whole page, with the margins added that I don't want, making the actual music too small to read. I now can't read the new page of music, without putting down or juggling with my chosen musical implement, while I do the awkward pinch to zoom in then slide around to get it lined up on the screen again.
Is there any way of stopping this behaviour? it's exactly what I don't want to happen in a sheet music reader.
I want as little interaction with it as possible, when I'm trying to play music. Anything more than a single tap to turn the page is too much to have to do, but the pinch zoom things is really awkward, and can't possibly be done while playing.
Single page mode in landscape orientation doesn't seem to be useful at all - I can make the music bigger, but I can only move down the page by swiping. I can't do anything with tapping, and i can't easily get to the next page.
Continuous mode in landscape orientation is more useful than single page mode, but appears to rely entirely on swiping to scroll. I assumed I'd be able to go forward or back by one screenful by tapping - like reading on a Kindle, or with the Kindle app.
Please give some more thought to making this app actualy useable while playing an instrument. In my view, I should always be able to see the next section of the music by a single tap, or go back with a single tap, and after I've messed about zooming it how I want it, it should keep it like that, not reset it to an unreadable zoom level so I have to start again.
I've got a lot of use out of MuseScore on my PC, so I don't begrudge the price of the Android app, but it's really not there yet, IMHO. I.e. it isn't yet useful for the most basic thing it's supposed to do - reading sheet music and turning pages, while playing.
Every day we are receiving complaints like "I can't open a file stored on my device with MuseScore app (free version)". So I decided to make a quick note here about that.
Opening files (no matter, stored on your local device or received by e-mail) is available in the paid version of the mobile app called Songbook. So, using the app offline by viewing the downloaded scores - it's, again, about MuseScore Songbook app. You can't do those things in free MuseScore app.
Things have always been like that, please see the old "introduction" article for mobile apps at
Hopefully, I've cleared things out a little bit. And sorry for the inconvenience: I really think that it is not obvious - that's why people are asking about those things every day.
P.S. Just one more thing - to make scores, you need to download MuseScore notation software at https://musescore.org
MuseScore Mobile apps are for viewing and playing scores, not creating and editing them.
in old core musescore, load a file contain 21 page in 6 years old device junst need 3 second.
but in new core musescore, loading a file and making a temp file, the same file, it take my whole new cpu device almost 2 minute!!
and of course the old device take almost 5 minute to load the same file.
the old device 1 page open in old core take 2 second but in new core take 3 minute!!
if the new core coming to the songbook, it will be a disaster!!
the new core make a temp file is good for faster loading page but really take a very long time to load!!
is it hard to solve the slow temp file loading problem?
is it possible faster to load a new file in the later version?
I propose to add a function that permit to add a fixed number of seconds BEFORE the count-in function in playback mode.
This feature leave us the necessary time to fit the instrument (eg. traverse flute)
thank you in advance
Is there any way to hide the cursor during playback? I use Songbook to practice with tracks of the other instruments in the orchestral section. During a performance I will not have the note by note cursor (the conductor does that) and would like to be able to practice that way. (I think I'm using Android Songbook 1.14 Pro, but I can see no way to display that!?)
Lately, MuseScore team has been working on the new version of the MuseScore Songbook mobile app. We’re planning to release a major update that will affect all aspects of the app.
This is going to be a very important update as it is meant to solve a lot of technical issues. Moreover, after its release, we’ll be able to improve the functionality of our apps at a much quicker pace. We have grand plans for mobile platforms (from improving the process of working with notes to deep integration with website and transition to a more convenient payment model)
After you'll launch the updated app for the first time you probably won’t see much of a difference (except for some small changes in the app design that we made in order to comply with App Store and Google Play guidelines)
But inside, we rewrote all the app code completely, from UI to the core functions like note mapping and score playback.
It is a major update from a technical point of view, and, unfortunately, things do not always go smoothly on the first try.
That’s why we invite all MuseScore users to join the beta test and help us find bugs and issues of our new app before it’ll fully replace the current MuseScore mobile apps. We can hire dozens of testers, but no one will do this job better than active users themselves.
To sign up for the beta test, follow the link below:
P.S. iOS beta testing will be available soon.