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 prefer just placing them in parallell in the same explicitly initiated Staff, as I did.
> 22 mars 2022 kl. 10:27 skrev Rip _Mus <ripetizioni.mus...@gmail.com>: > > 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 ”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 "Allegro" 4 = 144 > s1 > \time 3/8 \tempo "Adagio" 8 = 76 > s4. > \time 5/8 \tempo "" 8 = 92 > s8*5 > \time 3/2 \tempo "Vivo" 2 = 152 > s1. > \bar "|." > } > > part = { c'1 | d'4. | e'4~ 4. | a'1. } > > \new Staff << \global \part >> > > \layout { ragged-right = ##f } > > %%%%%%%%%%%%%% > > > 21 mars 2022 kl. 09:51 skrev Rip _Mus <ripetizioni.mus...@gmail.com>: > > > > 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? > > Perhaps there is some suitable context for this? Or other strategies? > > > > Thank you very much > > > > Rip_mus >