Lilypond score

2010-02-27 Thread René PRUAL
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

 



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Marking cross-staff unisons

2010-02-27 Thread David Kastrup
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.
>
> That's a documentation bug really.  The code says it only produces a
> bracket to the left of the notes, though it would be easy to fix.

Sounds like less work in the long run to treat it like a code bug rather
than document this irregularity and field the storm of bug reports.

-- 
David Kastrup



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Any news on LilyPond 2.14 release date?

2010-02-27 Thread Gerard McConnell
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 absolutely 
anything in the score in any way you want.

Which brings me to my two questions -
1.  Is there any significant downside (print quality?)
to using Inkscape to edit LilyPond files? 
2. When is LilyPond 2.14 likely to be released?

Gerard


  - Original Message - 
  From: musicologyman 
  To: lilypond-user@gnu.org 
  Sent: Saturday, February 27, 2010 5:20 AM
  Subject: double slurs within beamed notes


  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: 

   
  I've tried all sorts of things: hidden notes shifted as appropriate in order 
to position the slurs and ties in the desired location, hidden notes within a 
context that has the Collision_engraver removed, and so on. I've even 
considered manually (and tediously!) setting the control points for each slur. 
But there must be a better way! 

  Richard Wattenbarger 
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Strange message with autochange

2010-02-27 Thread Xavier Scheuer
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 alternatives I have for
> this hypothetical 500-bar piece is to either put up with those 50
> awkward staff changes, or rewrite the piece so that every single one
> of the staff changes in those 500 bars is done by hand? Pardon my
> frankness, but what a bloody stupid [insert nasty word here] system.

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.


> No, it's not. Not completely. With the \change in, the output has a
> semiquaver rest in the bottom staff, a b, e, g, and f sharp in the
> top staff, and the stems point up.
>
> Without the \change, the output has a semiquaver rest in the bottom
> staff, a b in the bottom staff, an e, g and f sharp in the top staff,
> and the stems point down (and the beaming looks ridiculous as a
> result). What I want here is for both the rest and the b to be on the
> top clef and for the beaming to look not ridiculous (I can do that
> myself, it's the first part I need help with). However, putting the
> \change in front of the rest gives the same output as if the \change
> weren't there, and using x16\rest where x is a note doesn't seem to
> put it in the right place either; for some reason Lilypond skips
> right over most of the top staff.

Indeed, looks like a bug.

Xavier

--
Xavier Scheuer 


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Any news on LilyPond 2.14 release date?

2010-02-27 Thread James Bailey


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 
+Summary&sort=&x=type&y=priority&cells=tiles&mode=grid
You can see all of the currently open issues. Graham doesn't want to  
release the program with anything in the critical row.___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Dynamics and Lyrics don't mix

2010-02-27 Thread Roman Stawski
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 cascade of warnings

warning: staff-affinities should only decrease

Can anyone translate this into English ? and/or tell me how to do to get
shot of them?

Inversing the dynamics and lyrics gets rid of the warnings. But doesn't
give me the output I want.


Thanks for any pointers

Roman




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Lilypond score

2010-02-27 Thread Valentin Villenave
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 list:
http://lists.gnu.org/mailman/listinfo/lilypond-user-fr

Regards,
V. Villenave.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Ambitus

2010-02-27 Thread David Kastrup
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 that the storage of the pitches/key signature is
> simpler.  I think combining my original approach of a music function
> with some extra listener code is better, since it allows scores in a
> book to have separate ambitus.

But wouldn't scores in a book use separate engraver instantiations and
have separate ambitus for that reason?

> \version "2.13.14"
>
> \header {  }
>
> ambitus =
> #(define-music-function (parser location music) (ly:music?)
>
>(define (add-stream-listener global listener . types)
>  (apply ly:add-listener
> (cons* listener (ly:context-events-below global) types))
>  global)
>
>(define (process-event event)
>  (case (ly:event-property event 'class)
>((note-event)
> (set! pitches (cons (ly:event-property event 'pitch) pitches)))
>((key-change-event)
> (and (null? key-list)
>  (set! key-list (ly:event-property event 'pitch-alist
>((Finish)
> (set! pitches (stable-sort pitches ly:pitch (if $defaultheader
> (module-define! $defaultheader 'ambitus
> (ambitus-markup key-list pitches))

Uh, what's with the $defaultheader here?

>(define (ambitus-markup key pitches)
>  (let* ((music (make-sequential-music
> (list (make-time-signature-set 2 4)
>   (make-grob-property-set 'TimeSignature
>   'stencil #f)
>
>(ly:parser-define! parser 'pitches '())
>(ly:parser-define! parser 'key-list '())

What does that do?  Why per-parser?

>(let* ((global (ly:make-global-context $defaultlayout))
>   (listener (ly:make-listener process-event))
>   (global-disp (ly:context-events-below global)))
>
>  (ly:connect-dispatchers (ly:make-dispatcher) global-disp)
>  (add-stream-listener global listener 'note-event 'key-change-event 
> 'Finish)
>  (ly:interpret-music-expression music global)
>  music))

What does this do?  Route the music expression through a parser with a
simple listener, then regurgitate it for the outer context?

> \new Staff \ambitus \relative c'' {
>   \key g \major
>   g8 a b c d e fis g
>   a1
> }

It would seem that this approach would not work when you want, say, an
ambitus per Voice, and the input is not continuous, but repeatedly
switches between contexts.

Then you don't have the whole music available as one music expression.

But frankly: I don't get half of what you are doing here, so I may well
be mistaken.

-- 
David Kastrup



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Vertical dashed line conecting notes

2010-02-27 Thread Caio Barros
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 are some problems:
- the line doesn't draw itself at the middle of the notehead
- the botton staff moves itself lower so the line does not colide. (I want
it do colide!)
- I don't know how to draw a dashed line with the \draw-line command ;)

Is there a way to tweak this, or maybe is better to use another code?

Thank you
Caio Barros
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Dynamics and Lyrics don't mix

2010-02-27 Thread Roman Stawski
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-affinity = #DOWN
  } { s4\p s\< s\! s\mf }
  \new Lyrics \with {
\override VerticalAxisGroup #'staff-affinity = #DOWN
  } { \lyricsto "a" \lyricmode { a b c d }}
>>
-

My only problem now is to increase the spacing between the dynamics and
the lyrics. Ah well, back to the VerticalAxisGroup documentation...

regards

Roman




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Vertical dashed line conecting notes

2010-02-27 Thread Kieren MacMillan
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 helps!
Kieren.

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: double slurs within beamed notes

2010-02-27 Thread Bernhard Ott


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 down:

I've tried all sorts of things: hidden notes shifted as appropriate in
order to position the slurs and ties in the desired location, hidden
notes within a context that has the Collision_engraver removed, and so
on. I've even considered manually (and tediously!) setting the control
points for each slur. But there must be a better way!

Here is my LilyPond code. Any assistance will be greatly appreciated!!!

Try using the tilde symbol for notes of same pitch - you definitely want 
ties there ;-)


http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Writing-rhythms#Ties

HTH, Bernhard

P.S.: this is my second attempt - carboncopying to the list wasn't 
successful...



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Staff "reappearance" callback?

2010-02-27 Thread Kieren MacMillan
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 
features:
1. Make the InstrumentName take the long name each time a Frenched staff 
reappears.
2. Make the TimeSignature appear each time a Frenched staff reappears.

Thanks,
Kieren.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Lilypond score

2010-02-27 Thread Xavier Scheuer
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 interested by
Valentin's video tutorials for LilyPond (in French too) :
http://valentin.villenave.info/-Lilypond-

Cheers,
Xavier

--
Xavier Scheuer 


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: double slurs within beamed notes

2010-02-27 Thread Colin Campbell




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:
  
  
  I've tried all sorts of things: hidden notes shifted as
appropriate in order to position the slurs and ties in the desired
location, hidden notes within a context that has the Collision_engraver
removed, and so on. I've even considered manually (and tediously!)
setting the control points for each slur. But there must be a better
way!
  
Here is my LilyPond code. Any assistance will be greatly appreciated!!!
   
\version "2.12.2" 
 
mainVoice = \new Voice { 
  \relative c'' {  
\slurDown 
\set doubleSlurs = ##t 
#(override-auto-beam-setting '(end * * * *) 1 8) 
#(override-auto-beam-setting '(end * * * *) 3 8) 
#(override-auto-beam-setting '(end * * * *) 4 8) 
\stemUp 8 ()   () \stemDown    
() \stemUp  () 8  
()  () \stemDown    
()  ()  () 
#(revert-auto-beam-setting '(end * * * *) 1 8) 
#(revert-auto-beam-setting '(end * * * *) 3 8) 
#(revert-auto-beam-setting '(end * * * *) 4 8) 
  } 
} 
 
notes = { 
  \clef treble 
  \key g \major 
  \time 2/4 
  s8 * 3  
  \mainVoice 
} 
 
 
\score { 
  \new Staff  
  { 
\notes 
  } 
}
  
Thanks in advance for your help!
  
  
Richard Wattenbarger

You might find some ideas in the Notation Reference section 1.2.1 under
Ties. There is a snippet at the end which shows the use of the
tie-configuratoin property of TieColumn. Essentially, it allows you to
place your ties explicitly.

HTH
Colin


-- 
I stay cool and dig all jive, That's the way I stay alive. 
My motto, as I live and learn, is "Dig and be dug in return."
   - Langston Hughes





___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 break, including staff reappearance and page break.

If I find the right sort of callbacks suggested by Kieren (on my own, or
because one of you points me to them), I might try to package them a bit
in some handy functions.

Cheers,

Mike O'D.
> --
>
> Message: 5
> Date: Sat, 27 Feb 2010 11:25:25 -0500
> From: Kieren MacMillan 
> Subject: Staff "reappearance" callback?
> To: Lilypond-User Mailing List 
> Message-ID: 
> Content-Type: text/plain; charset=us-ascii
>
> 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 
> features:
> 1. Make the InstrumentName take the long name each time a Frenched staff 
> reappears.
> 2. Make the TimeSignature appear each time a Frenched staff reappears.
>
> Thanks,
> Kieren.
>
>   


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 should list all possibilities:

1. before line break
2. after line break
3. before page break
4. after page break
5. before staff reappearance
6. after staff reappearance
??

Cheers,
Kieren.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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, looks like a bug.

So where can I report this?
-- 
View this message in context: 
http://old.nabble.com/Strange-message-with-autochange-tp27710824p27729707.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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) between the note heads. How can I
accomplish this?


http://old.nabble.com/file/p27730345/output.png 


Here is the relevant excerpt of my revised code:


\tieUp
\slurDown
\stemUp 8 ()   ()
\stemDown   
() \stemUp  () 8 
()  () \stemDown   
() \redSlur  () \tieDown \slurUp
 ()
\syncBeamsOff


Again, thanks much.

musicologyman

-- 
View this message in context: 
http://old.nabble.com/double-slurs-within-beamed-notes-tp27725943p27730345.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 
 ()
}

\score { \stuff }

Notice I also introduced the \partial (pickup), to accurately represent the 
music.

Hope this helps!
Kieren.

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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:
> 
>   http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs
> 
> -Patrick
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Strange-message-with-autochange-tp27710824p27730746.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 ever use the autochanges, so I don't really know  
what the expected outpus should be.


On 27.02.2010, at 21:32, George_ wrote:



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:

  http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs

-Patrick


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




--
View this message in context: http://old.nabble.com/Strange-message- 
with-autochange-tp27710824p27730746.html
Sent from the Gnu - Lilypond - User mailing list archive at  
Nabble.com.




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 g \major
   \autochange \relative c' {
  b'16*1/2\rest
  s16*1/2
  \change Staff = "up"
  b,16 e g fis
   }
}
 }
 \new Staff = "down" {
\key g \major
\clef bass
 }
  >>
   }
>>


On 27.02.2010, at 22:21, James Bailey wrote:

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 ever use the autochanges, so I don't really  
know what the expected outpus should be.


On 27.02.2010, at 21:32, George_ wrote:



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:

  http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs

-Patrick


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




--
View this message in context: http://old.nabble.com/Strange- 
message-with-autochange-tp27710824p27730746.html
Sent from the Gnu - Lilypond - User mailing list archive at  
Nabble.com.




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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" {
>   \autochange \relative c' {
>   \change Staff = "up" r16 b e g 
> \change Staff = "down" fis c b a g
>   }
>   }
>   >>
>   }
> 
> 

\change Staff = "" doesn't seem to apply to rests, even when in written
as b16\rest instead of just r16. I'm not sure what other information should
be put on, there's the rest of this thread, or just ask me if you need more
info.

Thanks

George
-- 
View this message in context: 
http://old.nabble.com/Strange-message-with-autochange-tp27710824p27731384.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 an accent.

Cheers,
Kieren.

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 break, including staff reappearance and page break.
> 
> Excellent point! We should list all possibilities:
> 
> 1. before line break
> 2. after line break
> 3. before page break
> 4. after page break
> 5. before staff reappearance
> 6. after staff reappearance

7. Before staff disappearance (in harakiri staves)

Cheers,
Reinhold
-- 
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 .el files to site-lisp inside Emacs.app.   
So, did that and lilypond-mode is automatically loaded when I open  
a .ly file.  Yay.  Everything looks fine, syntax coloring works, etc.


However, I can't compile.  C-c C-l results in "Compilation exited  
abnormally with code 127" (paraphrasing from memory here; there's  
also a /bin/bash complaint too).  Interestingly C-c C-s launches the  
designated PDF viewer (Preview) just fine, if I open a .ly file that  
has already been compiled and has a rendered PDF already.


This is not a new issue, when I tried to set up Carbon Emacs about a  
year ago I had the same problem... but I can't remember the fix and  
hence that is the "dumb" part of my question. I haven't been able to  
track the fix down in the archives of the lilypond-user list, which  
is where I got the fix last year IIRC.  Can anybody point me in the  
right direction?


BTW, my copy of Carbon Emacs with lilypond-mode still works fine, so  
that's the easy workaround.  This also suggests to me that it is not  
a problem in my .emacs file since that is the same for both Emacsen.   
I have some vague recollection of editing a particular file, just not  
*which* file.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 that for your 500 page fugue that  
sucks, but it's as easy as defining a variable,

csu = \change Staff = "up",
and then using that variable when you want to have a staff change, \csu.
On 27.02.2010, at 23:08, George_ wrote:



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" {
\autochange \relative c' {
		\change Staff = "up" r16 b e g \change Staff = "down" fis c  
b a g

}
}
>>
}




\change Staff = "" doesn't seem to apply to rests, even when in  
written
as b16\rest instead of just r16. I'm not sure what other  
information should
be put on, there's the rest of this thread, or just ask me if you  
need more

info.

Thanks

George
--
View this message in context: http://old.nabble.com/Strange-message- 
with-autochange-tp27710824p27731384.html
Sent from the Gnu - Lilypond - User mailing list archive at  
Nabble.com.




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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  
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 .el files to site-lisp inside Emacs.app.   
So, did that and lilypond-mode is automatically loaded when I open  
a .ly file.  Yay.  Everything looks fine, syntax coloring works, etc.


However, I can't compile.  C-c C-l results in "Compilation exited  
abnormally with code 127" (paraphrasing from memory here; there's  
also a /bin/bash complaint too).  Interestingly C-c C-s launches  
the designated PDF viewer (Preview) just fine, if I open a .ly file  
that has already been compiled and has a rendered PDF already.


This is not a new issue, when I tried to set up Carbon Emacs about  
a year ago I had the same problem... but I can't remember the fix  
and hence that is the "dumb" part of my question. I haven't been  
able to track the fix down in the archives of the lilypond-user  
list, which is where I got the fix last year IIRC.  Can anybody  
point me in the right direction?


BTW, my copy of Carbon Emacs with lilypond-mode still works fine,  
so that's the easy workaround.  This also suggests to me that it is  
not a problem in my .emacs file since that is the same for both  
Emacsen.  I have some vague recollection of editing a particular  
file, just not *which* file.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


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 so complaints from one character!
> 
> Any chance to add to the warning message a few words like
> 
>   This error most likely happens if you are using the wrong input
>   encoding.  Are you using UTF-8 encoding for your input file?
> 
> IMHO there are too many questions on this list w.r.t. this warning
> message.

I neglected to mention that in recent 2.13 versions, the warning
messages for invalid character encoding look like this:

  (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to 
pango_layout_set_text()

These warnings are generated by Pango.

Is this an improvement?


Thanks,
Patrick


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user