Urs Liska writes:
> Am 12.04.2018 um 20:45 schrieb Mark Stephen Mrotek:
>>
>> Marco,
>>
>> Got the 3’s on each group – see attached.
>>
>
> Finally you can tell LilyPond to automatically group consecutive tuplets:
>
> \set tupletSpannerDuration = #(ly:make-moment 1 8)
>
> which removes the need
Gianmaria Lari writes:
> I would like to tie the last note contained in a variable like this
>
> \version "2.19.81"
> var = {a b a}
> {\var ~ a}
>
> but this generates an error. This is just a simple example, the reason why
> I would like to do this is because the variable in the real piece is us
Suppose that I define a variable so that according to a tag I can generate
a a a
or
a b a
Is there any way to make lilypond complaint with a compilation
error/warning in case I don't specify a \keepWithTag or \removeWithTag?
For example:
\version "2.19.81"
var = {
a
\tag#'vera a
\tag#
Gianmaria Lari writes:
> I would expect the two scores generated by the following code were the
> same.
>
> \version "2.19.81"
> {a8 8}
> {a 8}
>
> Why lilypond treats them differently?
Because {a8 8} and {a8} are different? Spaces are not a relevant part
of input. You'd have to write { a8 8 }
Gianmaria Lari writes:
> I didn't understand what I can do and how to use the \pushToTag and
> \appendToTag.
>
> Do you have a very simple example?
\pushToTag #'tag c' \tag #'tag {}
How about stating what you _want_ to do?
--
David Kastrup
___
lily
Oh! I will wait for it :)
Thank you David!
On 13 April 2018 at 09:13, David Kastrup wrote:
> Gianmaria Lari writes:
>
> > I would like to tie the last note contained in a variable like this
> >
> > \version "2.19.81"
> > var = {a b a}
> > {\var ~ a}
> >
> > but this generates an error. This is
On 13 April 2018 at 09:15, David Kastrup wrote:
> Gianmaria Lari writes:
>
> > I would expect the two scores generated by the following code were the
> > same.
> >
> > \version "2.19.81"
> > {a8 8}
> > {a 8}
> >
> > Why lilypond treats them differently?
>
> Because {a8 8} and {a8} are different?
Gianmaria Lari writes:
> On 13 April 2018 at 09:15, David Kastrup wrote:
>
>> Gianmaria Lari writes:
>>
>> > I would expect the two scores generated by the following code were the
>> > same.
>> >
>> > \version "2.19.81"
>> > {a8 8}
>> > {a 8}
>> >
>> > Why lilypond treats them differently?
>>
>
On 13 April 2018 at 09:17, David Kastrup wrote:
> Gianmaria Lari writes:
>
> > I didn't understand what I can do and how to use the \pushToTag and
> > \appendToTag.
> >
> > Do you have a very simple example?
>
> \pushToTag #'tag c' \tag #'tag {}
>
> Thank you for the example. It is simple in the
Gianmaria Lari writes:
> On 13 April 2018 at 09:17, David Kastrup wrote:
>
>> Gianmaria Lari writes:
>>
>> > I didn't understand what I can do and how to use the \pushToTag and
>> > \appendToTag.
>> >
>> > Do you have a very simple example?
>>
>> \pushToTag #'tag c' \tag #'tag {}
>>
> Thank you
On 13 April 2018 at 10:00, David Kastrup wrote:
> Gianmaria Lari writes:
>
> > On 13 April 2018 at 09:17, David Kastrup wrote:
> >
> >> Gianmaria Lari writes:
> >>
> >> > I didn't understand what I can do and how to use the \pushToTag and
> >> > \appendToTag.
> >> >
> >> > Do you have a very s
Gianmaria Lari writes:
> On 13 April 2018 at 10:00, David Kastrup wrote:
>
>> How about pointing out what you find hard to understand in the
>> documentation then?
>
>
> I'm not a musician and I'm a young lilypond user. So I don't like come
> here and say that this part of the documentation is n
At 11:48 on 13 Apr 2018, David Kastrup wrote:
>Gianmaria Lari writes:
>> I simply don't understand it. I don't understand it because: it is
>> too long, there are too many things, I don't understand the example
>> goal, and I don't understand the explication following the code.
>
>It adds materi
One way would be to use bar line checks (|) and \barNumberCheck:
%%% Start
\version "2.19.81"
var = {
\time 3/4
a
\tag#'vera a
\tag#'verb b
a |
}
{\var} %this should generate a warning
{\keepWithTag #'vera \var} %this is ok!
{\keepWithTag #'verb \var} %this is ok!
{\removeWithTag #'vera
[ Is there any way to make lilypond complaint with a compilation
error/warning in case I don't specify a \keepWithTag or \removeWithTag?]
On 13 April 2018 at 15:17, Knute Snortum wrote:
> One way would be to use bar line checks (|) and \barNumberCheck:
>
> %%% Start
> \version "2.19.81"
> var =
Am 12.04.2018 um 19:25 schrieb Mark Stephen Mrotek:
Marco,
In the attached I got the beaming you want. Do not know how to give each
tuplet is own 3.
Have a look at my answer to that question: setting subdivideBeams (and
baseMoment) is way easier than setting stemLeftBeamCount and
stemRigh
Am 12.04.2018 um 22:35 schrieb foxfanfare:
> Is this exactly how this function works?
Yes, you explained exactly what I meant. You get multiple fonts as you
described but you cannot add multiple fonts in one function call.
Joram
___
lilypond-user mai
Mark Knoop writes:
> At 11:48 on 13 Apr 2018, David Kastrup wrote:
>>Gianmaria Lari writes:
>>> I simply don't understand it. I don't understand it because: it is
>>> too long, there are too many things, I don't understand the example
>>> goal, and I don't understand the explication following th
Hi all,
I try to bring two projects together and finally get to the point where
I should properly learn what lilypond-book-preamble.ly actually does.
I have an infrastructure that retrieves and composes the material to be
engraved from several places and finally produces the output with
ly:b
Hello folks,
In the example below, chords are split over two voices by musicxml2ly, as it
found them (as harmonies) in the MusicXML file.
Would it be better to have only one chords part in such a case, to have Ebm9 at
the same horizontal level as the other three chords, as MuseScore does in the
Hi all
Can anybody tell me what's wrong with this minimal example?
I would expect the included file to be relative to the location of the
file which includes it, not to the current working directory. What do
you think?
The only workaround is using the --include option?
[build (master *+)]$ ca
On 4/13/2018 12:20 PM, Menu Jacques wrote:
Hello folks,
In the example below, chords are split over two voices by musicxml2ly,
as it found them (as harmonies) in the MusicXML file.
Would it be better to have only one chords part in such a case, to
have Ebm9 at the same horizontal level as th
Hi,
what is in the musicxml? One or two chord tracks?
What is your goal?
If there are two intentionally in xml, musicxml2ly should keep them.
If you ask what would make sense for the ly file, one would be better.
Cheers,
Joram
___
lilypond-user mailin
Hello Joram,
> Le 13 avr. 2018 à 19:31, Noeck a écrit :
>
> Hi,
>
> what is in the musicxml? One or two chord tracks?
Two tracks.
> What is your goal?
I wondered if moving all chords to a single staff was was the trouble.
>
> If there are two intentionally in xml, musicxml2ly should keep t
On Fri 13 Apr 2018 at 19:01:27 (+0200), Federico Bruni wrote:
> Hi all
>
> Can anybody tell me what's wrong with this minimal example?
> I would expect the included file to be relative to the location of
> the file which includes it, not to the current working directory.
> What do you think?
> The
Il giorno ven 13 apr 2018 alle 20:28, David Wright
ha scritto:
On Fri 13 Apr 2018 at 19:01:27 (+0200), Federico Bruni wrote:
Hi all
Can anybody tell me what's wrong with this minimal example?
I would expect the included file to be relative to the location of
the file which includes it,
David Wright writes:
> I don't think this is the problem you think it is. It's actually
>
> myMusic = \relative c' { c4 d e f | } \myMusic
>
> where the definition of myMusic tries to eat itself.
Not really. The parser wants to know from the lexer whether something
like \addlyrics is after the
On 13 April 2018 at 11:48, David Kastrup wrote:
> Gianmaria Lari writes:
>
> > On 13 April 2018 at 10:00, David Kastrup wrote:
> >
> >> How about pointing out what you find hard to understand in the
> >> documentation then?
> >
> >
> > I'm not a musician and I'm a young lilypond user. So I don'
The piece I am setting has a flute cadenza which is notated in standard
size notes totalling 14 crotchets (quarter-notes) in length. The whole
cadenza is written between 2 successive barlines.
The prevailing time signature at this point is 6/8, and in the cadenza
all of the other instruments have
Hi David,
it seems you have to add a manual barline at \cadenzaOff, but otherwise
I don’t see any problem with
%
\version "2.19.80"
<<
{
\time 6/8
2.
\cadenzaOn
\repeat unfold 14 { 4 }
\cadenzaOff
\bar "|"
2.
}
{
2.
2.*14/3\fermata
2.
30 matches
Mail list logo
