headers
Juergen Reuter | 1 Nov 2004 04:42
Picon
Favicon

make-span-event

Hi!

Maybe this is a silly question, but there is something that I do not quite 
understand.  I am trying to create span events in a music function:

\version "2.4.0"
crescendo = #(def-music-function
	       (location music) (ly:music?)
	       (make-music 'SequentialMusic
			   'elements (list
				      (make-span-event 'CrescendoEvent START)
				      music
				      (make-span-event 'CrescendoEvent STOP))))

crescendoStart = #(make-span-event 'CrescendoEvent START)
crescendoStop = #(make-span-event 'CrescendoEvent STOP)

\score {
  <<
    { c d\crescendoStart e\crescendoStop f }
    { c \crescendo { d e } f }
    { c d\cr e\endcr f }
  >>
}

In this example, the predefined \cr and \endcr work well; also do the 
locally defined \crescendoStart and \crescendoStop.  However, although the 
\crescendo music function uses exactly the same scheme expressions for 
creating span events, applying the \crescendo function does not show any 
effect.  What I am doing wrong?
(Continue reading)

Permalink | Reply | 4 comments |
headers
Chip | 1 Nov 2004 05:56

Re: Help wanted: editor web-page!

Han-Wen Nienhuys wrote:
> chip <at> wiegand.org writes:
> 
>>>
>>>>Is there a specific style sheet to use
>>>
>>>
>>>    newweb/colors.css
>>>    newweb/newweb.css
>>>
>>>
>>>
>>>>(I would assume there would be one so the page matches the existing
>>>>lilypond web site)? How would the completed page be handled (sent as a
>>>>zipped file to a particular person, or would this person be given ftp
>>>>access to a server?)?
>>>
>>>
>>>The lilypond website is in CVS module newweb, have a look
>>>
>>>    cvs -d :ext:anoncvs <at> subversions.gnu.org:/cvsroot/lilypond co newweb
>>>
>>>Until you have CVS write access, a CVS diff would be best.
>>>
>>>Jan.
>>
>>I have no idea how cvs works. That's one area I just have not explored.
> 
> 
> Once we have the content (ie.: the text and the pictures), we can
(Continue reading)

Permalink | Reply | 0 comments |
headers
Carl Sorensen | 1 Nov 2004 10:19
Picon

Re: question about a <> mark similar to a c-> notation...

On Sun, 2004-10-31 at 16:20, Juergen Reuter wrote:

> And, whenever changing feta-schrift, don't forget to clean the font such 
> that all font files will be rebuilt; otherwise, you will not see any 
> change, or the font will be messed up (as inserting a new character 
> changes the numbers in the font tables).

The font is cleaned by executing buildscripts/out/clean-fonts, right?

> 
> BTW. (Carl/Graham?), maybe above instructions fit into the programming 
> concepts manual?
> 

I've added the info to my draft of the programming concepts manual.
Thanks.

Carl
Permalink | Reply | 2 comments |
headers
Erik Sandberg | 1 Nov 2004 10:22
Picon
Picon
Favicon

Re: convert-ly dummy rules

Citerar Jan Nieuwenhuizen <janneke <at> gnu.org>:
> > However, Han says that it'll make development a bit harder.  I don't
> > quite understand why, but I'm willing to trust him.  :)
> 
> > > I'd rather not, it makes development a little harder. I like the
> > > little extra room I have to add extra conversions.
> 
> Couldn't we create that extra room by adding an extra level, eg, 2.4.0.1

Couldn't we just do this upgrading thing for stable versions only? That's when
it's most relevant anyway, and there will be no development drawbacks for hwn
(convert-ly rarely does things for stable versions..)

Erik
Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 1 Nov 2004 11:10
Picon

formatting issues


I'm improving the texinfo documents to get a decent layout (no
overlong lines any more for lilypond.dvi!).  Some remarks:

  . Don't use extra indentation within  <at> example ...  <at> end example.

  . Please use ` <at> /' to insert breakpoints in long file names, namely
    after `/' but before `-' and `.':

       http://www
       .foo/
       bar
       -line.ly

    This makes it clear that `.' and `-' are part of the file name and
    not sentence syntax.

    If you disagree please tell me, and I'll change it accordingly.

      Werner
Permalink | Reply | 0 comments |
headers
Némo | 1 Nov 2004 14:16
Picon

Re: 2.4 announcement

Han-Wen Nienhuys wrote:
> Hi Y'all,
> 
> 
> I've just posted the LilyPond 2.4 release announcement to the
> following channels,
> 
> 	News:
> 		rec.music.compose
> 		comp.os.linux.announce
> 		comp.music.research
> 		comp.text.tex
> 	Mail:
> 
> 	      info-lilypond <at> gnu.org
> 	      linux-audio-announce <at> music.columbia.edu
> 	      linux-audio-dev <at> music.columbia.edu
> 
>      Web:
> 
> 	      freshmeat.net
> 
> 
> I would be very grateful if someone could take care of announcing lily
> on the following remaining channels,
> 
>       abcusers <at> argyll.wisemagic.com
>       rosegarden-user <at> lists.sourceforge.net
>       info-gnu <at> gnu.org
>       noteedit-users <at> lists.berlios.de
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nicolas Sceaux | 1 Nov 2004 16:42
X-Face
Picon
Favicon

Re: make-span-event

Juergen Reuter <reuter <at> ipd.uka.de> writes:

> Hi!
>
> Maybe this is a silly question, but there is something that I do not quite 
> understand.  I am trying to create span events in a music function:
>
> \version "2.4.0"
> crescendo = #(def-music-function
> 	       (location music) (ly:music?)
> 	       (make-music 'SequentialMusic
> 			   'elements (list
> 				      (make-span-event 'CrescendoEvent START)
> 				      music
> 				      (make-span-event 'CrescendoEvent STOP))))
>
> crescendoStart = #(make-span-event 'CrescendoEvent START)
> crescendoStop = #(make-span-event 'CrescendoEvent STOP)
>
> \score {
>   <<
>     { c d\crescendoStart e\crescendoStop f }
>     { c \crescendo { d e } f }
>     { c d\cr e\endcr f }
>   >>
> }
>
> In this example, the predefined \cr and \endcr work well; also do the 
> locally defined \crescendoStart and \crescendoStop.  However, although the 
> \crescendo music function uses exactly the same scheme expressions for
(Continue reading)

Permalink | Reply | 3 comments |
headers
Nicolas Sceaux | 1 Nov 2004 17:45
X-Face
Picon
Favicon

Re: make-span-event

Nicolas Sceaux <nicolas.sceaux <at> free.fr> writes:

> Juergen Reuter <reuter <at> ipd.uka.de> writes:
>
>> Hi!
>>
>> Maybe this is a silly question, but there is something that I do not quite 
>> understand.  I am trying to create span events in a music function:
>>
>> \version "2.4.0"
>> crescendo = #(def-music-function
>> 	       (location music) (ly:music?)
>> 	       (make-music 'SequentialMusic
>> 			   'elements (list
>> 				      (make-span-event 'CrescendoEvent START)
>> 				      music
>> 				      (make-span-event 'CrescendoEvent STOP))))
>>

A naive solution:

crescendo = #(def-music-function (location music) (ly:music?)
               (let* ((seq (ly:music-property music 'elements))
                      (first (ly:music-deep-copy (car seq))))
                 (set! (ly:music-property first 'elements)
                       (cons (make-span-event 'CrescendoEvent START)
                             (ly:music-property first 'elements)))
                 (let ((result (list first)))
                  (make-sequential-music (do ((e (cadr seq) (car rest))
                                              (rest (cddr seq) (cdr rest)))
(Continue reading)

Permalink | Reply | 2 comments |
headers
Heikki Johannes Junes | 1 Nov 2004 21:25
Picon
Picon

`Academy of E ngraved Music´

I would like to see some notations in the manual `expanded´. Especially,
it would be very useful to include in Section `5.7.8 Articulations´ with all
accents, pralls, mordents, etc. explanations how these marks have been used in
the past. For example, give briefly an etymologic overview on how J.S. Bach used
`turn´, `mordent´, `prall´.

Putting such information about the etymology (or development) of engraved music
would transform the manual to an invaluable resource of Engraved Music. Thus, it
could serve at the same time as the LilyPond manual and as a compulsory reading
in the `Academy of Engraved Music´. Also, the bibliography references should be
included sooner or later.

Here are the sections which could be `expanded´ (my list):

5.7.8 Articulations
 - etymologic overview: which systems are available
5.7.9 Running trills
 - starting on the note or above? speed?
5.7.12 Glissando
 - what does it mean in instruments with 12-tone, 24-tone, or continuous tuning
5.8.7 Measure repeats
 - how to separate the marks which repeat the bar once, two or three times, etc.
5.10.4 Arpeggio
 - speed, to `pre-play´ or to `start-at and post-play´?
5.12.1 Harmonic notes
 - when and how these are used?

These instructions would then also serve as a specification on what we wanted to
implement and why.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Werner LEMBERG | 1 Nov 2004 11:13
Picon

Re: indent in lilypond-book

> Between 2.3.18 or so (maybe as late as .20 or .22) and .25,
> lilypond-book no longer indents the first line in long (two-page)
> scores in latex documents.

Example, please, for further investigation.

    Werner
Permalink | Reply | 3 comments |

Gmane