Delay starting play with an specific file only
Hi, gang!!!
I use MuseScore 3.5.2 Portable AppImage inside a computer with Ubuntu Studio 20.04.1 LTS (64 bit Linux).
I have a problem with this specific file I'm attaching, here.
Each time I open it, Musescore takes a long time (more than 10 seconds) to start to play it.
And, it is not only when I ask Musescore plays the tune. It is the same with any Menu command I want to use: There is always a time delay, which is not normal, of course, and all this "bad" behaviour is ONLY with this specific file!
I wrote this file, years ago, with more than 10 Christmas pieces, but... It is the only one file I have this issue, and I don't understand what is the specific problem, here. What is the difference in this file? ???
I didn't use, and I don't know any kind of "DELAY" command into the Musescore playing part or something. So...
Can somebody help me, please?
I'm uploading the piece with 3 different format files (Musescore standard, Midi standard and MusicXML standar), just in case.
Blessings and Greetings from Chile!!!
JUAN
Comments
If you still have 3.4.2 the problem does not arise. With 3.6 instead yes :(
For me in 3.5.2 it completely hangs for more then a minute (70+ seconds), very wierd!
I wonder why none of the sounds are the expressive ones (supporting SIngle Note Dynamics)?
In reply to For me in 3.5.2 it… by Jojo-Schmitz
Similar experience here (opened the mscz).
The initial draw seems to take lots of time (little over a minute); but all actions after that are just normal without delay (so also not a menu delay).
Switching to a part takes a similarly long time.
In reply to Deleted parts to avoid… by Jm6stringer
Thank you so much, guys!!! Specially thanks to @jm6stringer!!!
Now, I have the "fixed" file (without hairpins and multiple dynamic marks) without any kind of "delay".
I didn't need to erase the coda part at all. I think it was only related with very long hairpins and multiple dynamic marks (bar 51). I uploaded the fixed file.
BTW: I'm sure I posted, years ago, something about the multiple dynamic marks. It is useful when we use more than one voice in some staff, but... In this case (and it is not the only one case), I used just one voice, but with more than one note at a time. Musescore put one dynamic mark to each note, even the fact all those notes are in the same voice. I think it is not logic. Just my humble opinion.
And, at last... Why the long hairpins produced this rare behaviour, in this case? ??? I've used very long hairpins in other pieces without this issue. So...