lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: extending event-listener.ly


From: Phil Hézaine
Subject: Re: extending event-listener.ly
Date: Fri, 29 Mar 2013 00:20:18 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4

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
pitches with whatever program you're using to process it.

Indeed. But Lilypond knows how to do this internally. If you look at the sources you'll see the midiDrumPitches in drumpitch-init.ly
It will be straightforward.

on the other hand...

I want to say: are there some improvements needed?

well, this is not related to your patch, but since you're at it... ;-)

i realized that the format-text function can only process simple text
scripts, but returns an error message when using a markup.

c^"accel." is OK, but:

c^\markup{ accel. } or c^\markup{ \italic { accel. }}

return errors:

Unsupported SCM value for format: (#<procedure line-markup (layout props
args)> (accel.))

Unsupported SCM value for format: (#<procedure line-markup (layout props
args)> ((#<procedure italic-markup (layout props arg)> accel.)))

in both cases the .notes file has an empty text line where the markups
were used.

looking at the code i see that the format-text function is very basic, i
guess it wouldn't be trivial to adapt it to handle markups?


Not for me!... err... to handle... :-)

best,

lj

Phil.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]