Re: grace notes in TimeSig

Stefan The mechanism used for timing means you have to include matching dummy grace notes in all parallel contexts. If you make the following change I think it will work as you want: dreiviertel = { \time 3/4 \grace {s32 s s} % matching grace timing #(override-auto-beam-setting '(e

Whole bar rests - in the wrong place

Hi all I was typesetting some stuff and I put in a whole bar rest: %% R2.^\fermataMarkup | %% Instead of hanging from the second line as the full-bar rest should, it hangs from the top line of the staff. So, what's going on? Thanks George -- View this message in context: http://www.nabb

"header", "layout" and "paper" blocks as variables...

hi. is there a way to put the header, layout and block values as variables? I woul like to use something like myheader = \header { . } mylayout = \layout { } mypaper = \paper { } and then call these variables to construct my score... I tried but I get errors like: ./instr/comhead

Re: Accessing header properties from ordinary markup

Am Mittwoch, 21. Mai 2008 schrieben Sie: > Le 21 mai 08 à 18:21, Reinhold Kainhofer a écrit : > > [...] how can I access the header fields from a top-level markup? > > Book and score title are dealt with in a special way: when they > are interpreted, the header variables are added to the properties

Re: location of rests and bar alignment between staffs

for synchronized staves you need to do something like this: \version "2.11.43" \header { tagline = "" } #(define mydrums '( (bassdrum default #f -1) (acousticbassdrum default #f 1) (hihat cross #f -1) (closedhihatcross #f

Re: When is "-" required in articulations?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Donnerstag, 22. Mai 2008 schrieb Nicolas Sceaux: > Le 22 mai 08 à 12:44, Reinhold Kainhofer a écrit : > > Actually, these two are not the same, in particular the spacing is > > very different. I ran into this problem just a few days ago: With {...},

location of rests and bar alignment between staffs

Hello, I'm new to lilypond and would like to create notation for an ensemble of hand drums. Currently, I'm having trouble with two specific layout issues and I wasn't able to find exactly what I needed in searching the archives. The first is how to position a rest relative to a single lin

Re: Lilypond version compile times

My bad- I should have read the fixes for 2.11.43.. Cheers, Jack - Original Message From: Jack Cooper <[EMAIL PROTECTED]> To: List lilypond-user ; List lilypond-user Sent: Thursday, May 22, 2008 2:26:01 PM Subject: Lilypond version compile times A silly question- a while back, peop

Lilypond version compile times

A silly question- a while back, people were reporting drastically slower compile times for the newest release of lilypond from that for previous versions. For that reason, I haven't version 11 since something like 2.11.32 (or maybe earlier..). Has the speed issue been resolved? If I recall, the

Re: When is "-" required in articulations?

Le 22 mai 08 à 12:44, Reinhold Kainhofer a écrit : Actually, these two are not the same, in particular the spacing is very different. I ran into this problem just a few days ago: With {...}, when lilypond decides on the space between the words, the spaces between the words was a too tight,

Re: Redefining \smallCaps, Sceaux method - compile error

Le 22 mai 08 à 12:13, Nicholas Wastell a écrit : Hello list, A couple of months ago, Nicolas Sceaux showed some code to redefine the \smallCaps function to extend support to non-ascii characters (ref: ). I have just tried inserting his code in a .ly file, but

Re: Figured Bass commands in property-init.ly

Reinhold Kainhofer kainhofer.com> writes: > > Am Mittwoch, 21. Mai 2008 schrieb Carl D. Sorensen: > > By way of standard practice, is it better to define > > figuredBassStackingDirUpOff as an \override (which makes it absolute, but > > keeps adding to the props list), or as a \revert, which undo

grace notes in TimeSig

Dear lilypondusers, I have a problem with TimeSig in connection with grace-notes. I don't understand why the grace notes why the grace-notes in the below quoted example appear before the time signature. It must have to do with the TimeSig function. How can I fix the problem? Here is the example: %%

Re: How to show a small glissando?

Thanks Mats, I looked at the Internal Reference Manual, but I would never have guessed the solution. But it worked like a charm. Arjan On 22 mei 2008, at 13:04, Mats Bengtsson wrote: If you add the following two lines before the first note, the note spacing will be adjusted, when necessar

Re: rhythm template function

On Thu, May 22, 2008 at 5:09 AM, Jay Anderson <[EMAIL PROTECTED]> wrote: > "Easy Rhythm Template Creation" added to the lsr. Thanks. > > -Jay Hi Jay, I had some trouble getting tuplets to work with your snippet. Here's a modified version that checks whether a tuplet (TimeScaledMusic) is used

Re: How to show a small glissando?

If you add the following two lines before the first note, the note spacing will be adjusted, when necessary, to give each glissando a minimum length (which is long enough that it's also printed). \override Glissando #'springs-and-rods = #ly:spanner::set-spacing-rods \override Glissando #'minimu

Re: When is "-" required in articulations?

Am Donnerstag, 22. Mai 2008 schrieb Valentin Villenave: > "Markup expressions may also be enclosed in double quotes "...". Such > expressions are treated as text strings and may not contain nested > expressions or commands. Therefore, braces are generally prefered to > double quotes." Actually, th

Redefining \smallCaps, Sceaux method - compile error

Hello list, A couple of months ago, Nicolas Sceaux showed some code to redefine the \smallCaps function to extend support to non-ascii characters (ref: ). I have just tried inserting his code in a .ly file, but I see errors on compiling: In procedure make-small-caps

How to show a small glissando?

Dear list, Could someone please show me how to make a \glissando appear when the notes are very close to each other? See this small example: \version "2.11.45" \paper { ragged-right = ##t } %% makes the first \glissando disappear \score { \relative c'' { es8\glissando d4.~ d2 \glissan