Musescore 3 (alpha2) starts slower than Musescore 2 with polyrhytmic tuplets

• Nov 10, 2018 - 20:26

Musescore 3 (alpha2) chokes on simultaneous multiple tuplets when starting. In Muscscore 2, the attached polyrhythmic two bar score starts within 1 second after hitting play, whereas in Musescore 3, it takes up to 5.


In reply to by Sambaji

Please test out the attached file to confirm if this slow-start multi-tuplet bug is inherent in how Musescore 3 now parses scores, regardless of OS. I am interested in the outcome of comparing Musescore 2 and 3 start times, after hitting play, in Linx, Mac and Windows with this score and other arrangements with complex polyphonic polyrhythms.

Here are my specs:
Latitude E5410
OS: Windows 10 64bit
Processor: Intel(R) Core(TM) i5 CPU (M 560 @ 2.67GHz, 2667)
RAM:8.00 GB
Hard drive: Crucial SSD

Many Thanks,

Edit: Added "after hitting play" for clarification.

In reply to by Sambaji

Loads too fast in 3.0 for me to get an accurate timing - a matter of milliseconds, same as 2.3.2

EDIT: ah, but indeed, it is noticeably slower to begin playback. I wouldn't be so sure the tuplets are the relevant thing here, though? It's possible since I know we now use "ticks" internally much less than before, so some of the timing precalculation that might have been present in 2.x won't be any more. Whether that could really explain this difference I can't say. Score seems too short for that to be such a factor, I wonder if it's something about the soundfonts.

Did I post this Musescore 3 playback issue in the right forum, or should potential Musescore 3 bugs be reported in the "Development and Technology Preview" forum?


Do you still have an unanswered question? Please log in first to post your question.