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
Description:
When a section of music with a complex local time signature is exported to MusicXML and the MusicXML is then re-imported, the resulting layout is incorrect. This is not a MS 4.0 regression, because the same problem exists for MS 3.6.2.
Steps to reproduce the behavior:
Create a grand staff with two measures, as per illustration below. The example is the first two measures of Goldberg Variation 26 (J S Bach). See example score on musescore.org forum: https://musescore.org/en/node/286883#comment-1172268
The upper staff has a local time signature of 18/16, and the lower staff has the general time signature of 3/4.
The upper staff's measures each contain three groups of 6 sixteenth notes, and the lower staff is a varied rhythm in 3/4 time.
Export this short score to MusicXML.
Then re-import the MusicXML into MS 4.0.1
Expected behavior:
a) the 18/16 time signature should apply to the upper staff
b) the general 3/4 time signature should apply to the lower staff
Actual behavior:
a) the 18/16 time signature does apply to the upper staff;
b) the time signature in the lower staff wrongly changes from 3/4 to 18/16, and the measure duration is corrupted by introducing a leading rest in each measure.
Screenshots:
Desired layout:
Faulty layout after import of MusicXML:
Platform information:
OS: Windows 10 Version 2009, Arch.: x86_64,
MuseScore version (64-bit): 4.0.1-230121751, revision: github-musescore-musescore-9b70a8c
…ime signature
- export all time signatures for multi-staff parts
- when streched correct duration of:
- normal rest
- measure rest
- backup
Note that import also requires fixes
…ime signature
- export all time signatures for multi-staff parts
- when streched correct duration of:
- normal rest
- measure rest
- backup
Note that import also requires fixes
Description:
When a section of music with a complex local time signature is exported to MusicXML and the MusicXML is then re-imported, the resulting layout is incorrect. This is not a MS 4.0 regression, because the same problem exists for MS 3.6.2.
Steps to reproduce the behavior:
Expected behavior:
a) the 18/16 time signature should apply to the upper staff
b) the general 3/4 time signature should apply to the lower staff
Actual behavior:
a) the 18/16 time signature does apply to the upper staff;
b) the time signature in the lower staff wrongly changes from 3/4 to 18/16, and the measure duration is corrupted by introducing a leading rest in each measure.
Screenshots:
![Goldberg_Variation_26_OpenGoldberg](https://user-images.githubusercontent.com/124567953/216936991-a721c822-083a-499a-ad92-fe6f6174ec84.jpg)
Desired layout:
Faulty layout after import of MusicXML:
![Goldberg_Variation_26_after MusicXML_import_MS4](https://user-images.githubusercontent.com/124567953/216937144-dc838b45-a61a-4e19-b491-9b7fd9791377.jpg)
Platform information:
OS: Windows 10 Version 2009, Arch.: x86_64,
MuseScore version (64-bit): 4.0.1-230121751, revision: github-musescore-musescore-9b70a8c
Issue on musescore.org forum:
https://musescore.org/en/node/286883#comment-1172268
The text was updated successfully, but these errors were encountered: