Hello,
Thank you very much!
Il sab 19 ago 2023, 14:10 Thomas Morley ha
scritto:
> Am Fr., 18. Aug. 2023 um 21:51 Uhr schrieb David Kastrup :
> >
> > Rip _Mus writes:
> >
> > > Hello,
> > > does anyone happen to have an answer?
> > > I just can't understand this behavior...
> > >
> > > Thank yo
Am Fr., 18. Aug. 2023 um 21:51 Uhr schrieb David Kastrup :
>
> Rip _Mus writes:
>
> > Hello,
> > does anyone happen to have an answer?
> > I just can't understand this behavior...
> >
> > Thank you
> >
> > Il mer 16 ago 2023, 08:18 Rip _Mus ha
> > scritto:
> >
> >> Good morning everyone,
> >> goi
Rip _Mus writes:
> Hello,
> does anyone happen to have an answer?
> I just can't understand this behavior...
>
> Thank you
>
> Il mer 16 ago 2023, 08:18 Rip _Mus ha
> scritto:
>
>> Good morning everyone,
>> going back to the solution written by David, I found that simply adding
>> the Duration_l
Hello,
does anyone happen to have an answer?
I just can't understand this behavior...
Thank you
Il mer 16 ago 2023, 08:18 Rip _Mus ha
scritto:
> Good morning everyone,
> going back to the solution written by David, I found that simply adding
> the Duration_line_engraver causes the example to fa
Good morning everyone,
going back to the solution written by David, I found that simply adding the
Duration_line_engraver causes the example to fail to compile.
Can anyone tell me why this happens?
Below is the minimal example:
%%%
global = {
s1\break
s1\break
s1
}
flOne = \relative c' {
On 2023-08-14 19:46, David Kastrup wrote:
Sounds somewhat like
exa.ly
%%%
\version "2.24.1"
global = {
s1\break
s1\break
s1
}
flOne = \relative c' {
e1
r1
e1
}
flTwo = \relative c' {
c1
r1
c1
}
\new StaffGroup \with { \consists "Keep_alive_together_engraver" }
Rip _Mus writes:
> wow!!
> Now I understand Knute's answer too.
> Unfortunately, opening the page in the Italian version, the documentation
> relating to the Keep_alive_together_engraver is not there.
Its internals are documented, but its remove-layer settings are not
really documented as a user
> From: Rip _Mus
> To: Flaming Hakama by Elaine
> Cc: Lilypond-User Mailing List
> Bcc:
> Date: Mon, 14 Aug 2023 17:45:27 +0200
> Subject: Re: Question about condensed score
> Thanks for sharing your workflow, that's what I was afraid I'd have to do.
> While
wow!!
Now I understand Knute's answer too.
Unfortunately, opening the page in the Italian version, the documentation
relating to the Keep_alive_together_engraver is not there.
Thank you very much for the solution, thank you very much!
Il giorno lun 14 ago 2023 alle ore 19:46 David Kastrup ha
scri
Rip _Mus writes:
> Hello,
> please consider the following example:
>
> %%%
> \version "2.24.1"
>
> global = {
> s1\break
> s1\break
> s1
> }
>
> flOne = \relative c' {
> e1
> r1
> e1
> }
>
> flTwo = \relative c' {
> c1
> r1
> c1
> }
>
> \new StaffGroup \with { shortInstrumentNam
Hello,
please consider the following example:
%%%
\version "2.24.1"
global = {
s1\break
s1\break
s1
}
flOne = \relative c' {
e1
r1
e1
}
flTwo = \relative c' {
c1
r1
c1
}
\new StaffGroup \with { shortInstrumentName = "Fl. 1-2" } <<
\new Staff \with {
instrumentName = "Fl
Rip _Mus writes:
> Good morning everyone!
> I would like to ask if you know a strategy to achieve the following result.
>
> I'm working on an orchestral score. I'd like the two flute staves to be
> shown separate when they play, while condensed when both are silent
> (perhaps with a staff name sh
aine <
ela...@flaminghakama.com> ha scritto:
>
>
>
>> From: Rip _Mus
>> To: Lilypond-User Mailing List
>> Cc:
>> Bcc:
>> Date: Mon, 14 Aug 2023 08:43:17 +0200
>> Subject: Question about condensed score
>> Good morning everyone!
>> I wo
> From: Rip _Mus
> To: Lilypond-User Mailing List
> Cc:
> Bcc:
> Date: Mon, 14 Aug 2023 08:43:17 +0200
> Subject: Question about condensed score
> Good morning everyone!
> I would like to ask if you know a strategy to achieve the following result.
>
> I'm worki
In fact, sadly, I haven't found any trace of this in the documentation.
I imagined a solution, a bit like a programmer, but I don't know how to
implement yet.
The idea is to be able to change the instrumentName conditionally:
- if the staffGroup contains less than two staves (because one of them is
Perhaps I'm mistaken, and if so, I'm certain will correct me, but I believe
lilypond isn't able to do this. You would need three staves, one each for the
individual parts and on common one for both, manually assign music to the
appropriate staves, and insert breaks where necessary.
> On Aug 14,
Thank you Knute,
I already know how to hide empty staves.
The point is to condense only during the rests, changing the name of the
staves. When they are separated each staff should have its own name ("fl.
1" - "fl. 2"), while when they are condensed they should show a unique name
("fl. 1-2"), perh
This part of the documentation will probably help you:
https://lilypond.org/doc/v2.25/Documentation/notation/hiding-staves
--
Knute Snortum
On Sun, Aug 13, 2023 at 11:44 PM Rip _Mus
wrote:
> Good morning everyone!
> I would like to ask if you know a strategy to achieve the following result.
Good morning everyone!
I would like to ask if you know a strategy to achieve the following result.
I'm working on an orchestral score. I'd like the two flute staves to be
shown separate when they play, while condensed when both are silent
(perhaps with a staff name showing the indication "fl. 1-2"
19 matches
Mail list logo
