Re: Time signature guide

2022-03-22 Thread Leo Correia de Verdier
I hadn’t seen David’s reply until after I posted, otherwise I wouldn't have basically repeated his answer. A disadvantage of the << … \\ … >> syntax in this case is that it applies \voiceTwo to \melody (it has all its stems turned down, for instance). While you can reset that with \oneVoice I pr

Re: Time signature guide

2022-03-22 Thread Rip _Mus
Thank you so much, you offered two similar and valid solutions! Regards Il giorno lun 21 mar 2022 alle ore 10:19 Leo Correia de Verdier < leo.correia.de.verd...@gmail.com> ha scritto: > I’m not sure I understood your question right, but I think the usual way > to do it would be to write the ”g

Re: Time signature guide

2022-03-21 Thread Leo Correia de Verdier
I’m not sure I understood your question right, but I think the usual way to do it would be to write the ”global” variable as a sequence of tempos, time signatures and other events separated by spacers or skips. Something like: %% \version "2.23.6" global = { \time 4/4 \tempo "All

Re: Time signature guide

2022-03-21 Thread bobr...@centrum.is
- Original Message - > From: "Rip _Mus" > To: "Lillypond Users Mailing List" > Sent: Monday, March 21, 2022 8:51:16 AM > Subject: Time signature guide > Good morning, > I would need advice. > In a score with many time signature changes (where

Time signature guide

2022-03-21 Thread Rip _Mus
Good morning, I would need advice. In a score with many time signature changes (where I therefore cannot use a stable global variable of tempo and time signature), there is a way to set a "guide" in which to set the various time signature changes, without " dirty "the instrumental variables? Perhap