Le 24/04/2022 à 11:09, Martín Rincón Botero a écrit :
Dear list, already in 2019 there was a report of articulate.ly (https://link.getmailspring.com/link/2b7323b8-2288-42b2-8116-0bce0a45c...@getmailspring.com/0?redirect=articulate.ly&recipient=YnVnLWxpbHlwb25kQGdudS5vcmc%3D) misbehaving when there's a trill followed by a full measure rest. I recently had the same problem in Lilypond 2.22 which was solved with the patch described here: https://marc.info/?l=lilypond-user&m=142477756707049&w=2 (https://link.getmailspring.com/link/2b7323b8-2288-42b2-8116-0bce0a45c...@getmailspring.com/1?redirect=https%3A%2F%2Fmarc.info%2F%3Fl%3Dlilypond-user%26m%3D142477756707049%26w%3D2&recipient=YnVnLWxpbHlwb25kQGdudS5vcmc%3D). MWE: \version "2.22.1" \include "articulate.ly" \score { \unfoldRepeats \articulate { b1 \startTrillSpan | R1 \stopTrillSpan | b2 r | b1 } \midi {} } Produces: barcheck failed at: 1/2 b2 r | Furthermore, the resulting MIDI is totally wrong after the first full measure rest. Subsequent notes are trilled and rests are ignored. The two lines patch described above solves both problems (failed barcheck and bad playback) perfectly (add to line number 537 of articulate.ly (https://link.getmailspring.com/link/2b7323b8-2288-42b2-8116-0bce0a45c...@getmailspring.com/2?redirect=articulate.ly&recipient=YnVnLWxpbHlwb25kQGdudS5vcmc%3D) in master/539 of 2.22.). Regards, Martín.
Looks good to me. How about submitting this patch as an actual merge request? Then you'll not only have contributed it to LilyPond, but you'll also have learnt how to do this for future contributions. The Contributor's Guide has details: https://lilypond.org/doc/v2.23/Documentation/contributor/working-with-source-code Best, Jean _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
