Re: lilypond questions

[Mats Bengtsson]

> Slur marks look really bad for phrasing marks in 1.2.17, so I upgraded
> to 1.3.94 (using the debian package), and now they look fine.  Yay.
> 
> 
> However, the new version appears to ignore this:
> 
>    \property Staff.noVoltaBraces=1
> 
> I'm using this because I have piano music (two staffs) with a volta
> repeat, and don't want the repeat number and brace to be shown on the
> bass clef.  This worked fine in 1.2.17.

There've been some major changes to the input syntax since 1.2.17.
One such change is that most values now are specified in the 
syntax of the Scheme programming language (a LISP version).
For example, all boolean properties now use ##t for true and 
##f for false instead of the previous 1/0. 
Also, many properties have changed name and I'm not sure about
this specific one since I don't have a running Lilypond available.


> Also, the new version defaults to putting crescendos under the staff
> instead of above.  The reference manual tells me to use
> 
>    \property Voice.dynamicDirection = \up
> 
> which works perfectly.  However, lilypond complains loudly that this
> is depreciated and I should instead be using
> 
>    \property Voice.Crescendo \push #'direction = #1
> 
> which doesn't appear to do anything at all.

It should work, but I'm not sure about version 1.3.94.

> >> 4) In the title, I'd like to have a bit be superscripted.  I am no TeX
> >> expert, so I'm not sure how to do this.  I tried entering math mode
> >> but couldn't get it to work quite right.  "1$^{ere}$ Gymnopedie" or
> >> so is what I'd like.  I tried throwing backslashes at it, but still
> >> no luck.
> >
> > How about
> >
> > title ="1$^\\textrm{ere} Gymnop\\'edie" ;
> 
> This produces an error.  Looking at the TeX file ly2dvi -k produces,
> it appears something gets confused by the }, and this is generated:
> 
> \begin{document}
> \mudelatitle{1$^\textrm{ere}%
> \mudelacomposer{Erik Satie}%
> \makelilytitle
> 
> 
> Interestingly, running lilypond directly produces:
> 
> \def\mudelatitle{1$^\textrm{ere}%
>   Gymnop\'edie}
> 
> 
> So the closing brace (and Gymnop\'edie with it) is being lost
> somewhere, but I'm not sure where or how.  In the meantime, I can use
> the very ugly:
> 
>     title = "1$\\rm ^e$$\\rm ^r$$\\rm ^e$ Gymnop\\\'edie";

Yes, this nice TeX code formatting in the Lilypond output 
which inserts a newline after each '}' has caused many 
problems, since ly2dvi is unable to parse the two-line
definition. We really should solve this someway, I don't
know how. Another more or less ugly workaround is to 
create a separate LaTeX header file with a definition

\newcommand{\premiere}{1$^\textrm{ere}}

and include this file using 

\header{
...
  latexheaders = "myheaderfile.tex";
}

    /Mats



> 
> 
> 
> And another question:
> 
> My piece starts like this:
> 
>     R2. ^\textscript "Lent et douloureux" "Large" | R2. |
>     R2. | R2. |
>     r4 fis( \pp \< a | g fis cis |
> 
> However, the "lent et douloureux" (instructions for the playing of the
> piece) isn't displayed unless I change it into
> 
>     r1. ^\textscript "Lent et douloureux" "Large" *3/4 | R2. |
> 
> in which case the rest moves to a different spot and clashes with a
> rest from another voice.  Where's the appropriate place to put playing
> directions?
> 
> 
> And with my:
> 
>     r4 fis( \pp \< a | g fis cis |
> 
> the \pp clashes with the \<.  Ideally, I'd like the \pp to be
> printed just before the fis which it modifies instead of directly
> above it.  How do I do this?  (There are other cases where the note
> before it isn't a quarter rest, so just putting it on the r4 isn't a
> general solution)
> 
> 
> 
> Many thanks.
> 
> ------------------------------------------------------------
> --== Sent via Deja.com http://www.deja.com/ ==--
> Before you buy.
> 
> 
> 
> _______________________________________________
> Help-gnu-music mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/help-gnu-music
>