Re: doc suggestion
LM 5 hasn't been touched as part of GDP, and AFAIK nobody has any
spare time to look at it. The only possibility is that Trevor
might spend a few hours on it after he's done the first update for
NR 6.
(remember that Trevor is the *only* person working on LM 3-5 and
NR 3-6. Everybody else is still struggling with NR 1+2)
Cheers,
- Graham
On Wed, 30 Jul 2008 00:45:11 -0300
"Han-Wen Nienhuys" <[EMAIL PROTECTED]> wrote:
> there is a the following snippet in
>
> 5.1.4 Saving typing with variables and functions
>
> but the example doesn't show how the padText works. I think skylining
> handles this automaticallly. Maybe you should find a different
> example?
>
> padText =
> #(define-music-function (parser location padding) (number?)
>#{
> \once \override TextScript #'padding = #$padding
>#})
>
> \relative c''' {
>c4^"piu mosso" b a b
>\padText #1.8
>c4^"piu mosso" d e f
>\padText #2.6
>c4^"piu mosso" fis a g
> }
>
> --
> Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
doc suggestion
there is a the following snippet in
5.1.4 Saving typing with variables and functions
but the example doesn't show how the padText works. I think skylining
handles this automaticallly. Maybe you should find a different
example?
padText =
#(define-music-function (parser location padding) (number?)
#{
\once \override TextScript #'padding = #$padding
#})
\relative c''' {
c4^"piu mosso" b a b
\padText #1.8
c4^"piu mosso" d e f
\padText #2.6
c4^"piu mosso" fis a g
}
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 329 in lilypond: lyrics messed up when assigned to voices with different rhythms
Issue 329: lyrics messed up when assigned to voices with different rhythms
http://code.google.com/p/lilypond/issues/detail?id=329
Comment #4 by paconet.org:
This now behaves differently. Here is the same example, and another
added examples
that use lyricmode. With \lyrics the syllables appear left-aligned on
their notes,
with \lyricmode the syllables appear centered.
\version "2.11.53"
words = \lyrics{ ly rics }
wordstwo = \lyricmode{ ly ricmode }
<<
\new Voice = "sop" { c'1 }
\new Lyrics \lyricsto "sop" { \words }
\new Voice = "alt" { c'2 c' }
\new Lyrics \lyricsto "alt" { \words }
\new Voice = "soptwo" { c'1 }
\new Lyrics \lyricsto "soptwo" { \wordstwo }
\new Voice = "alttwo" { c'2 c' }
\new Lyrics \lyricsto "alttwo" { \wordstwo }
My questions are,
what is \lyrics used for?
does it create a new context, or not?
is \lyrics deprecated?
is the comment #2 still valid, ie does "the original "\new Lyrics"
remains empty"?
anyway, the issue is either fixed or easily workaroundable.
Attachments:
notabug.preview.png 5.9 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 653 in lilypond: \override inconsistency with ties in a polyphonic situation
Han-Wen, you wrote:
Doing overrides on individual ties is not supported like this, exactly
because there
is no way to select them. Try \tweak,
\new Voice <<
{ c'' }
{ e' }
This works fine with #'control-points too. Thanks.
(changing status so someone will update lsr/the manual.)
I've made a note to do this in NR 5
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Improvement request: Tuplet numbers and staff lines collision avoidance (bounty)
2008/7/28 Chris Snyder <[EMAIL PROTECTED]>: > After looking at more published scores, as well as looking at a printed copy > of the current LilyPond default (the space between the middle of the three > and the staff line was less pronounced on-screen), I'm beginning to concur. Yes, this is something you have to know regarding LilyPond: its output is *visibly* optimized for printing rather than on-screen reading. Whenever you find that the PDF score looks odd (and assuming you're lucky enough to own a printer that works), it's generally a good habit to print it to check it out. Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Improvement request: Tuplet numbers and staff lines collision avoidance (bounty)
Francisco Vila wrote: "Default" is better for me. Maybe a scan from a good printed example would help on supporting a version or another After looking at more published scores, as well as looking at a printed copy of the current LilyPond default (the space between the middle of the three and the staff line was less pronounced on-screen), I'm beginning to concur. Feel free to disregard my request. Thanks for your responses. -Chris ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: small notes etc.
2008/7/25 David Biddiscombe <[EMAIL PROTECTED]>:
Greetings,
> Below is an input file representing small parts of a file for a four-verse
> song.
May I invite you to have a look at the two following pages for your
future reports?
http://lilypond.org/web/devel/participating/bugs
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Minimal-examples
> The rhythm of the fourth verse, which differs from that of the other verses,
> is
> shown in the .pdf file by the small notes above the top staff, except that the
> two small quavers must be (a) beamed, (b) with a slur/tie **above** the beam,
> and (c) in line with the other three small notes. (The markups are attached to
> the **alto** input to avoid complications over stem directions.) I've tried a
> number of markup variations, but can't get the necessary output.
The markup \note function is only meant for printing separate notes
(it doesn't support beams nor ties). You're looking for the markup
\score function, as in:
\relative {
d2^\markup {
\score {
\new Staff \with {
fontSize = #-3
\override StaffSymbol #'line-count = #0
\remove "Clef_engraver"
\remove "Time_signature_engraver"
\remove "Bar_engraver"
\consists "Pitch_squash_engraver"
squashedPosition = #0
}
{ c2. c4 c c8( c) }
\layout {}
}
}
}
If you want these notes to be horizontally synchronized with the main
score, you will have to use an invisible staff (like the one in this
markup) above your ChoirStaff.
> Also, for some reason, the first alto crotchet f is not offset from the
> soprano
> g, although in every similar case in the the complete song (as for example in
> the last chord in this extract) the output is correct.
Beware of your use of simultaneous polyphonic constructs. You're
placing two Voices on a Staff (which is fine), *but* in your altoMusic
variable you used << >>, which in turn instantiates two voices
(defaulting to voiceOne and voiceTwo). Hence the mess with the first
f.
Your hack with invisible notes shouldn't be needed anymore.
> Lastly, is it possible to make bar lines (of all types) thinner? Line 10 of
> the
> file below is an attempt (but doesn't work).
The correct property is #'hair-thickness, and the BarLine objects live
in the Staff context (not Voice).
> PS: I'm using LilyPond version 2.10.33, notwithstanding email advice (from
> Graham Percival on 4 and 6 Apr 2008) to use a 2.11 version, because Mats
> Bengtsson in an email of 19 Feb 2008 on a previous enquiry advised me to use
> the
> latest **stable** version'. Also I find that switching versions involves a
> great
> deal of work, over and above using convert-ly, in making older files work.
For the kind of music you appear to write, the conversion should be
straight-forward... if needed at all (the example you sent, for
instance, is fully compatible with 2.11).
Cheers,
V. Villenave
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \set chordChanges troubles
Thank You very much for the explanation and solution. I didn't undestand that from the user-manual. (But still I'm surprised, that at least one of the \set in my file was interpreted but not the second one...) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: spacing, version 2.10 and 2.11
2008/7/26 <[EMAIL PROTECTED]>:
> This files compiles on the stable version but hangs on the 2.11. (i.e it
> keeps compiling).
> Is there a reason and how to by-pass it ?
Hi Karim,
stupid question: have you tried to let LilyPond work for more than
twelve hours without doing anything else with your computer? We need
to know if it's caught in a infinite loop, or if it just takes a
veeery long time to process your file...
Other than that, have you tried to use
\paper {
#(define page-breaking ly:minimal-breaking)
}
?
(this divides the compilation time by ten when I compile my opera)
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \set chordChanges troubles
2008/7/29 Werner <[EMAIL PROTECTED]>:
Hi Werner, thanks for the report (still a bit long indeed; but at
least I can see why you're confused).
> % if put chordChanges above ChordNames,
> % symbols are printed below staff and in every bar
> % (also if there is no change) ‒ strange
> % second chordChanges doesn't work at all
I think you've misunderstood how to use \set.
It has to be used *inside* the relevant context; if you use it
*outside* ChordNames, it will be placed in the StaffGroup context and
therefore it will be useless.
So, you have several solutions:
\new ChordNames { \set chordChanges = ##t \Harmonien }
or
\new ChordNames \with { chordChanges = ##t } \Harmonien
or (if you want to set it for the whole score)
\layout {
\context {
\ChordNames
chordChanges = ##t
}
}
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \set chordChanges troubles
This is not minimal. A minimal example of a bug like this would
probably be about 6 lines.
Cheers,
- Graham
On Tue, 29 Jul 2008 13:00:09 + (UTC)
Werner <[EMAIL PROTECTED]> wrote:
> % So I send a "minimal" example.
> % Again, use the whole message-text as ly-file!
>
> \version "2.11.54"
>
> Erste = \relative c' {
> \clef G
> \key es
> \major
> \time 4/4
> c1 | r | c |
> }
>
> Harmonien = {
> \chordmode {c1:m7 c:m7 c:m7 }
> }
>
>
> Vierte = \relative c' {
> \clef G
> \key es
> \major
> \time 4/4
> r1 |c1 | r |
> }
>
>
> \score {
> \new StaffGroup
> <<
> \new ChordNames \Harmonien
> \new Staff \Erste
> \set chordChanges = ##t
>
> \new ChordNames \transpose c d \Harmonien
> \new Staff \transpose c d \Vierte
> \set chordChanges = ##t
> % if put chordChanges above ChordNames,
> % symbols are printed below staff and in every bar
> % (also if there is no change) ___ strange
> % second chordChanges doesn't work at all
> >>
>
> \layout {
> indent = #0
> \context { \Score \remove "Bar_number_engraver" }
> }
> }
>
>
>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \set chordChanges troubles
% So I send a "minimal" example.
% Again, use the whole message-text as ly-file!
\version "2.11.54"
Erste = \relative c' {
\clef G
\key es
\major
\time 4/4
c1 | r | c |
}
Harmonien = {
\chordmode {c1:m7 c:m7 c:m7 }
}
Vierte = \relative c' {
\clef G
\key es
\major
\time 4/4
r1 |c1 | r |
}
\score {
\new StaffGroup
<<
\new ChordNames \Harmonien
\new Staff \Erste
\set chordChanges = ##t
\new ChordNames \transpose c d \Harmonien
\new Staff \transpose c d \Vierte
\set chordChanges = ##t
% if put chordChanges above ChordNames,
% symbols are printed below staff and in every bar
% (also if there is no change) ‒ strange
% second chordChanges doesn't work at all
>>
\layout {
indent = #0
\context { \Score \remove "Bar_number_engraver" }
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
