music-encoding
music-encoding copied to clipboard
music-encoding
unbeamed cross-staff tuplets
In some cases there are tuplets crossing staves without a beam. To deal with this, @bracket.place and @num.place should allow the same values as @beam.place, i.e. "mixed" is missing.
see Gould p. 320:
What for does tupletSpan need @beam.with?
(Edit by @bwbohl: for discussion about the necessity of @beam.with please refer to https://github.com/music-encoding/music-encoding/discussions/1030 )
@beam.with is also needed for beam, e.g. in piano notation (see rism-ch/verovio #1732). Working on Mozart's piano sonatas in Salzburg right now, we are wondering (together with @craigsapp) if this attribute is necessary. Shouldn't rendering software like verovio automatically place the beams correctly? (Sorry for being slightly off-topic. Should a new issue be opened for this?)
The fundamental problem here is that the placement of beams is relative to the placement of the notes, rests, chords under the beam while the placement of tuplet brackets is specified relative to the staves the events are on. However, "fixing" the placement of tuplets and their accompanying brackets and numbers by making their placement the same as those of beams may introduce a backwards compatibility problem. More input from @lpugin regarding Verovio's handling of these things is required.
For discussion on the necessity of beam.with I moved #714 to discussions (https://github.com/music-encoding/music-encoding/discussions/1030), and there added the last comment @pe-ro posted here.
