MusicXML: request for more optimal calculation of "divisions"
Calculation of "divisions" value is incorrect and poorly reflects what is notated on the score
version used : 2.3.2 build 4592407
a) Expected behavior
When a measure contains complex or irregular tuplets , the "divisions" value in the xml file (path :...part / measure/attributes/divisions) is expected to be the "lowest common multiple" and the backward/forward nodes be used only when this is (absolutely) necessary.
b) Actual Behavior/ observed situation
In the xml file (see attachments) the "divisions" value is inappropriate what leads the engine to Insert superfluous and undesirable backward & forward values ( micro movements) in order to keep the tempo...
Those inelegant values (mathematically speaking) lead the program who would read/parse the xml file to twist itself in knots….after a burden of work….
Alternate calculations (on the example) show that the “divisions” value should be 57 instead of 480 (see attachments)
Demonstration (see also excel sheet in attachment)
With "57 " instead of 480, results will be :
a) the tuplet of 19 notes (32nd) will require 19 * 6 = 114 divisions in 2 beats (i.e an half)
b) the (normal) quarter requires 57 divisions
c) and the two notes in the triplet require respectively 38 & 19 divisions , by considering that 57= 38 + 19 and 38 = 2*19.
d) backward and forward values are not necessary
1°) first measure of "happy birthay to you " created with musescore V2.3
2°) The xml file obtained by the "export" menu in musescore
3°) pdf with summary of current and expected data