Application: MuseScore 3.2.3 Portable
Category: Music & Video
Description: Create, play back, and print sheet music for free. MuseScore is cross-platform, multi-lingual, open source music notation software. It features an easy to use WYSIWYG editor with audio score playback for results that look and sound beautiful. It supports unlimited staves with up to four voices each, dynamics, articulations, lyrics, chords, lead sheet notation, import/export of MIDI and MusicXML, export to PDF and WAV, plus online score sharing.
Download MuseScorePortable 3.2.3 Development Test 3 [92.1MB download / 258MB installed]
(MD5: 58E24393722C8FDB66932D1C92037D3A)
(SHA256: 11543F812EBAFEE2166FAC3E3F47C631578A00AD2DA432AA59BFD4561EACB7F6)
Release Notes:
Development Test 3 (2019-08-24):
- Modified path replacement for more general cases
Development Test 2 (2019-08-19):
- Added path replacement in case of changed drive or folder to additional setting files
Development Test 1 (2019-08-18): Initial release
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
I had a quick look at the MuseScorePortable.ini.
It seems you're adjusting the paths in MuseScore*.ini only.
Previous MuseScore Portable releases did some adjustments to plugins.xml and session file as well. Doesn't use MuseScore 3 these files anymore?
Thank you, you are right: I totally overlooked those files.
I added the path replacement for those and also for the strored HKCU\Software\QtProject\OrganizationDefaults\FileDialog registry key, and updated the first post with the new development test release.
Regarding your handling of the Qt bits - see KVIrc Portable 5.0.0 for the method we recommend for handling these, paying close attention to the Custom.nsh file.
Thank you for the tip, but I tried it and I am not sure it is the right approach:
with this Custom.nsh (and QtKeysCleanup in the .ini file) after closing MuseScorePortable the keys I listed in [QtKeysCleanup] section are wiped, even if they already existed before launching MuseScorePortable.
On the other hand, by using the backup/restore approach (as it is now in Development test 2) those keys are reverted back to how they were before launching MuseScorePortable (for example, empty if they were originally empty. Moreover, on relaunching MuseScorePortable they are restored. For example, I can save a custom color in the color selection menu and it is kept from one session of MuseScorePortable to the next, or the file open dialog remembers the recently visited locations from one session to the next; and another application using Qt 5 will not have its Qt file dialog and custom color preferences overwritten (probably unless launched at the same time when MuseScorePortable is running, but such a preference mess in that situation would happen also in the Custom.nsh/QtKeysCleanup case).
So, unless it can give additional problems, that at the moment I can't see, I think I will leave the handling of these specific Qt registry keys as done for Development test 2. Please correct me if I am wrong and/or such application registry behavior could be problematic; I am definitely not an expert in registry handling and I may overlook something important.
Can I find this new MuseScorePortable.ini somewhere on GitHub?
Don't want to waste my bandwidth. Can't test on my machine anyway.
Here it is: https://github.com/AntonioBL/MuseScore/commit/3ec781e0dff55ba7be56fd4b48...
I didn't trigger a new Appveyor build on the official MuseScore account to avoid clogging the disk space available on Appveyor, but simply repacked the old build with the new .ini file. If only modifications to the Launcher files are required, a full new build is not needed.
I am not sure what happens first: the text replace or the registry backup/restore of stored values.
As plugins and user files could be saved everywhere on the disk, the adjustment should be a bit wider.
I suggest something like this for FileWrite 2 and 3:
I don't know how the registry file looks like, but FileWrite 4 could be improved as well. Just be sure to find and replace not only the drive letter. This can have strange effects.
Sorry for the delay in the answer.
I modified the text replace and updated the binary file.
You can find the new .ini here: https://github.com/AntonioBL/MuseScore/commit/a50977f90f94b2789e041442d5...
Now the path replacement is more general; there can be cases in which the behavior is still not the desired one (for example, when moving the portableapp from one drive to another, but keeping the plugins in the old one), but, frankly speaking, it is impossible to cover every single improbable corner case, and as it is now it should cover the most common cases.
Thank you for your help in the review.
Is there something I can/should do to speed up the review process?