Install 2.0.3 ?
On a Win 7 system, I want to install/use 2.0.3 instead of 2.0.2 but I do not want to click the "upgrade" button since I never liked where on my HD 2.0.2 got installed by default. I took all the 2.0.2 defaults since I wasn't sure what was going on.
Now, to install 2.0.3, I propose
1) copy items in /scores/ folder to some safe place.
1a) my scores haven't used anything that I think is complicated, except maybe, linked staves.
2) uninstall 2.0.2 completely
3) install 2.0.3 onto D drive. I assume all MuseScore stuff will use/follow whatever path on D that I give it.
4) copy my saved scores into the new "scores" folder.
I know I will loose any preferences that I have set.
Please confirm this (I hope) simple process.
THX.
Comments
Unless your computer is running low on memory or hard-drive space, there is no good reason for uninstalling the previous version. Two versions of MuseScore can co-habit quite happily on the same computer, as long as they are given different file names when they are installed.
I suggest you download the new version from the website and give it a new name such as MuseScore203 before running the install wizard. This way, if it turns out there are any issues with backwards compatibility, you will still be able to open your existing scores using the version with which you created them.
In reply to Unless your computer is by Recorder485
Again, I think it's a bad idea to keep MuseScore 2.0.2 and MuseScore 2.0.3 on your computer. It will make your life more complicated. They share the same preference file, which one will open if you double click a mscz file etc..? The Windows and Mac package are designed to override the previous version, you should do that except if you have a specific requirement.
Regarding the top poster, your steps looks fine and it should work ok.
(PS: I'm the packager for Windows and Mac OSX)
In reply to Again, I think it's a bad by [DELETED] 5
Thanks LASCONIC, you're the only one who focused my Q (and answered it).
In reply to Again, I think it's a bad by [DELETED] 5
As you know, I do have a specific need to maintain legacy versions of the graphic software we use, but in an ideal world I will eventually be able to dispense with them. That can't happen until all the scores created using 1.3 have been substantively revised (IOW, creating a 2nd edition, as opposed to issuing a 2nd printing). Yes, we can open those 1.3 scores with 2.0, but page make-up and layout aren't stable enough across versions to rely on without submitting the score to a whole new round of proofreading. (When auto-generated system and line breaks change, for instance, we have to review the need for certain courtesy accidentals.) The proofing process is fairly time consuming and therefore expensive, so 1.3 is still sitting there on the task bar, ready to run when needed (generally only when correcting minor errata for future printings).
I have not had any problems with the computer getting confused about where to look for which preference files. Does that issue apply only among the various flavours of 2.0?
In reply to As you know, I do have a by Recorder485
1.x and 2.0 can indeed coexists and even run simultaneously, they also don't collide when installing with all the defaults.
In reply to 1.x and 2.0 can indeed by Jojo-Schmitz
Okay, thanks for the confirmation.
OTOH, based on what Nicolas said it seems I will have to stand corrected as to my earlier comments about running different versions of 2.x on the same machine. It's just as well, too, because I had been considering installing 2.0.3 before I had completed all the scores created with 2.0.1. With this new information, I'll wait on that.
One more question: If a future nightly were to feature a modification that we need, could the nightly co-habit peacefully alongside 2.0.1? I'm still hoping Miwarre will get the max-min spacing control for the melismatic dashes sorted out before we have to publish a set of motets that's been hanging fire for the last few months. I know there were fatal problems with his first attempt to control the SIZE of the dash itself, but I would really like to be able to set the dashes we already have closer than the hard-coded default spacing. There are workarounds I can use to lose dashes we don't want, but inserting hard spaces and hyphens to compensate for too-wide dash spacing is not practical.
In reply to Okay, thanks for the by Recorder485
Nightlies do generally coexist well with released versions, and they normally use different settings as well (so you can have different Preferences for each), although I guess that might somewhat OS-specific.
What generally does *not* work, however, is creating with a nightlly and then opening that score in a released build. Not only will a score created in a nightly build not open in the *previous* released version, there is a very real chance it won't work in the *next* released version either. That is, no promise are made regarding compatibility of nightly builds with other builds. So you really don't want to depend on them for any real work.
In reply to Nightlies do generally by Marc Sabatella
Awkward, but understandable.
I need to go find the thread from last year about spacing control of those dashes and see if there's any chance of getting that issue back on the table. Possibly it could be addressed via plug-in??
In reply to Awkward, but by Recorder485
As far as I know there is no particular issue with this, it just hasn't been merghed yet. It would represent a somewhat incompatible change so it would only be in "master" builds most likely (although if the setting is simply ignored in previous releases, that wouldn't be so bad). See https://musescore.org/en/node/87841 for the original discussion, including a link to the issue and PR created for this.
In reply to As far as I know there is no by Marc Sabatella
Thanks; I'll get ahold of Miwarre and ask if it might be possible to do this via plug-in until the next master build comes out.
In reply to Okay, thanks for the by Recorder485
You can have as many versions installeed as you want, if you take extra care about where they install. You can run up to 3 version in parallel, 1.x, 2.0 and the nightly builds and neither of these conflict with their Installation defaults either.
I have 1.3, 2.0.3 and my sellf build versions installed and have a thumb drive with all portable versions that ever existed, should I need to check something in an older version.
In reply to You can have as many versions by Jojo-Schmitz
So if I wanted to run 2.0.3 alongside 2.0.1, I'd just have to ensure 2.0.3 did not install in the same directory branch as 2.0.1? Right now I've got the executables for 1.3, a nightly from Jan 2015, and 2.0.1 all installed in the x86 Program Files directory.
In reply to So if I wanted to run 2.0.3 by Recorder485
Yes, install 2.0.3 to a non-default direcory
In reply to Okay, thanks for the by Recorder485
I'd like to point out that, while it's very true that MuseScore 2 will make scores from MuseScore 1 look different, that's not really true for different patch updates to MuseScore 2.0. There should be no change at all from 2.0.1 to 2.0.2, and only two rarely encountered things might be different in 2.0.3—the fix for #81321: Slur anchor wrong, and the potential (extremely unlikely to be encountered) for one or two automatic line breaks to change. If you're concerned by that, then indeed you might want to be cautious about keeping 2.0.2 and 2.0.3, but I don't think there is any reason to keep 2.0.1 instead of 2.0.2.
In reply to I'd like to point out that, by Isaac Weiss
Hmm, if I'm not mistaken, I think actually there have been changes involving FreeType and the internal representation of the system DPI value that could result in differents between 2.0.1 as well as between 2.0.2 and 2.0.3 in some cases. Nothing that wouldn't be solved by locking in line breaks then reducing stretch a notch (before updating) to give some wiggle room.
It certainly never hurts to backup your scores, but it shouldn't be necessary. Nothing about uninstalling or installng any version of MuseScore would ever touch any of your scores. And regardless of what drive you install MuseScore onto, it should by default use your "home" (My Documents) folder for your scores. If you wish to move that to another location, you are welcome to do so whether or not you also change anything about your MuseScore installation, but either way, you will need to tell MuseScore where you have moved your Scores flder to, via Edit / Preferences. Similarly if you elect for whatever reason to change the location of your Templates, Style, Plugins, or Soundfont folder.
In reply to It certainly never hurts to by Marc Sabatella
Hmmmm - I assume the word "uninstall" means/implies removing any traces whatsoever (including scores, registry, etc.). That is what I expect of any uninstall process.
In reply to Hmmmm - I assume the word by dpenny
No uninstall process ever removes the documents you create yourself. At least, not for Windows, Mac, or Linux. "MY Documents" on Windows is, as the name implies, yours. On iOS, uninstalling an app does generally remove documents creates, because iOS doesn't provide any general user storage space.
In reply to It certainly never hurts to by Marc Sabatella
Not directly related with this issue, but...
I tried to get the new 2.0.3 version to my Ubuntu Studio and... It doesn't exist!!!
I mean, there is no any new package to upgrade the today 2.0.2, at any available repository in the web.
When can we downloaded it? ???
In reply to Not directly related with by jotape1960
That's up to the distributin maintainers, but see the Download page here on this stie - it is explicit about how to download the "AppImage" version works on any flavor of Linux, no installation required.
In reply to That's up to the distributin by Marc Sabatella
Thanks a lot!!!
Now I downloaded that "AppImage" and... It works so fine!!!
Thanks a lot for your data!!!
Uninstall removing scores ??
Uninstall paint doesn't remove GIF, uninstall word doesn't remove Doc,...
You can follow the standard way to installation musescore without any complex procedure, it works well
In reply to Uninstall removing scores by frfancha
I guess it is related with the directories MuseScore creates when you installed, one of them is intended to save your music scores.
I almost use two directories to this: the MuseScore directory and another "MIDI" directory which I always save as a backup of all my works.
But, I assume that not all the people saves it works into a backup directory, so... They could lost all their music... Maybe.
In reply to I guess it is related with by jotape1960
Do you mean that installing 2.0.3 will empty the default scores directory?
I would be extremely surprised by this.
In reply to I guess it is related with by jotape1960
Absolutely definitely not. Uninstalling does not ever delete *your* scores. That's true for MuseScore and pretty much every other program ever produced for Windows, Mac, or Linux. Uninstalling uninstall;s the *program*, not *your documents*.