Resubmitting bug report: Musescore 3 impractical to use due to start play delay.

• Nov 15, 2018 - 15:03

I reported the following bug, confirmed by Marc Sabatella, in the wrong forum, so I am resubmitting it here (with a more catchy title) for further consideration.

"Musescore 3 (alpha2) starts playing slower than Musescore 2 with polyrhythmic tuplets"

I had no problem creating and playing the sample score (see above original post) in Musescore 2. However, Musescore 3 is impractical to use when working with the same score because of its prolonged start play time (e.g., 5 seconds in Musescore 3 compared to 1 second or less in Musescore 2).

Please consider submitting this report to the issue tracker as it indicates a flaw in Musescore's new parsing algorithm (or can us regular folk submit bugs to the almighty issue tracker?). I assume the play delay has to do with the polyrhythmic tuplets as the score is only two bars long. Hopefully, this issue will be resolved as I, and I am sure others as well, would like to be able to use Musescore 3 for creating polyrhythmic compositions with ease.

Again, I tested the score using the latest build on the following system.
OS: Windows 10 (10.0), Arch.: x86_64,
MuseScore version (64-bit): 3.0.0, revision: d3d0f87

Many thanks to the development team,

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