Lilypond score

I have just unloaded lilypond and I did not succeed to transform the writed message in a musical score. May be I did not unload correctly? I have too unloaded "eDit" whith "lilypond tool", whithout success. Do I need an authorization? Thank you for your response René Prual __

Re: Marking cross-staff unisons

Neil Puttock writes: > On 26 February 2010 21:04, Robin Bannister wrote: >> Neil Puttock wrote: >>> >>> \override ChoirStaff.Arpeggio #'stencil = #ly:arpeggio::brew-chord-bracket >> >> I wanted to do pretty much the same last week and ran into a familiar bug >> which I haven't reported yet. > >

Any news on LilyPond 2.14 release date?

I saw musicologyman's post about "double slurs within beamed notes" and didn't quite have the answer to his question, but realized that the edit he wants to perform is exactly the sort of thing that is simple to do when you use LilyPond's SVG output. Open the SVG file in Inkscape0.47 and edit a

Re: Strange message with autochange

On 27 February 2010 06:09, George_ wrote: > So say I have a piece that is five hundred bars long. Say I use > autochange to get Lilypond to automatically change staff for the > music. Say that there are 50 staff changes that are particularly > awkward. You are telling me that the only alternative

Re: Any news on LilyPond 2.14 release date?

On 27.02.2010, at 12:19, Gerard McConnell wrote: 2. When is LilyPond 2.14 likely to be released? I can't say when it is going to be released, but I know when it isn't. ^.^ If you go to http://code.google.com/p/lilypond/issues/list? can=2&q=&colspec=ID+Type+Status+Priority+Stars+Owner +S

Dynamics and Lyrics don't mix

Hi folks When I build the snippet - \version "2.13.11" \paper{ ragged-right = ##t } << \new Staff \new Voice = "a" \relative c'' { a b c d } \new Dynamics { s4\p s\< s\! s\mf } \new Lyrics { \lyricsto "a" \lyricmode { a b c d }} >> - the output is as expected, but I get a whole ca

Re: Lilypond score

On Sat, Feb 27, 2010 at 9:12 AM, René PRUAL wrote: > I have just unloaded lilypond and I did not succeed to transform the writed > message in a musical score. May be I did not unload correctly? Greetings, if you speak French, you may be interested in subscribing to our French-speaking mailing li

Re: Ambitus

Neil Puttock writes: > On 5 February 2010 00:18, Neil Puttock wrote: > >> Yes (see attached file).  I had to move the markup outside the >> 'finalize method though, since it wouldn't evaluate it directly. > > I've come to the conclusion using an engraver is a waste of time; its > only benefit is

Vertical dashed line conecting notes

Hi, I'm writing a composition with two unmeasured staffs and I want to draw a vertical dashed line that indicates when the notes sound together. I've tried something like that: \version "2.12.1" \relative c' { << { c_\markup { \draw-line #'(0 . 9) } } { a } >> } but as you can see there ar

Dynamics and Lyrics don't mix

After some playing around, I found that the following gets rid of the warnings. It does seem a little messy, though. - \version "2.13.11" \paper{ ragged-right = ##t } << \new Staff \new Voice = "a" \relative c'' { a b c d } \new Dynamics \with { \override VerticalAxisGroup #'staff-aff

Re: Vertical dashed line conecting notes

Hi Caio Barros: 1. Try using grid lines: 2. Use cross-staff arpeggios, and modify the shape and offset. [See recent list threads for info.] Hope this h

Re: double slurs within beamed notes

On 02/27/2010 06:20 AM, musicologyman wrote: I've been struggling to replicate the placement of slurs and ties in the following original: Problem is, I can't get the slurs and ties to appear _within_ the beamed note. They always appear above the beam if the stem is up and below if the stem is d

Staff "reappearance" callback?

Hi all, Michael's question about instrument names got me wondering... Is there an easy way to have a callback for any grob (e.g. TimeSignature) so that it knows whether or not its Staff context was alive in the previous system? If so, this would have lots of good uses, including Michael's two

Re: Lilypond score

On 27 February 2010 15:53, Valentin Villenave wrote: > Greetings, > > if you speak French, you may be interested in subscribing to our > French-speaking mailing list: > http://lists.gnu.org/mailman/listinfo/lilypond-user-fr Agree. ;-D And if you are a beginner with LilyPond you may also be int

Re: double slurs within beamed notes

musicologyman wrote: I've been struggling to replicate the placement of slurs and ties in the following original: Problem is, I can't get the slurs and ties to appear _within_ the beamed note. They always appear above the beam if the stem is up and below if the stem is down:

Re: Staff "reappearance" callback?

While we're in speculative mode, I'll mention a principle that might affect a future release: It looks like break-related items of all sorts, including "break-visibility", should have more than the 3 categories of before break, after break, and no break. Then might should distinguish levels of bre

Re: Staff "reappearance" callback?

Hi Michael, > It looks like break-related items of all sorts, including > "break-visibility", should have more than the 3 categories of before > break, after break, and no break. Then might should distinguish levels > of break, including staff reappearance and page break. Excellent point! We shou

Re: Strange message with autochange

>Actually I'm not a pianist, nor some kind of "LilyPond-genius", so my >answer was only based on my knowledge of LilyPond (little with >keyboard-related stuffs) and also based on your minimal code, which had >only one (zero) staff change... > >Pardon my bloody stupid answer. I'm sorry. >Indeed,

Re: double slurs within beamed notes

The tip on using the tie was helpful. Thanks, much! (I'd tried it before, but for some reason, the tie didn't work. Or maybe I'm caught not seeing the forest because of the trees) I still have one issue to work out: I'd like to position the slur from a to b (see the red box & red slur below

Re: Strange message with autochange

On 2010-02-27, George_ wrote: > > So where can I report this? If you run LilyPond without arguments, you'll see the bug report URL listed at the very bottom: http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs -Patrick ___ lilypond-u

Re: double slurs within beamed notes

Hi, You might want to do something like this: \version "2.12.1" stuff = \relative c'' { \time 2/4 \tieUp \slurDown \partial 8 \stemUp 8( | ) [( ]) \stemDown ( | ) \stemUp [( ]) 8( | ) [( ]) \stemDown ( | ) [-\tweak #'extra-offset #'(0.3 . 3) ( ]) \tieDown \slurUp () } \sco

Re: Strange message with autochange

Is there any particular format I need to conform to for bug reports, or do I just write 'freestyle'? Patrick McCarty-3 wrote: > > On 2010-02-27, George_ wrote: >> >> So where can I report this? > > If you run LilyPond without arguments, you'll see the bug report URL > listed at the very bottom

Re: Strange message with autochange

On Sat, Feb 27, 2010 at 12:32 PM, George_ wrote: > > Is there any particular format I need to conform to for bug reports, or do I > just write 'freestyle'? Yes, see this page for some hints: http://lilypond.org/doc/v2.13/Documentation/web/bug-reports Thanks, Patrick __

Re: Strange message with autochange

I can add the bug to the tracker, but can you make a short snippet (http://lilypond.org/doc/v2.13/Documentation/web/tiny-examples#Tiny- examples) that demonstrates the problem. and then a sentence or two that explains what the behavior should be. Then I'll know what to add, 'cause I don't ev

Re: Strange message with autochange

Again, I don't know what the expected behavior of autochange is, it seems to be a pretty simple tool, however you may be able to achieve the desired result with a spacer rest. << \new PianoStaff { << \new Staff = "up" { \new Voice = "melOne" { \key

Re: double slurs within beamed notes

Thanks! That did the trick! One question: what does the en-dash before the \tweak command mean/do? --RW -- View this message in context: http://old.nabble.com/double-slurs-within-beamed-notes-tp27725943p27731275.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. __

Re: Strange message with autochange

Okay, I've put the snippet in the quote. Basically the first change shows the \change not working; the second one shows the \change working. Regardless, both produce errors in the log. > \version "2.13.7" > > \new PianoStaff { > << > \new Staff = "up" { >

Re: double slurs within beamed notes

Hi RW, > Thanks! That did the trick! Great. > One question: what does the en-dash before the \tweak command mean/do? Shouldn't be an en-dash; just a hyphen. Anyway, it's required to "attach" or "anchor" the \tweak to the moment (note) it belongs to, just like g-> is used to attach/anchor

Re: Staff "reappearance" callback?

Am Samstag, 27. Februar 2010 18:45:26 schrieb Kieren MacMillan: > Hi Michael, > > > It looks like break-related items of all sorts, including > > "break-visibility", should have more than the 3 categories of before > > break, after break, and no break. Then might should distinguish levels > > of b

Dumb Emacs lilypond-mode question

I've had lilypond-mode working in Emacs for a year now, using Carbon Emacs on Mac OS X 10.4. Works great, kuds to whomever wrote the mode. I just built the latest Emacs 23.1 to give it a try; it initially didn't work with Lilypond at all until I remembered I had to add the lilypond-mode .

Re: Strange message with autochange

The only problem I have with this is that I don't think that manual staff changes are supposed to work with autochange. I could force things to work, but the known issues and warnings says that if you want high quality output, staff switches should be specified manually. And yeah, I realize

Re: Dumb Emacs lilypond-mode question

If I remember correctly, GUI apps don't by default load your $PATH, there's a trick somewhere to get them to do it, I just don't remember where or how. But that may be what you need. On 28.02.2010, at 06:46, Tim McNamara wrote: I've had lilypond-mode working in Emacs for a year now, using

Re: "Programming error" message

On 2010-02-27, Werner LEMBERG wrote: > > >> I don't see any non-ASCII characters in my file.  Oh, I take that back now > >> that I scrutinize closer... I have © in the input file.  Well, that's easy > >> to get rid of.  And doing so eliminates the glyph complaint from Lilypond. > >>  Wow, eight or