v2, musescore.com and backwards compatibility.
I'm working on a rehearsal score for our choir and finding the text style issues a bit of a pain.
So I thought I would try v2, (compiled on Linux from the github)
Very nice.
And then I found that musescore.com doesn't like v2 files and that 1.2 doesn't like them either, and there's no export 1.2 function :)
Is this correct, and how long will it be thus, can someone give some timescales ?
I could export via music xml, but this loses the richness that is the beauty of musescore.
I guess I should stick to 1.2 for the time being and be more structured in my tinkering ?
Oh and I lhave long loved musescore, as a rehearsal and learning aid. The android app is great - I take my phone to the gym, put my phone on the dashboard of the bike and warm up with the bass part ...
Jon.
Comments
2.0 is not yet ready for production and AFAIK won't be fo some more months.
MuseScore is backward compatible. MuseScore 2.0 will be able to open files created with MuseScore 1.2. But MuseScore is not forward compatible. MuseScore 1.2 will not be able to open MuseScore 2.0 files.
Regarding MuseScore.com, it only supports the current stable version for the moment, meaning 1.2. MuseScore 2.0 is not yet released and so doesn't exist yet. Your "v2 file" could be not usable in a next gitub checkout.
In reply to MuseScore is backward by [DELETED] 5
The idea of adding a "MuseScore 1.X" format option in the Save As dialog is not a bad one, though. Of course, you'd lose anything not supported by 1.X, amd might be more trouble than it's worth.
Meanwhile though, for those who enjoy playing with the 2.0 builds, you *can* export as musicXML and import that into 1.X with some degree of success.
In reply to MuseScore is backward by [DELETED] 5
Many thanks for the speedy reply.
I see what you mean about backwards compatibility :) I should have said forwards compatibility.
As I'm not a developer, all I can do is put money where my mouth is and buy a subscription to musescore.com.
And v2 will help me - I can read the 1.2 file in, to 2 and change all the dynamics to a silly size to spot them all and cross check that I have manually caught and tweaked the 1.2 versions.
v2. Really does look good.
Jon