>> I tried to read the associatedVoice property, but that seems to be
>> empty.
>
> Try the context property associatedVoiceContext . I think it gets set
> by the iterator resposible for \lyricsto et al, just don't know when.
Just tried it, and it indeed contains the voice context required. In
Maurits Lamers writes:
>>> But those values are not retrievable through (ly:context-id
>>> context), are they?
>>
>> They are. LilyPond just does the equivalent of
>> << \context Voice = "1" ...
>> \context Voice = "2" ...
>> \context Voice = "3"
>>
>> But
>> But those values are not retrievable through (ly:context-id context), are
>> they?
>
> They are. LilyPond just does the equivalent of
> << \context Voice = "1" ...
> \context Voice = "2" ...
> \context Voice = "3"
>>>
>
> But this is just ad-hoc for a << \\ \\ >> construct.
So, if I
Maurits Lamers writes:
>> Op 20 okt. 2017, om 18:32 heeft David Kastrup het
>> volgende geschreven:
>>
>> Maurits Lamers >
>> writes:
>>
>>> I can retrieve the retrieve that name through
> Op 20 okt. 2017, om 18:32 heeft David Kastrup het volgende
> geschreven:
>
> Maurits Lamers >
> writes:
>
>> Hi all,
>>
>> I am trying to extend the default event-listener.ly to also include
>> information about in which
Maurits Lamers writes:
> Hi all,
>
> I am trying to extend the default event-listener.ly to also include
> information about in which voice a specific note is being played.
> When the voice is defined using
>
> \new Voice = voicename
>
> I can retrieve the retrieve that
Hi all,
I am trying to extend the default event-listener.ly to also include information
about in which voice a specific note is being played.
When the voice is defined using
\new Voice = voicename
I can retrieve the retrieve that name through (ly:context-id
(ly:translator-context engraver)).
Hello,
On 15/10/14 03:35, flip wrote:
It looks like this patch never made it into the current development
repository (or it got put into some place I couldn't find it). I've manually
tweaked my event-listener.ly for now, but wondered if this just sort of got
mis-placed. We need to output some
It looks like this patch never made it into the current development
repository (or it got put into some place I couldn't find it). I've manually
tweaked my event-listener.ly for now, but wondered if this just sort of got
mis-placed. We need to output some drum part events for some experiments
Hi list,
A patch about event-listener.ly was send to:
https://codereview.appspot.com/8165043/
Phil.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On Thu, Mar 28, 2013 at 08:09:45PM +0100, Phil Hézaine wrote:
And what about the conversion of drum notes to midi pitches?
I'm not able to find a way to write a specific function for that issue.
Graham? Have you some time?
To clarify, I wasn't suggesting that drums should be converted to
midi
on 2013-03-27 at 14:13 Graham Percival wrote:
On Wed, Mar 27, 2013 at 08:21:53AM -0300, luis jure wrote:
BTW, i was quite curious myself about why the point-and-clik info was
included in the first place. i thought it was only useful for pdf
files. is this information used by your virtual
On Thu, Mar 28, 2013 at 2:46 PM, luis jure l...@internet.com.uy wrote:
BTW, is phil's patch going be merged into lilypond's event-listener?
It can be. Phil, please make a git-formatted patch and send a request
for merging it to bug-lilypond mailing list. If you need help with
this, let us
Le 28/03/2013 15:00, Janek Warchoł a écrit :
On Thu, Mar 28, 2013 at 2:46 PM, luis jure l...@internet.com.uy wrote:
BTW, is phil's patch going be merged into lilypond's event-listener?
It can be. Phil, please make a git-formatted patch and send a request
for merging it to bug-lilypond
Hi Phil,
On Thu, Mar 28, 2013 at 8:09 PM, Phil Hézaine philippe.heza...@free.fr wrote:
Le 28/03/2013 15:00, Janek Warchoł a écrit :
Phil, please make a git-formatted patch and send a request
for merging it to bug-lilypond mailing list. If you need help with
this, let us know.
Hi,
Yes, I
on 2013-03-28 at 20:09 Phil Hézaine wrote:
And what about the conversion of drum notes to midi pitches?
mmm... i wonder if that's strictly necessary? once you get the correct
text output, as you do now, it's trivial to convert the drum notes names to
pitches with whatever program you're using
Le 28/03/2013 21:44, Janek Warchoł a écrit :
Hi Phil,
On Thu, Mar 28, 2013 at 8:09 PM, Phil Hézaine philippe.heza...@free.fr wrote:
Le 28/03/2013 15:00, Janek Warchoł a écrit :
Phil, please make a git-formatted patch and send a request
for merging it to bug-lilypond mailing list. If you need
Le 28/03/2013 23:36, luis jure a écrit :
on 2013-03-28 at 20:09 Phil Hézaine wrote:
And what about the conversion of drum notes to midi pitches?
mmm... i wonder if that's strictly necessary? once you get the correct
text output, as you do now, it's trivial to convert the drum notes names to
on 2013-03-26 at 16:04 Graham Percival wrote:
I'm quite curious about this -- do drum events not have
point-and-click info?
BTW, i was quite curious myself about why the point-and-clik info was
included in the first place. i thought it was only useful for pdf files.
is this information used
Le 27/03/2013 00:04, Graham Percival a écrit :
On Tue, Mar 26, 2013 at 08:12:42PM +0100, Phil Hézaine wrote:
for NoteEvent:
#(define (format-note engraver event)
(let* ((origin (ly:input-file-line-char-column
(ly:event-property event 'origin
(print-line
on 2013-03-27 at 18:35 Phil Hézaine wrote:
@ Luis
In MY OWN PERSONAL...etc... I have added a context for a DrumVoice
which was absent.
wonderful, phil, it works to perfection now. a million thanks!
___
lilypond-user mailing list
On Wed, Mar 27, 2013 at 08:21:53AM -0300, luis jure wrote:
on 2013-03-26 at 16:04 Graham Percival wrote:
I'm quite curious about this -- do drum events not have
point-and-click info?
BTW, i was quite curious myself about why the point-and-clik info was
included in the first place. i
Le 26/03/2013 02:29, Graham Percival a écrit :
On Mon, Mar 25, 2013 at 10:05:28PM +0100, Phil Hézaine wrote:
Le 25/03/2013 17:29, Graham Percival a écrit :
To add \parenthesize, you need to create a similar function or
extend that original one to deal with those events. To see the
events,
On Tue, Mar 26, 2013 at 08:12:42PM +0100, Phil Hézaine wrote:
for NoteEvent:
#(define (format-note engraver event)
(let* ((origin (ly:input-file-line-char-column
(ly:event-property event 'origin
(print-line engraver
note
;;
on 2013-03-26 at 20:12 Phil Hézaine wrote:
You're right. Though it was not evident at starting it was not so
difficult to solve the problem. Thanks for your clarification.
I paste for Luis and others my solution.
this is great, phil, thank you.
i must be missing something, though, because
hello list,
i have just discovered that you can save music events to a file with
event-listener.ly. this is an incredible feature for what i'm trying to
do, that is generate csound scores from lilypond files. i managed to do
that from the midi file generated by lilypond, using a very simple
On Mon, Mar 25, 2013 at 08:58:09AM -0300, luis jure wrote:
i looked at event-listener.ly, but i'm afraid it's way over my head. i can
hardly manage some basic python, for me scheme is undecipherable.
could anyone give me a hint how to modify event-listener.ly to recognize
parenthesized
on 2013-03-25 at 09:29 Graham Percival wrote:
Unfortunately you'll need some scheme knowledge, but if you can
get the general idea of the below function then you should be
fine:
thanks for the thorough explanation, graham, you just ruined my easter
holidays... ;-)
first i need to finish
Le 25/03/2013 17:29, Graham Percival a écrit :
On Mon, Mar 25, 2013 at 08:58:09AM -0300, luis jure wrote:
i looked at event-listener.ly, but i'm afraid it's way over my head. i can
hardly manage some basic python, for me scheme is undecipherable.
could anyone give me a hint how to modify
on 2013-03-25 at 22:05 Phil Hézaine wrote:
Today, after the same discovery I was wondering the same question than
Luis but for drum-types (in \drummode, ie: sna, wbl... )
funny, i was intending to use it for a drumstaff also...
___
lilypond-user
On Mon, Mar 25, 2013 at 10:05:28PM +0100, Phil Hézaine wrote:
Le 25/03/2013 17:29, Graham Percival a écrit :
To add \parenthesize, you need to create a similar function or
extend that original one to deal with those events. To see the
events, try:
\displayMusic { c'4 \parenthesize d' e }
31 matches
Mail list logo