Le 30/04/2021 à 20:45, Timothy Lanfear a écrit :
I would like a StaffGroup without any systemStartDelimiter -- staves
grouped inside simultaneous music will not do because I would like a
\with clause to modify the context plugins. Unsetting the
systemStartDelimiter does the trick
\new
I would like a StaffGroup without any systemStartDelimiter -- staves
grouped inside simultaneous music will not do because I would like a
\with clause to modify the context plugins. Unsetting the
systemStartDelimiter does the trick
\new StaffGroup \with { \unset systemStartDelimiter } <<
On Fri, 30 Apr 2021 at 19:55, Rachel Green wrote:
>
> Hi,
> For trios, I would like all the tempo markings to occur both above all
parts (as seen above the flute in the example below) but also right above
the harp part. When I add a tempo marking to the harp part, it places it
above the flute
Hi Rachel,
You can make this work by adding the engraver to the staff you want it
to print above (in this case the harp's upper staff). Based on your
example the code might look something like this:
\new Staff \with {
\consists Mark_engraver
\consists
Le 30/04/2021 à 19:17, Rachel Green a écrit :
Hi,
For trios, I would like all the tempo markings to occur both above all parts
(as seen above the flute in the example below) but also right above the harp
part. When I add a tempo marking to the harp part, it places it above the flute
part,
Hi,
For trios, I would like all the tempo markings to occur both above all parts
(as seen above the flute in the example below) but also right above the harp
part. When I add a tempo marking to the harp part, it places it above the flute
part, but when I add a regular markup to the harp part,
On Fri, 2021-04-30 at 16:41 +0200, David Kastrup wrote:
> David Sumbler writes:
> > On Fri, 2021-04-30 at 04:17 -0700, Aaron Hill wrote:
> > > A duration without pitch is encoded as a NoteEvent with the
> > > pitchproperty. expand-repeat-notes! is the internal procedure
> > > thatcarries over
On Fri 30 Apr 2021 at 05:31:50 (+), Werner LEMBERG wrote:
>
> > Okay, so here's a thing: I don't know this term (let vibrate), and
> > if I did, I'm not sure how it would apply in this context (it's a
> > tie, right?).
>
> Have you actually looked into the Notation Reference, section 'Ties'?
David Sumbler writes:
> On Fri, 2021-04-30 at 04:17 -0700, Aaron Hill wrote:
>
>> A duration without pitch is encoded as a NoteEvent with the pitch
>> property. expand-repeat-notes! is the internal procedure that
>> carries over the most recent pitch. So long as you insert these
>> events
On Fri, 2021-04-30 at 04:17 -0700, Aaron Hill wrote:
> On 2021-04-30 3:39 am, David Sumbler wrote:
> > I want to be able to insert a note of the same pitch as the preceding
> > one. I don't mind what form the pitch information is in, so long as I
> > can use it to create a new note. It could,
Mark Knoop writes:
> At 12:15 on 30 Apr 2021, David Kastrup wrote:
>> David Sumbler writes:
>>> How can I access the pitch value of this most recent note for use in a
>>> Scheme function after some rests?
>>
>> Other value-propating mechanisms exist for default durations (attached
>> by the
At 12:15 on 30 Apr 2021, David Kastrup wrote:
David Sumbler writes:
How can I access the pitch value of this most recent note for use in a
Scheme function after some rests?
Other value-propating mechanisms exist for default durations (attached
by the parser upon reading expressions),
On 2021-04-30 4:17 am, Aaron Hill wrote:
On 2021-04-30 3:39 am, David Sumbler wrote:
I want to be able to insert a note of the same pitch as the preceding
one. I don't mind what form the pitch information is in, so long as I
can use it to create a new note. It could, for example, be in the
On 2021-04-30 3:39 am, David Sumbler wrote:
I want to be able to insert a note of the same pitch as the preceding
one. I don't mind what form the pitch information is in, so long as I
can use it to create a new note. It could, for example, be in the form
"b,,", or something similar to "(-2,
David Sumbler writes:
> On Fri, 2021-04-30 at 12:15 +0200, David Kastrup wrote:
>> David Sumbler writes:
>> > In a \relative{ } passage, in order for Lilypond to work out
>> > theabsolute pitch of a note, it must have a record of the absolute
>> > pitchof the previous note, even if there have
On Fri, 2021-04-30 at 12:15 +0200, David Kastrup wrote:
> David Sumbler writes:
> > In a \relative{ } passage, in order for Lilypond to work out
> > theabsolute pitch of a note, it must have a record of the absolute
> > pitchof the previous note, even if there have been some intervening
> >
David Sumbler writes:
> In a \relative{ } passage, in order for Lilypond to work out the
> absolute pitch of a note, it must have a record of the absolute pitch
> of the previous note, even if there have been some intervening rests.
> It seems probable that it has this information in all cases,
In a \relative{ } passage, in order for Lilypond to work out the
absolute pitch of a note, it must have a record of the absolute pitch
of the previous note, even if there have been some intervening rests.
It seems probable that it has this information in all cases, whether
relative pitch notation
Gianmaria Lari writes:
>>
>> > Nota bene: I didn't yet add any examples that take advantage of David new
>> > possibilities:
>>
>> Ah, but that was sort of the point.
>>
>
> Sure, I'm sorry :(
> I'll help with that too when I will be able to access this new feature.
>
>> P.S. I would have liked
Le 05/04/2021 à 12:00, Thomas Morley a écrit :
Hi Jean,
thanks for your reply, though the situation is more complex than the
initial minimal. Consider the following:
{ b'4\glissando 4 4 4 2 b'' }
The plan is to print a glissando from b' to b'' and at intermediate
NoteColumns print a Stem
>
> > Nota bene: I didn't yet add any examples that take advantage of David new
> > possibilities:
>
> Ah, but that was sort of the point.
>
Sure, I'm sorry :(
I'll help with that too when I will be able to access this new feature.
> P.S. I would have liked to add a screenshot of the generated
Werner wrote:
>>
> Have you actually looked into the Notation Reference, section 'Ties'?
> A few paragraphs after the start of the section you can find
> documentation for `\laissezVibrer`!
>
May bad. I missed that, and this is exactly the symbol I wanted to use.
What I skipped over was the
22 matches
Mail list logo
