From MusicXML

key signatures - While not common, there are known cases for this. e.g. Beethoven, Piano Sonata 31. Needs handling especially in the accidentalhelper
time signatures - Possible in MusicXML, and there are some very rare cases where this has been reported. But most applications tested do not support this (Guitar Pro, MuseScore, Soundslice, Dorico. Hence we will not add support for it.
Clef - Should be supported. Similar like key signatures it needs handling in the accidental helper to calculate the right lines.
Staff Lines - Should be supported.
Staff Tuning - While technically possible, unlikely to happen. I'd say it is super unlikely that tuning changes in the middle of a song (retuning your song while playing?)
Capo - Could be quite likely that a capo is placed during the song.
Transpose - Unclear if this can change.

Implementation idea(s):

Various properties are currently on staff level. We should likely add a new data structure holding the values applied on bars and assign it to the bars (e.g. via ID lookup to staff/score level?). Every bar holds then the ID of the values applied on it.

To fit into the current principles: We handle changes on these values through automations on beats (change of the ID). Or we simply specify the IDs on the beats to detect changes (should bars still have an "initial" ID or do we ensure a empty beat at start if missing?).

Respective components (like accidental helper) can then lookup the values needed and act accordingly.

Rendering wise: we could attach the glyphs to the respective beat (pre-notes container). This would handle timely alignments accordingly without major rework.

Mid-Bar Attribute Changes. #1991

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions