It turns out that custom annotation types were not properly handled.
\annotate looks up the LaTeX value in an alist dictionary, and for custom
annotations this simply returned #f.
Pushed a fix, should work now.
Thanks for the report.
Best
Urs
Thanks :-)
I still have an issue on
Am 30.01.2015 um 21:50 schrieb Philippe Massart:
It turns out that custom annotation types were not properly handled.
\annotate looks up the LaTeX value in an alist dictionary, and for
custom annotations this simply returned #f.
Pushed a fix, should work now.
Thanks for the report.
Best
On Fri, Jan 30, 2015 at 3:11 PM, Urs Liska u...@openlilylib.org wrote:
Am 30.01.2015 um 22:06 schrieb David Nalesnik:
[...] what we find at
http://lilypond.org/doc/v2.18/Documentation/internals/scheme-functions:
*Function:* *ly:music-property** mus sym val*
Return the value for
I still have an issue on the example file, on the custom annotation, with
this message:
./annotate.annotations.inp:15: Undefined control sequence.
argument See \textbackslash what is \possible
[opts]{args}
l.15 {custom-annotation}
On Fri, Jan 30, 2015 at 2:27 PM, Peter Gentry peter.gen...@sunscales.co.uk
wrote:
Date: Thu, 29 Jan 2015 22:16:12 +0100
From: and...@andis59.se and...@andis59.se
To: lilypond-user lilypond-user@gnu.org
Subject: Where are Lilypond Scheme functions documented?
Message-ID:
Hi Craig,
Am 30.01.2015 um 17:59 schrieb Craig Dabelstein:
Urs,
Here is a zip of the complete project.
Thank you, this was indeed instructive (and a nice score BTW).
There is an issue with your set-up which I had immediately noticed and
wanted to tell you about, even before I realized you
Am 30.01.2015 um 22:06 schrieb David Nalesnik:
On Fri, Jan 30, 2015 at 2:27 PM, Peter Gentry
peter.gen...@sunscales.co.uk mailto:peter.gen...@sunscales.co.uk
wrote:
Date: Thu, 29 Jan 2015 22:16:12 +0100
From: and...@andis59.se mailto:and...@andis59.se
and...@andis59.se
From: Thomas Morley thomasmorle...@gmail.com
To: David Sumbler da...@aeolia.co.uk
Cc: lilypond-user lilypond-user@gnu.org
Subject: Re: Key signature and key cancellation need to be aligned
Date: Thu, 29 Jan 2015 11:21:15 +0100
2015-01-28 19:00 GMT+01:00 David Sumbler da...@aeolia.co.uk:
Date: Thu, 29 Jan 2015 22:16:12 +0100
From: and...@andis59.se and...@andis59.se
To: lilypond-user lilypond-user@gnu.org
Subject: Where are Lilypond Scheme functions documented?
Message-ID: 54caa31c.1060...@andis59.se
Content-Type: text/plain; charset=utf-8; format=flowed
Have a look at
Hi Pierre,
I am writing here as an interested spectator. I find this very interesting. The
optimal solution would be to have the stem lengths being calculated from the
note distances and in a uniform syntax with other transcriptions of gregorian
music – know that’s not your scope, I am just
2015-01-29 22:06 GMT+01:00 and...@andis59.se and...@andis59.se:
On 2015-01-28 21:45, Pierre Perol-Schneider wrote:
Thank you Anders,
myNotes = \relative c' { \pedA a2\5 \pedF cis'2\4 } seems to work.
It seems that your function cannot be applied into a chord.
Well, I don't know what to
Thanks Urs,
And you put the \include annotate code in the main-init.ily file?
Craig
On Sat Jan 31 2015 at 8:05:57 AM Urs Liska u...@openlilylib.org wrote:
Hi Craig,
Am 30.01.2015 um 17:59 schrieb Craig Dabelstein:
Urs,
Here is a zip of the complete project.
Thank you, this was
Am 31. Januar 2015 03:05:24 MEZ, schrieb Craig Dabelstein
craig.dabelst...@gmail.com:
Thanks Urs,
And you put the \include annotate code in the main-init.ily file?
Yes, and any similar code like the include of global-defs.ily etc. too.
Urs
Craig
On Sat Jan 31 2015 at 8:05:57 AM Urs Liska
http://lilypond.org/doc/v2.18/Documentation/notation/expressive-marks-as-lines#Selected-Snippets-33
Yes, this shows the cross-staff arpeggio. But the examples there have
always two notes in each staff. It would be interesting how to notate an
arpeggio when only one note is e.g. in the bass
Am 30.01.2015 um 03:30 schrieb Br. Samuel Springuel:
a cross staff arpeggio
Ha! I think I know where to find this one:
http://lilypond.org/doc/v2.18/Documentation/notation/expressive-marks-as-lines#Selected-Snippets-33
Yes, this shows the cross-staff arpeggio. But the examples there have
Hi Urs,
I put \include scholarly/annotate.ily in each of my 24 files -- one for
each instrument.
In the score I put:
\include scholarly/annotate.ily
\setAnnotationExportTargets #'(plaintext latex)
I added 1 criticalremark and 1 musical issue to test it out.
The generated parts (both the log
[OFF TOPIC]
I'm stuck with converting automagically score/ties into tab/glissandi.
Thanks anyway for the reminder!
Cheers,
Pierre
2015-01-29 22:06 GMT+01:00 and...@andis59.se and...@andis59.se:
BTW, have you gotten anywhere with the LSR snippet? (just curious...)
Am 30.01.2015 um 09:35 schrieb Craig Dabelstein:
Hi Urs,
I put \include scholarly/annotate.ily in each of my 24 files -- one
for each instrument.
In the score I put:
\include scholarly/annotate.ily
\setAnnotationExportTargets #'(plaintext latex)
I added 1 criticalremark and 1 musical issue
Thank you Mark , Robin , Noeck , Dominic, Helge Kruse, Br. Samuel Springuel and
David Nalesnik:
after use the following the warning message is gone.\set
PianoStaff.connectArpeggios = ##t
Immanuel,Ming
On Thursday, January 29, 2015 10:03 PM, Mark Stephen Mrotek
carsonm...@ca.rr.com
Am 30.01.2015 um 08:16 schrieb Urs Liska:
Am 30.01.2015 um 08:13 schrieb Philippe Massart:
Probably not. I assume that hash hasn't been properly filtered. Could you
please post the generated .inp and maybe also the LilyPond file?
Urs
These are based on the sample file included :
Ah, OK.
Dear Sister Judit,
Dear All,
I slightly changed the snippet for a much easier typesetting; See:
http://lsr.di.unimi.it/LSR/Item?id=973
Now you can include a modernGregorian.ily file and simply code like:
...
d d d \melisma { f g \lst a } \orn #1 g g \melisma { g a \lst c' }
...
Some issues
21 matches
Mail list logo
