2015-01-10 4:36 GMT+01:00 Craig Dabelstein craig.dabelst...@gmail.com:
Thanks Thomas. text-script-event was the one I was missing.
Hi again,
let me add some basic hints.
If you don't know how something is called in LilyPond, it's often
useful to display it as a first and lookup what you get
Hi Kieren,
Am 10.01.2015 um 16:20 schrieb Kieren MacMillan:
Hi Jan-Peter,
TimeSignature grobs are another kind, I'd like to add conditionally or with the
edition-engraver, if the instrument-transposition changes.
Um… you mean KeySignature? =)
In any case, YES — this would let me remove
Hi Jan-Peter,
TimeSignature grobs are another kind, I'd like to add conditionally or with
the edition-engraver, if the instrument-transposition changes.
Um… you mean KeySignature? =)
In any case, YES — this would let me remove about a third of the remaining \tag
constructs in the content
Hi Jan-Peter,
I'm still having a hard time understanding how engravers, events,
acknowledgers etc. relate, so I'm not sure if I understand your
explanations. Am I right that the problem is *not* in addressing the
score context but that marks are simply not supported yet?
And if yes, is this a
Am 10.01.2015 um 16:20 schrieb Kieren MacMillan:
Hi Jan-Peter,
TimeSignature grobs are another kind, I'd like to add conditionally or with the
edition-engraver, if the instrument-transposition changes.
Um… you mean KeySignature? =)
In any case, YES — this would let me remove about a third
Hi list,
is it possible to collect the measure/measure-position values of all
breaks in a compilation and output that to a logfile?
As mentioned yesterday I found a way to ask LilyPond to compile only a
portion of a score by passing a range of measures.
And if I had a generated list of all
Hi Urs,
Am 10.01.2015 um 15:29 schrieb Urs Liska:
I'm not sure if I understand your explanations. Am I right that the
problem is *not* in addressing the score context but that marks are
simply not supported yet?
Yes
And if yes, is this a fundamental issue or is it just that marks have
to be
Hi Urs, hi list,
as I am the inventor of the edition-engraver, I'd like to try some
explanation ...
The edition-engraver is a scheme-engraver, which looks at most of the
defined hooks, if there are mods for its id on the current time (=
measure + position-in-measure).
They are:
* initialize
- Original Message -
From: James Harkins jamshar...@qq.com
To: lily-users lilypond-user@gnu.org
Sent: Saturday, January 10, 2015 3:12 AM
Subject: Demo: Score and parts template
Hi,
Since the question came up about organizing LilyPond code for score and
parts, I thought I would make
Hi David,
thank you for that suggestion.
I'll try to get my mind around this ASAP.
On the first sight I don't understand too much of it. But at least I
notice that I'm not afraid of these lambda, let and let* constructs
anymore. Finally I'm getting *somewhere* to familiarity with the basic
Am 10.01.2015 um 19:34 schrieb Kieren MacMillan:
Hi Urs,
I'm right now busy moving our Fried score to an edition-engraver based set-up,
which is more than promising.
I’m so glad you’ve jumped on the bandwagon. =)
Me too ...
Maybe it would have been better to do so in a project where
Am 10.01.2015 um 22:22 schrieb Orm Finnendahl:
Hi,
I can't find documentation about how to write segmented glissando
lines, like in the attached png. The line segments have to get notated
with precise rhythms, so I'm looking for something similar to
glissando notation but without noteheads.
Hi,
I can't find documentation about how to write segmented glissando
lines, like in the attached png. The line segments have to get notated
with precise rhythms, so I'm looking for something similar to
glissando notation but without noteheads.
I tried this:
\new Staff
\relative c'' {
\hide
Am 10.01.2015 um 23:02 schrieb Orm Finnendahl:
Hi Urs,
Am Samstag, den 10. Januar 2015 um 22:22:15 Uhr (+0100) schrieb Urs
Liska:
Can't test right now, but what about \omit NoteHead?
same problem, glissandolines aren't drawn at all if NoteHeads are
omitted:
And making the NoteHead
On Fri, Jan 9, 2015 at 10:12 PM, James Harkins jamshar...@qq.com wrote:
Hi,
Since the question came up about organizing LilyPond code for score and
parts, I thought I would make a quick demo of what I believe to be the
standard way to do it. Somehow I pieced these ideas together from LP code
Hi Urs,
Am Samstag, den 10. Januar 2015 um 22:22:15 Uhr (+0100) schrieb Urs
Liska:
Can't test right now, but what about \omit NoteHead?
same problem, glissandolines aren't drawn at all if NoteHeads are
omitted:
%
\version 2.19
\new Staff
2015-01-10 15:44 GMT+01:00 Jan-Peter Voigt jp.vo...@gmx.de:
So, if one can show a scheme-engraver, that produces marks (or time-sigs)
programmaticly, I can easily add it to the edition-engraver.
Hi Jan-Peter,
I did not look into your edition-engraver, below you'll find an
engraver printing
Hi Urs,
On Sat, Jan 10, 2015 at 8:44 AM, Urs Liska u...@openlilylib.org wrote:
Hi list,
is it possible to collect the measure/measure-position values of all
breaks in a compilation and output that to a logfile?
Yes, it is possible. As far as I can tell, though, an engraver only has
access
Am 10.01.2015 um 20:16 schrieb Kieren MacMillan:
Hi Urs,
As it is possible to inject temporary LilyPond code I see a lot of fancy things
becoming possible. Including my favourite original breaks ;-)
Uh-oh… Are we going to get into another debate about what “edition” means?! ;)
Not
Am 10.01.2015 um 22:04 schrieb David Nalesnik:
On Sat, Jan 10, 2015 at 2:06 PM, Urs Liska u...@openlilylib.org
mailto:u...@openlilylib.org wrote:
Hi David,
thank you for that suggestion.
I'll try to get my mind around this ASAP.
On the first sight I don't understand too much
It would be fantastic if that could be integrated in the edition-engraver. I'm
very sorry that I can only express wishes and can't offer any help.
Actually I'm right now busy moving our Fried score to an edition-engraver based
set-up, which is more than promising.
Urs
Am 10. Januar 2015
Hi Urs,
As it is possible to inject temporary LilyPond code I see a lot of fancy
things becoming possible. Including my favourite original breaks ;-)
Uh-oh… Are we going to get into another debate about what “edition” means?! ;)
Best,
Kieren.
___
Kieren MacMillan,
On Sat, Jan 10, 2015 at 2:06 PM, Urs Liska u...@openlilylib.org wrote:
Hi David,
thank you for that suggestion.
I'll try to get my mind around this ASAP.
On the first sight I don't understand too much of it. But at least I
notice that I'm not afraid of these lambda, let and let* constructs
Hi Urs,
I'm right now busy moving our Fried score to an edition-engraver based
set-up, which is more than promising.
I’m so glad you’ve jumped on the bandwagon. =)
I suppose, in all fairness, I should get off my butt and get my Git-flow
working now… ;)
Cheers,
Kieren.
On Sat, Jan 10, 2015 at 1:39 PM, David Nalesnik david.nales...@gmail.com
wrote:
\version 2.19.15
writeBreaksEngraver =
#(lambda (context)
(let ((out (open-output-file output.txt)))
(make-engraver
(listeners
((line-break-event engraver event)
(let* ((ccc
Hi Urs,
On Sat, Jan 10, 2015 at 3:50 PM, Urs Liska u...@openlilylib.org wrote:
Am 10.01.2015 um 22:04 schrieb David Nalesnik:
On Sat, Jan 10, 2015 at 2:06 PM, Urs Liska u...@openlilylib.org
mailto:u...@openlilylib.org wrote:
Hi David,
thank you for that suggestion.
I'll
Hi,
version 2.19.15:
Is anyone using instrumentSwitch that can explain what the various
variables in addInstrumentDefinition mean?
I don't care about the midi transposition. AFAIK I really only
want the key signature to change automatically when I do an
instrument switch.
In the following
Hi David,
thanks for your work - this is a really great tool.
I often work with things like this:
http://lsr.di.unimi.it/LSR/Item?id=960
http://lsr.di.unimi.it/LSR/Item?id=960
so what I found in this thread is very interesting for analysis purposes.
I started to try some modifications on
Hello,
Still struggling with gregorian.ly:
So I compile first the gregorian to pdf then convert eps (directly as
dbackend=eps returns inverted black-white and very bad quality), and
include in mybook.ly as
\markup { \epsfile #X #20 #rorateCoeli.eps }
but I dont find how to crop the image to
Hi Orm,
How about :
\version 2.19.15
#(define (add-gliss m)
(case (ly:music-property m 'name)
((NoteEvent) (set! (ly:music-property m 'articulations)
(append (ly:music-property m 'articulations)
(list (make-music (quote GlissandoEvent)
Hi Klaus,
On Sat, Jan 10, 2015 at 7:03 PM, Klaus Blum benbigno...@gmx.de wrote:
Hi David,
thanks for your work - this is a really great tool.
I often work with things like this:
http://lsr.di.unimi.it/LSR/Item?id=960
http://lsr.di.unimi.it/LSR/Item?id=960
so what I found in this thread
From: Phil Holmes
Since the question came up about organizing LilyPond code for score and
parts, I thought I would make a quick demo of what I believe to be the
standard way to do it. Somehow I pieced these ideas together from LP code
that I found online (Mozart Horn Concerto, as I
32 matches
Mail list logo
