Nightlies seem to not be backwards compliant
I created a score with Nightly 4829 and, I tried opening it with Nightly 4859 and it doesn't work.
Could something be done about this to facilitate bug reporting, or, would investing work in this be useless?
Thanks!
Comments
What error do you see? I have older 2.0 nightly scores and they open without error. The version number in the later nightlies would be higher than the older ones but that shouldn't cause issues.
In reply to What error do you see? I have by schepers
Nightlies are not meant to be backward compliant. Any nighly can break your scores made with another nightly. It's already a lot of work to make stable version backward compliant but there is no way to make development version backward compliant. If you use nighlies, please, don't use them for serious work but only for testing purpose.
If you do encounter a problem opening a MuseScore 1.1 file in a nightly, please open a bug report and exact steps to reproduce, together with a file.
In reply to Nightlies are not meant to be by [DELETED] 5
"Nightlies are not meant to be backward compliant. ". While this may be true in theory, I've never encountered it yet. The only thing I notice and intend to report once the nightlies get more stable and approach beta status is how specific elements are being imported incorrectly.
Daniel, I have many sample and real scores including 1.0, 1.1 and 2.0 (various versions) and they all open in the latest 4873 build. Maybe there is an issue with your specific build.
In reply to No issue opening older MS files in 2.0 by schepers
Yup, I think it was 4829 which I chose because the order the nightlies are displayed on http://prereleases.musescore.org/windows/nightly/ is in reverse and it has happened many times to me that I have actually picked the oldest available nightly instead of the newest one....
I don't have the scores anymore, I deleted them and decided to rewrite them, they weren't very long, but it was a bit annoying.
It just gave that error message that it can't open the score, I don't know why I didn't take a screenshot of it...
schepers, do report any bugs you see now, before 2.0 is going to be out, it is really dissapointing when major versions come out and basic stuff doesn't work, this just leads to MuseScore loosing rep and creates a bad track record for it even though future work would be done.
If major institutions have bugs with basic stuff using MuseScore, they're just going to say Sibelius next time and ditch MuseScore alltogether, so, even though the following statement is kind of a repeateing one: "First things first"...
In reply to Yup, I think it was 4829 by tonyjustme
If the error window said "your version of MuseScore is too old" then that was it. If it just said "can't read score" then thats another issue. A screen shot would have been somewhat helpful.
I'm not going to report issues until a feature freeze, unless the error is a show stopper. There are others here that do so, and generally find things that I wouldn't even dream of trying. The problem is that many of these reports don't get addressed or are unintentionally "fixed" in the next release and so were very transient. Personally I find the nightlies too unstable and so I just play a little. The code base is still changing quite a bit and its not even close to alpha status much less release. Once development switches from major additions and tinkering to freeze and bug fix, I will start reporting again.
Release versions 1.0 and 1.1 work fine, so the debugging process works. There's a large base of users with many reporting their findings. When 2.0 starts to approach release I'm confident this user base will find the bugs and they will be dealt with.
In reply to If the error window said by schepers
Yes, it did say my MuseScore version is too old, now that you wrote that I remembered the error.
It's GOOD to work with Nightlies, because, they inherently become the next prerelease and then the stable one.
I mean, this is how I understand the development proccess, lasconic could probably tell me if I'm right or wrong, and, also, in order to have whatever bug that wrecks your score fixed, nightlies is the only place where you're going to get it fixed so you can get on with work otherwise you'll be stuck waiting for the next stable release wishing you had money to buy Sibelius...
So, as for me and what I do, I ride the cutting edge of development with the nightlies and I don't mind bugs I encounter, I just report them.
What developer WOULDN"T love miriads of testers behind him basically doing his testing part for free.
It's the testing part that is mostly annoying to developers, because it's the case where one has to think of all of the possible variables in which his software would crash and so, with loads of testers like me riding the wave, the developer can just turn into a fixer and spare himself some work.
In reply to Yes, it did say my MuseScore by tonyjustme
How I despise the uselessness of that subject line copying the first words of my comment...