Musescore playing mixed meters wrong.
OS: Windows 10 Version 2009 or later, Arch.: x86_64,
MuseScore Studio version (64-bit): 4.3.2-241630831, revision: 22b46f2
Please take a look at the attached score.
When simple and compound meters are mixed, either the beat or the division of the beat remains constant.
IF Division constant:
The speed of the eighth note remains constant throughout, but consequently, the beats are of unequal length. You will fell the the tempo speed up when moving from compound to simple meter, and slow down when moving from simple to compound meter.
IF Beat Constant
The quarter note in simple meter equals the dotted quarter note in compound meter.
Consequently, the speed of the eighth note changes.
At the attached file you'll see:
a) First system: I assigned quarter note equals to quarter note (from the "tempo" menu).
It plays exactly as it supposes to be, the speed of the eighth note remains constant throughout, but consequently, the beats are of unequal length.
b) Second System:
The same music written, same tempo, but this time, I assigned doted quarter not equals to quarter note (from the same "tempo" menu).
Here is the problem.
It should keep and steady beat and change the duration of the quarter notes between the simple and the compound meters.
It doesn't.
c) Third system: Prove of fail: So I "hacked" it by assigning quarter note equals to 100bpm over the simple meters, and assigned doted quarter note equals to 100bpm over the compound meters.
NOW it plays what it supposed to be playing in the second system.
Now bear with me for a second:
In the second system:
2/4, quarter note equals to 100 bpm. 6/8, dotted quarter note equals to quarter note.
Mathematically, doted quarter note equals to 100 BPM.
It should sound exactly the same as the third system
Am I missing something ?
To isolate the problem ( and get rid of possible problems with tempo change and symbols interaction), I wrote the same music in three separate files, and had the same results. These files are also attached.
Thank you in advance from your help.
| Attachment | Size |
|---|---|
| disgnostic.zip | 47.55 KB |
| MIXED METER ERROR.mscz | 23.86 KB |
Comments
I'm not 100% sure, but
it is convention to place tempo equivalencies exactly backwards from how you have them.
Old=New
You might want to try that first.
In reply to I'm not 100% sure, but it is… by mkjnovak
Hello mkjnovak,
Is actually a good advice, but unfortunately, I got the same result (and this is even more odd) .
It was worth the try, though.
I attached it here, in case anyone else might be curious or have a solution.
Thank you
In reply to Hello mkjnovak, Is actually… by Vinicius Moulin
OK, I'm still not sure why this works, but it does.
In this Inverse time change file, untick 'follow written tempo', then tick them back on again for each instance.
I'd bet you probably should also do this in order of their appearance.
In reply to OK, I'm still not sure why… by mkjnovak
Oh! Thank you! It works!
I attached the file with the changes and correct tempo changes.
When unticking "follow written tempo" (proprieties menu), the tempo showing below was the same as before (100 BPM). But when ticking it back it recalculates the correlation for the time to be the same and the eight notes to be different ( exactly as it should be!) and changes it.
I'm reporting this in GitHub, I believe it's worth fixing.
Thank you very much fro your help!