Swing turned on by MuseScore3 whenever .mscz file opened
After initially creating a file x1.mscz with Swing=On, I turned Swing Off in the file's Style Score and after the change, the file played properly with no swung notes. I then saved the file as x2.mscz. However, when I subsequently reopened the file, Swing had been turned back on. I verified that file x2.mscz was different from file x1.mscz, by doing a binary file compare with the Windows FC utility, which identified 12 bytes different (details from command prompt log below).
Is there some global parameter switch somewhere that causes MuseScore to override the Swing setting in the file? If so, how do I turn it off? (I've been using MuseScore quite a lot for about a year now, but hadn't noticed this before because most of the scores I work with are for vocal jazz, so more often than not, I want the Swing parameter on.)
Thanks for any help anyone can offer.
......mandy
Comparing files MUSIC\MUSE\x1.mscz and MUSIC\MUSE\x2.mscz:
0000000A: D0 38
0000000B: 40 41
000000B9: D0 38
000000BA: 40 41
00000D6F: D0 39
00000D70: 40 41
00005C71: D0 38
00005C72: 40 41
00005CB5: D0 38
00005CB6: 40 41
00005CFC: D0 39
00005CFD: 40 41
OS: Windows 7 SP 1 (6.1), Arch.: x86_64, MuseScore version (64-bit): 3.0.5.5992, revision: 58dd23d
Comments
a) update, 3.0.5 is pretty old meanwhile, 3.4.2 is the latest release, 3.5 Beta is available on top
b) attach the 2 scores. Binary comparing mscz files is pretty meaningless, they are ZIP archives under the cover
In reply to a) update, 3.0.5 is pretty… by Jojo-Schmitz
Thanks for the info on versions; it was about a year since I last upgraded to the latest MuseScore. Based on your message, I just installed 3.4.2 and it seems to have fixed the problem. (FYI: I realize that a binary compare couldn't do an accurate diagnosis, but it might help narrow down exactly where the problem was occurring (e.g. If there had been no difference in files after I turned the swing parameter off , the problem might be related to not saving changes properly; since the files were different, it made me suspect that the problem was somewhere in the open-file process, when the parameter setting saved in the file was being overridden. That hypothesis seemed to be confirmed when version 3.4.2 loaded the same file correctly.)
Btw, I had assumed incorrectly that MuseScore would issue an alert when a new version was available for download. From now on, I'll make a point to check every month or so, and download the latest stable version.
Thanks again for your prompt and helpful advice.
In reply to Thanks for the info on… by MandyWh
MuseScore does check for and alert about updates.
In reply to MuseScore does check for and… by Jojo-Schmitz
Normally it does, yes, on Windows anyhow. Not on other systems I think? And also not if you turned that option off in Preferences.
In reply to Normally it does, yes, on… by Marc Sabatella
Mac too, not on Linux though
As mentioned, the actual score would be needed to do more than guess. But assuming you checked and the global swing style setting really is off for the score, then perhaps there is a Swing text element in the score. That's actually the more correct / supported way of enabling swing; it lets you turn it on and off over the course of the score, also apply differently to different staves, etc.
In reply to As mentioned, the actual… by Marc Sabatella
I'm pretty sure that's not it. Currently I mainly use MuseScore to create lead sheets to give to the band for vocal jazz singing (i.e. Fake-Book format with just a treble clef that has melody, lyrics and chord symbols). I've been learning various Muse-Score components as the need arises, and so far I've only wanted swing on or off for an entire song. Therefore, I always change it via the Swing parameter accessible via Format | Style | Score.