Musescore 3.6.2 (and other recent versions) download and appear as 3.2,3.3 or 3.5 - MacOS Catalina
I have noticed that when I download the latest MacOS versions of Musescore - now 3.6 or 3.6.2, the logo which appears in MacOS is still 3.3. I don't mind having a few older versions around for compatibility reasons, but it would be helpful if each version had an updated and correct logo.
I am running on Catalina still.
Comments
I am not sure I understand the issue. What logo? The default name for all versions of MuseScore 3.x is "MuseScore 3". You can rename it to include the whole version number after you copy it to your Applications folder. This is what I do, and it allows me to have several different versions of MuseScore 3 installed at the same time, and I can easily tell all of them apart.
In reply to I am not sure I understand… by mattmcclinch
Indeed - I can "fix" this by going to Applications and explicity changing the file name, and I could probably change the logo too. However, I do feel that I shouldn't have to do this. The current version is 3.6 anyway - so shouldn't that at least be correct - even if the variants after that differ?
In reply to Indeed - I can "fix" this by… by dave2020X
Hopefully by now we have adequately explained what happened, and why it should absolutely be up to you to fix it, since you admittedly know how. There is nothing wrong with renaming the MuseScore app to include the version number, but expecting it to automatically update the modified name when the app autoupdates is expecting a bit too much.
Nevermind.
In reply to I believe I downloaded 3.5… by RobFog
If you rename the MuseScore app to something other than the default name ("MuseScore 3.app"), why should the app be automatically renamed when you update?
In reply to If you rename the MuseScore… by mattmcclinch
Spot on. Ouch!
In reply to Spot on. Ouch! by RobFog
I'm going to have to come back on this one. I have several different machines, some running slight variants of MacOS. I'm sure I see different version numbers from some of the instance on some machines - and I have to actually go to "About Musescore" to find which version each one is. Then it sometimes helps to actually change the name in the Applications folder so that I know which one I'm choosing.
I will check this over the next day or so and get back - but it is an issue for me.
In reply to I'm going to have to come… by dave2020X
See the above. I think at this point it's pretty obvious. You changed it at some point in the past, perhaps to help you remember which version is on which machine. Since you changed the version number manually, that is now "sticking" and it is up to you to continue to update it. Probably best to just return it back to the default, MuseScore 3.
In reply to See the above. I think at… by Marc Sabatella
I'm not quite sure whether I have multiple versions because of the machines I have, or because I felt I needed several versions. I have had files which I think from memory would only open in Musescore 2, and then I was able to convert them to Musescore 3.
i am curious to know how the developers manage to control having multiple versions - which I feel they must have for their work. On MacOS I can move applications into different folders, so that only the most recent and tested versions are activated. I don't particularly want to delete old versions until I'm sure that I don't need the functionality they provide, and that the newer versions are working properly.
From what you are saying, the fact that I tried to solve the problem of having multiple versions (which I wanted to keep) by renaming them has itself caused a problem. Presumably I can still keep the versions I've renamed - but make sure that the latest working version is always called Musescore 3 - or will the damage already have been done irreversibly (which I doubt) by renaming the application file?
In reply to I'm not quite sure whether I… by dave2020X
I am guessing that you ran into this problem because MuseScore prompted you to update to the latest version, and you agreed. So it installed the latest version into the same location, which you had renamed to include the old version number. But if you want to keep older versions of MuseScore, then you probably do not want to take advantage of MuseScore's autoupdate facility, but rather download each new version directly from musescore.org.
In reply to I'm not quite sure whether I… by dave2020X
MuseScore 2 and MuseScore 3 happily coexist, no special steps are needed to manage this.
It's only if you for some reason also make the choice to keep multiple 3.x versions around that you would need to take extra steps to keep the latest 3.x version from overwriting the previous 3.x version. I don't recommend it unless you are an expert sysadmin and know exactly how to manage this for your particular OS. On Linux it's easy to keep multiple AppImage files for older releases so I can test that way, but I always have only the latest actually installed. No idea if anything similar exists for macOS. But I'd certainly be looking for ways to keep the current version as "pure" as possible, to avoid problems that might be caused by not managing this properly. So if you can find a way to have an older version installed that in no way interferes with the current version, great - accomplish that by messing with that older version. But keep the current one as is - don't mess with it. That's my advice anyhow.