MusicXML - clefs not properly encoded

Report problems, bugs, etc.
Forum rules
Please be specific when reporting bugs and be able to reproduce them.
If you don't, the post will most likely be ignored or deleted.
Post Reply
TenorAlan
Super User
Posts: 537
Joined: Sun Sep 08, 2019 10:28 am

MusicXML - clefs not properly encoded

Post by TenorAlan »

Observed on Overture 5.6.3-3/Windows 7

When Overture creates a MusicXML file from a score in which the clef on a staff has been changed from the clef the staff had when created, it seems that Overture puts in the code for the original clef.

Alan
TenorAlan
Super User
Posts: 537
Joined: Sun Sep 08, 2019 10:28 am

Re: MusicXML - clefs not properly encoded

Post by TenorAlan »

Ah, I see the problem. When we apply a new clef to a staff, it changes the "Starting" clef but not the "Transposed" clef. It is the latter that Overture encodes into MusicXML, part of Overture's approach to the MusicXML encoding of transposing instrument tracks.

It is tricky to correct this problem, as when we apply a new clef the Starting and Transposed clefs may not be the same.

Perhaps a good approach would be, if the two clefs were the same when we apply a different clef to the staff, the clef we apply would become the new Starting and Transposed clefs.

Alan
Post Reply