> If it has to be a music expression transformation, [...] Yes, more or less – it is for supporting a MusicXML feature that probably gets introduced in the next version, see
https://github.com/w3c/musicxml/issues/557 This means I don't need this right now but was rather interested whether somebody has worked on this issue already. Note that a solution without a transformation, i.e., simply providing a multi-measure rest, is rather straightforward to implement in `musicxml2ly`. However, this would drop a lot of information that might be relevant for manual adjustment after converting MusicXML to Lilypond code. > [...] an engraver might be better that would print the appropriate > tacet rest as long as the music for that context ends before the end > of the score. Sounds sensible, and thanks for the suggested outline! Werner
