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
I have exported a musicxml file from Dorico to try out Smashcima. However, I am getting an assertion error regarding the use of key signatures:
assert set(self.clefs.keys()) == set(range(1, self.staff_count+1)), \
31 "There is not one clef exactly for each staff"
---> 32 assert set(self.keys.keys()) == set(range(1, self.staff_count+1)), \
33 "There is not one key signature exactly for each staff"
34
AssertionError: There is not one key signature exactly for each staff
This is strange since the solo piano excerpt I am using appears to have the correct number of key signatures:
This seems to be an issue with grand stave instruments since this was not a problem with a solo violin excerpt I tried. However, the key signature of the violin excerpt was not included in the final render.
The text was updated successfully, but these errors were encountered:
Smashcima was tested on MuseScore 3.6.2 musicxml outputs, maybe try loading the Dorico musicxml file in MuseScore and then exporting it again. It should fix it.
Also, could you send me the Dorico's musicxml file here? I'll look into the XML to see what the problem might be and possibly fix it. Thanks!
Thank you, exporting the musicxml file from MuseScore fixes the problem. However, the ties, dynamics and key signatures do not show up in the generated handwritten score. Is there a reason for this?
I have exported a musicxml file from Dorico to try out Smashcima. However, I am getting an assertion error regarding the use of key signatures:
This is strange since the solo piano excerpt I am using appears to have the correct number of key signatures:
This seems to be an issue with grand stave instruments since this was not a problem with a solo violin excerpt I tried. However, the key signature of the violin excerpt was not included in the final render.
The text was updated successfully, but these errors were encountered: