Will MuseScore 3.0 definitely not be able to open pre-2.0 scores?
If this is the case, a lot of code catering for mscVersion() less than 200 can get removed and/or simplified.
Anyway, at https://github.com/musescore/MuseScore/pull/2576 you'd find a PR doing this ;-)
Comments
It's up to us as a (developer) community to decide... if nobody takes the challenge then, yes 3.0 will not be able to open/import 1.X files. Of course, it's easier to delete the whole stuff, than take the challenge :) Are you sure you don't want to try it before deleting it ?
In reply to It's up to us as a by [DELETED] 5
Subtle hint ;-)
We should at least remove every tweak for mscVersion() > 114 and < 200, shouldn't we?
In reply to Subtle hint ;-) We should at by Jojo-Schmitz
As I said, if we do remove them now, it will be harder to make the import later.
In reply to As I said, if we do remove by [DELETED] 5
Anything between 1.3 and 2.0 is worth being kept?
In reply to Anything between 1.3 and 2.0 by Jojo-Schmitz
Is it really a wise decision to remove support for 1.x files and lower? It seems like conversion works fairly well.
I probably still have some pre 1.0 files around that I've forgotten about and already 2.0 won't open those, correct? I have many more 1.x files that would require keeping old MS versions around. Someday those old versions of MS might not work on newer Windows.
In reply to Is it really a wise decision by schepers
No, not correct. MuseScore 2 should be able to open any score from MuseScore 0.9.6 and up including MuseScore 1.3.
In reply to No, not correct. MuseScore 2 by [DELETED] 5
And support for pre-0.9.6 was removed in 1.2 IIRC
In reply to And support for pre-0.9.6 was by Jojo-Schmitz
2.0.3 actually will open scores from 0.9.5, with only a warning similar to the corruption check.
In reply to 2.0.3 actually will open by Isaac Weiss
Hmm, ISTR that 1.3 refused to open them
In reply to Hmm, ISTR that 1.3 refused to by Jojo-Schmitz
I'm seeing 1.3 do it, and 2.0.3 after a warning. Try with this one:
In reply to 2.0.3 actually will open by Isaac Weiss
Yes, a warning that could get ignored ("Load anyway"), not a plain refusal
In reply to Anything between 1.3 and 2.0 by Jojo-Schmitz
Anything between 1.3 and 2.0 is worth being kept?
It's not worth being kept. It's worth being transferred in its own class. And anything before 1.3 too, if possible.
In reply to Anything between 1.3 and 2.0 by [DELETED] 5
It was always stated that files created with 2.0 nightly builds may not load in 2.0
In reply to It was always stated that by Jojo-Schmitz
I'm not talking about nightlies here. Nightlies are not meant to be used for anything serious, so files are no supposed to be reopened except for development purpose.
In reply to I'm not talking about by [DELETED] 5
That's what I meant with We should at least remove every tweak for mscVersion() > 114 and < 200, shouldn't we?
In reply to That's what I meant with We by Jojo-Schmitz
Sure anything between MuseScore 1.3 and MuseScore 2.0 can go. > 114 and < 206 in fact.
https://musescore.org/en/developers-handbook/version-information
In reply to Sure anything between by [DELETED] 5
OK, I'll amend my PR accordingly.
moving the 114 stuff to some 'Import old files' class might be in a later PR or by someone else ;-)
In reply to Sure anything between by [DELETED] 5
New PR at https://github.com/musescore/MuseScore/pull/2581.
In reply to It's up to us as a by [DELETED] 5
From a user point of view, I find normal to be forced to use an intermediary version (will be 2 here) to convert old files (1.3) before begin able to use them with the current version (3.0).
Especially if:
-it is announced and explained in advance
-the necessary version to use (2.0) stays easily available
-it enables the developpers of the new version to concentrate on new features and enhancements without being forced to maintain old code
Fred
You might want to export them all as pdfs, then convert using pdf converter when Musescore 3.0.0 comes out, that's worth a try.
In reply to You might want to export them by Elwin
Use MusicXML, definitely not PDF.
Is it coming out soon? I really hope I can convert 2.0 files to 3.0 version
In reply to Is it coming out soon? I by bumble02_omit@…
There is no release date, the work just started a couple of months ago. In any case, yes, MuseScore 3 will be able to open MuseScore 2 files. This discussion is about the ability to open 1.x files in MuseScore 3.
In reply to There is no release date, the by [DELETED] 5
So why don't people concerned about this open the 1.xx files in MS2 and save them?
If you have too old a computer for MS2 your more important challenge will be to have a machine that can handle MS3 by the time it rolls around. And that machine in turn will be able to handle MS2. Etc.
As a non-developer, all I can offer is a suggestion from the user point of view. Long-term users will probably know that 2.0 can open 1.x files; so if 3 can open 2, then 2 can be used as a converter. Thus the need to retain the ability to open 1.x files with 3 is small to non-existant.
However: Newer users may very well not know any of the above history, so it might be quite useful for MuseScore 3 to show a pop-up warning upon any attempt to open a pre-2.0 file, with wording something like this:
In reply to As a non-developer, all I can by Recorder485
Something like:
See https://musescore.org/en/node/109166#comment-492566 above.
In reply to Something like: by Isaac Weiss
Yes, something along those lines. But if I understood the comments earlier in this thread correctly, 2.0 will open anything prior, so why not specify 2.0 as the 'conversion app'?
Also, it would be very convenient if there was a live link to the proper download page in that popup. I presume that can be done without jumping through too many hoops?
In reply to Yes, something along those by Recorder485
The above image is not a mockup; it is what MuseScore 2.0.x actually does when opening a score from MuseScore 0.9.5 or earlier.
In reply to The above image is not a by Isaac Weiss
And 3.0 does the equivalent currently. That's why I started this topic about deleting the now apparently unnecessary code. Adding a link to the section of the download page might indeed be a good and easy Addition.
Like this:
![error.png]( "error.png")
The last line of that messages is the addition. the rest shows currently already.
In reply to And 3.0 does the equivalent by Jojo-Schmitz
Well, it's good to see you guys are ahead of me. ;o) And I'm glad the suggestion of adding a download link was helpful.
I guess what made me think of that is that I have spent 'way too much time recently battling with Microsoft in an attempt to maintain our old 'Dragon' in a functional state so we can continue to use a number of legacy versions of software that run on XP. Microsoft has dumped XP off the cliff, of course, but worse than that, their servers won't even answer a call from IE8 (the latest IE version that XP can run, apparently). But instead of informing me that my browser version was 'not supported', Microsoft spews out the standard error 404 text which tells me to check my connectivity, spelling of the URL, or try again later.... >Grrr<