You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text of the <harm> matches the contents of @n. Notice that the vertical order of the harm labels is "2, 3, 1" rather than "1, 2, 3" which would be expected. The problem is caused by there being no harm@n="1" on the first note of the score. If it is added, then the behavior is as expected:
Notice that the @n="1" line is both in the correct order, and that it is moved into an empty vertical position that should have been used for the @n="1" harm data in the first example.
So there is some variable mixup or omission: The @n="1" information created a space for the @n="1" data, but it was then placed below the @n="3" because the first @n="1" item was found after an @n="3" item.
The system break in the examples demonstrates that the castoff process is not involved, because the order remains mixed on the second system in the first example.
The text was updated successfully, but these errors were encountered:
The
@n
order of<harm>
data gets mixed up if the initial appearances of the data is not at the same timestamp.Example:
Click to view MEI data for above example
The text of the
<harm>
matches the contents of@n
. Notice that the vertical order of the harm labels is "2, 3, 1" rather than "1, 2, 3" which would be expected. The problem is caused by there being noharm@n="1"
on the first note of the score. If it is added, then the behavior is as expected:Click to view MEI data for above example
Notice that the
@n="1"
line is both in the correct order, and that it is moved into an empty vertical position that should have been used for the@n="1"
harm data in the first example.So there is some variable mixup or omission: The
@n="1"
information created a space for the@n="1"
data, but it was then placed below the@n="3"
because the first@n="1"
item was found after an@n="3"
item.The system break in the examples demonstrates that the castoff process is not involved, because the order remains mixed on the second system in the first example.
The text was updated successfully, but these errors were encountered: