Re: Multi-Measure Rests: Adding to what gets printed?

Alexander, Thanks so much. I'll take a look at your suggestion in detail. Randy rasAK wrote: > > In my orchestral parts, I would like Multi-Measure Rests to have both: > (1) an integer representing the number of measures in the current MMR, > centered above (default behavior) > (2) a second

Cannot connect tie in a voice of polyphony

Dear users. I found a problem in polyphony. In version 2.12.2 of lilypond-learning.pdf, sample of page 51 (section 3.2.1 I’m hearing Voices) tie connect properly. But, page 52 of version 2.13.11 tie cannot connect, also voice style does not continue. Is there any changes recent version? thank y

Re: Multi-Measure Rests: Adding to what gets printed?

rasAK wrote: In my orchestral parts, I would like Multi-Measure Rests to have both: (1) an integer representing the number of measures in the current MMR, centered above (default behavior) (2) a second text indicating which measures are included in the given MMR, in parentheses and centered BELOW

Re: RE; Re nesting curves getting closer

On Sun, Jan 24, 2010 at 12:39:51AM +0100, Gilles Sadowski wrote: > > > IMHO, perfect would be to *attach* a complete lilypond file, so that > > > people > > > > Well, IMO, it's better to have a short file in the body of the email. > > Because that way I can look at it and identify errors without

Re: RE; Re nesting curves getting closer

Gilles Sadowski wrote Saturday, January 23, 2010 11:39 PM >>> Gilles asked for an attachment I don't exactly know what to >>> attach so >>> I've attached the latest pdf output. >> >> What was wanted was the exact working code to get bad output, >> which you've >> included in the body of the

Re: RE; Re nesting curves getting closer

Hi. > >>> Gilles asked for an attachment I don't exactly know what to attach so > >>> I've attached the latest pdf output. > >> > >> What was wanted was the exact working code to get bad output, which you've > >> included in the body of the email. Perfect! > > > > IMHO, perfect would be to *att

Re: RE; Re nesting curves getting closer

On 1/23/10 7:07 AM, "Gilles Sadowski" wrote: > Hi. > >>> Gilles asked for an attachment I don't exactly know what to attach so >>> I've attached the latest pdf output. >> >> What was wanted was the exact working code to get bad output, which you've >> included in the body of the email. Perf

Multi-Measure Rests: Adding to what gets printed?

In my orchestral parts, I would like Multi-Measure Rests to have both: (1) an integer representing the number of measures in the current MMR, centered above (default behavior) (2) a second text indicating which measures are included in the given MMR, in parentheses and centered BELOW the MMR. (1)

[2.13.11-1] lilypond-book: duplicate filename but different contents of orginal file

Hi, masters! Please, help :-) Having run lilypond-book (linux, lilypond 2.13.11-1) i've got these warnings (note, all is well with lilypond 2.12.3-1): % ---8< [ ... latex's output ...] (./tmpRfG3TY.aux) ) No pages of output. Transcript written on

Re: RE; Re nesting curves getting closer

Hi Jay, > So could a snippet be created from this simple(r) example with that > instruction? What exactly is wrong with the [very simple] example in the docs? What could you not figure out by looking at that coe, or by

Re: RE; Re nesting curves getting closer

This is what I was looking for. So could a snippet be created from this simple(r) example with that instruction? The current example of nested slurs with the schenker example is way too complex for my (and maybe others?) poor brain. Thanks to everyone for your help. Jay On Sat, Jan 23, 2010 at 5:

Re: RE; Re nesting curves getting closer

Hi. > > Gilles asked for an attachment I don't exactly know what to attach so > > I've attached the latest pdf output. > > What was wanted was the exact working code to get bad output, which you've > included in the body of the email. Perfect! IMHO, perfect would be to *attach* a complete lilyp

Re: Nesting SLurs and phrases

{ \clef bass e''8-1^\markup {\bold "#8"} ^\( ^(f-2 e f) fis-3 ^(f-2 fis f\)) } { \clef bass e''8-1^\markup {\bold "#8"} _\( ^(f-2 e f) fis-3 ^(f-2 fis f\)) } { \clef bass e''8-1^\markup {\bold "#8"} ^\( _(f-2 e f) fis-3 _(f-2 fis f\)) } { \clef bass e''8-1^\markup {\bold "#8"} _\( _(f-2 e f

Re: RE; Re nesting curves getting closer

On 1/23/10 6:39 AM, "i...@soundand.com" wrote: > > > Gilles asked for an attachment I don't exactly know what to attach so > I've attached the latest pdf output. What was wanted was the exact working code to get bad output, which you've included in the body of the email. Perfect! > > This

RE; Re nesting curves getting closer

Gilles asked for an attachment I don't exactly know what to attach so I've attached the latest pdf output. This is close but nothing I've tried gets the 1st set of 8ths to be \slurDown \version "2.12.2" \header { title = "Nested Curves" } melody = \relative c' { \clef bass \

Re: Nesting SLurs and phrases

Kieren- I did read both and the lsr example and I just tried your ^ which I had tried before in a slightly different way. However nothing produces what I am trying to get. And your latest did not change my example the phrase still goes up. as do the slurs. As it did in the previous example

Re: Nesting SLurs and phrases

Hi Jay, > I copy/pasted your suggestion into the piece and the slurs/phrases all are up. > Explanation- > all of the notes are one phrase > each group of four 8ths are slurred. In the original the slurs are under the > 8ths and the phrase mark is above. Then raise it: music = { \slurDown e''

Re: Nesting SLurs and phrases

Hello. > I would have expected something like this to work > e''8-1^\markup {\bold "#8"} \slurDown > ( > \slurNeutral > (f-2 e f) fis-3 (f-2 fis f\)) ^^ This "\)" seems unbalanced. > but it won't compile. Gilles P.S. Please always give a self-contained example

Re: Nesting SLurs and phrases

Kieren- I copy/pasted your suggestion into the piece and the slurs/phrases all are up. Explanation- all of the notes are one phrase each group of four 8ths are slurred. In the original the slurs are under the 8ths and the phrase mark is above. Jay Quoting Kieren MacMillan : Hi Jay, I wo

Re: Nesting SLurs and phrases

Hi Jay, > I would have expected something like this to work > e''8-1^\markup {\bold "#8"} \slurDown > ( > \slurNeutral > (f-2 e f) fis-3 (f-2 fis f\)) > > but it won't compile. So I'm still not understanding that section or I'm > placing the \slur in the wrong place. Is this what you're trying

Re: Nesting SLurs and phrases

I would have expected something like this to work e''8-1^\markup {\bold "#8"} \slurDown ( \slurNeutral (f-2 e f) fis-3 (f-2 fis f\)) but it won't compile. So I'm still not understanding that section or I'm placing the \slur in the wrong place. Jay Quoting James Bailey : See section 5.4.

Re: Nesting SLurs and phrases

See section 5.4.2 in the notation reference, Direction and Placement On 23.01.2010, at 13:25, i...@soundand.com wrote: version 12.2 I would like to have the slurs in the following \slurDown and the long phrase Neutral or up but the LSR example is confusing as it uses many voices and I can'

Nesting SLurs and phrases

version 12.2 I would like to have the slurs in the following \slurDown and the long phrase Neutral or up but the LSR example is confusing as it uses many voices and I can't get it to usefully work for me. e''8-1^\markup {\bold "#8"} \ ((f-2 e f) fis-3 (f-2 fis f\)) The slurs and phrase mar

Re: [Lilypond] half-stopped horn

> Something like c2^"⊕" should do the trick; it works in my little test > sample (using 2.12.3) without needing any tweaking. In case it's necessary (or at least useful), the circled-plus character appears to be coded as 2295 in UTF-16. ___ lilypond-us

Re: [Lilypond] half-stopped horn

On Fri, 22 Jan 2010 21:54:44 -0200 Ezequiel Birman wrote: > Hello. > > I found your post in lylypond user list of 25 Sep 2004 regarding horn > notation and the half stopped glyph. > > I am facing the same problem. I've tried inserting an eps file with > the $\oplus$ glyph, but I can't get it ri