Feathered beams: More than one beam at the end?
Another question -- is there any way to make the narrow end of a feathered beam
show more than one beam? That is, as far as I can see, the beams taper down to
one point (as in this code snip) but the documentation doesn't show any way to
specify the number of beams you want at the end.
\version 2.14.2
\include english.ly
% \override Beam #'grow-direction = #LEFT
% % revert to non-feathered beams
% \override Beam #'grow-direction = #'()
\relative c'' {
\key d \major
\numericTimeSignature
r16
\override Beam #'grow-direction = #LEFT
\scaleDurations #'(2 . 1) { e32 [ e e e e e e ] }
\override Beam #'grow-direction = #'()
e16 e e4.
}
In this example, I'd like to indicate that the note duration at the end of the
feathered bit should be a 16th note (and the performed rhythm would merge
smoothly with the metered notes following). As shown, it kind of looks like the
notes should slow down to roughly an eighth note, and then the next 16th notes
would be played faster. Not the intent.
Writing by hand, I might start the feathered part with 32nd notes and merge two
of the beams down into one, leaving 16th notes at the end.
If it's impossible, I'll work around it with some explanatory text. Maybe a
viable feature request?
Thanks,
James
--
James Harkins /// dewdrop world
jamshar...@dewdrop-world.net
http://www.dewdrop-world.net
Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal. -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tupletFullLength clashes with barline
On 03/10/2012 09:55 PM, Patrick Karl wrote:
On Mar 10, 2012, at 1:35 PM, Jamespkx1...@gmail.com wrote:
Message: 6
Date: Sat, 10 Mar 2012 19:34:40 +
From: Jamespkx1...@gmail.com
To: Peter O'Dohertym...@peterodoherty.net
Cc: lilypond-user@gnu.org
Subject: Re: tupletFullLength clashes with barline
Message-ID:
CA+T3wFkZtC-A0k6W1zjy3q2U=dtu8+qP+AWSf9rf=7orexq...@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Hello,
On 10 March 2012 08:18, Peter O'Dohertym...@peterodoherty.net wrote:
Hi list,
tupletFullLength = ##t
causes the right hand part of the tuplet bracket to clash with the barline.
This only happens with a barline at the end of a line.
Is there a way to avoid this?
Tiny example and the version you are using might help us.
Here's one that illustrates what he's talking about:
\version 2.14.2
music = \relative g' {
\repeat unfold 3 { \times 2/3 { f8 g a f g a f g a f g a} }
\break
\set tupletFullLength = ##t
\repeat unfold 3 { \times 2/3 { g8 a b g a b g a b g a b} }
}
\score { \new Staff { \music } }
Note that in the 1st two measures of the 2nd system the tuple bracket extends
slightly past the last note, but in the last measure in the 2nd system the
tuple bracket extends all the way to the bar line.
Regards,
Pat Karl
Thanks for the example Pat. That illustrates it well. This examples
shows how bad it looks in a piano stave:
\version 2.12.3
\include english.ly
upper = {
\clef treble
\time 4/8
\times 4/6 { c'8 c'8 c'8 c'8 c'8 c'8 } |
\times 4/6 { c'8 c'8 c'8 c'8 c'8 c'8 } |
\times 4/6 { c'8 c'8 c'8 c'8 c'8 c'8 } |
\break
\times 4/6 { c'8 c'8 c'8 c'8 c'8 c'8 } |
}
lower = {
\clef bass
\times 4/6 { c8 c8 c8 c8 c8 c8 } |
\times 4/6 { c8 c8 c8 c8 c8 c8 } |
\times 4/6 { c8 c8 c8 c8 c8 c8 } |
\times 4/6 { c8 c8 c8 c8 c8 c8 } |
}
\score {
\new PianoStaff
\new Staff = upper \upper
\new Staff = lower \lower
\layout {
\context {
\Score
tupletFullLength = ##t
\override TupletBracket #'bracket-visibility = ##t
\override TupletNumber #'text = #tuplet-number::calc-fraction-text
}
}
}
Best wishes,
Peter
--
//=
- Peter O'Doherty
- http://www.peterodoherty.net
- m...@peterodoherty.net
- https://joindiaspora.com/people/70716
//=
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tupletFullLength clashes with barline
On Sun, Mar 11, 2012 at 09:25:55AM +0100, Peter O'Doherty wrote:
On 03/10/2012 09:55 PM, Patrick Karl wrote:
On Mar 10, 2012, at 1:35 PM, Jamespkx1...@gmail.com wrote:
Message: 6
Date: Sat, 10 Mar 2012 19:34:40 +
From: Jamespkx1...@gmail.com
To: Peter O'Dohertym...@peterodoherty.net
Cc: lilypond-user@gnu.org
Subject: Re: tupletFullLength clashes with barline
Message-ID:
CA+T3wFkZtC-A0k6W1zjy3q2U=dtu8+qP+AWSf9rf=7orexq...@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Hello,
On 10 March 2012 08:18, Peter O'Dohertym...@peterodoherty.net wrote:
Hi list,
tupletFullLength = ##t
causes the right hand part of the tuplet bracket to clash with the barline.
This only happens with a barline at the end of a line.
Is there a way to avoid this?
Tiny example and the version you are using might help us.
Here's one that illustrates what he's talking about:
\version 2.14.2
music = \relative g' {
\repeat unfold 3 { \times 2/3 { f8 g a f g a f g a f g a} }
\break
\set tupletFullLength = ##t
\repeat unfold 3 { \times 2/3 { g8 a b g a b g a b g a b} }
}
\score { \new Staff { \music } }
Note that in the 1st two measures of the 2nd system the tuple bracket
extends slightly past the last note, but in the last measure in the 2nd
system the tuple bracket extends all the way to the bar line.
Regards,
Pat Karl
Thanks for the example Pat. That illustrates it well. This examples
shows how bad it looks in a piano stave:
\version 2.12.3
\include english.ly
upper = {
\clef treble
\time 4/8
\times 4/6 { c'8 c'8 c'8 c'8 c'8 c'8 } |
\times 4/6 { c'8 c'8 c'8 c'8 c'8 c'8 } |
\times 4/6 { c'8 c'8 c'8 c'8 c'8 c'8 } |
\break
\times 4/6 { c'8 c'8 c'8 c'8 c'8 c'8 } |
}
lower = {
\clef bass
\times 4/6 { c8 c8 c8 c8 c8 c8 } |
\times 4/6 { c8 c8 c8 c8 c8 c8 } |
\times 4/6 { c8 c8 c8 c8 c8 c8 } |
\times 4/6 { c8 c8 c8 c8 c8 c8 } |
}
\score {
\new PianoStaff
\new Staff = upper \upper
\new Staff = lower \lower
\layout {
\context {
\Score
tupletFullLength = ##t
\override TupletBracket #'bracket-visibility = ##t
\override TupletNumber #'text = #tuplet-number::calc-fraction-text
}
}
}
Not sure if this is the same issue or not, but there was another
recent posting about tupletFullLength:
http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg01081.html
And the associated issue tracker:
http://code.google.com/p/lilypond/issues/detail?id=2362
Cheers,
Colin.
--
Colin Hall
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Subdivide beam bug 2.15.33?
I'm not top posting
Nick Payne nick.payne at internode.on.net writes:
I would expect that all four beams should be subdivided, but only the
second beam in the bar is being subdivided:
\version 2.15.33
\relative c' {
\set tupletSpannerDuration = #(ly:make-moment 1 4)
\set baseMoment = #(ly:make-moment 1 8) \set subdivideBeams = ##t
\times 4/6 { \repeat unfold 24 { c16 } } |
}
Thanks for the bug report, Nick. An issue tracker was created and you can
follow
progress on it here:
http://code.google.com/p/lilypond/issues/detail?id=2386
Cheers,
Colin.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 2.0.4
2012/3/11 Janek Warchoł janek.lilyp...@gmail.com: Thanks and happy birthday to you! Frescobaldi is great! Yeah, I'm still not entirely convinced by the KDE-less version (in a couple months we should discuss it in the Report :-). But: happy birthday! Cheers, Valentin. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond 2.15.33 available as a FreeBSD port
On Sun, Mar 11, 2012 at 12:49 AM, lilyp...@umpquanet.com wrote: By and large, the project is already providing what FreeBSD LilyPond users want and need: a good product, built from clean, open source code which is highly portable to run on a variety of platforms. Well done, all of you. Hi Jim, would you by any chance be able to do some benchmarking of the compiled port versus our binary distribution? It would certainly be interesting to see whether it can speed things up for some large ly scores. Cheers, Valentin. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
line breaks within beamed tuplets
Hi,
Another question concerning tuplets:
\remove Forbid_line_break_engraver
\override Beam #'breakable = ##t
only seem to work with a single stave.
The code below causes a warning:
warning: forced break was overridden by some other event, should you be
using bar checks?
Is there an alternative?
Many thanks,
Peter
=
\version 2.12.3
upper = {
\clef treble
\time 4/8
c'8 c'8 c'8 c'8
c'8 c'8 c'8 c'8
c'8 c'8 c'8 c'8
c'8 c'8 c'8 c'8
}
lower = {
\clef bass
\times 4/5 { c8[ c8 c8 c8 c8] }
\times 5/6 { c8[ c8 c8 c8 c8 \bar \break c8] }
\times 3/4 { c8[ c8 c8 c8] }
\times 4/5 { c8 c8 c8 c8 c8 }
}
\score {
\new PianoStaff
\new Staff = upper \upper
\new Staff = upper \lower
\layout {
\context {
\Score
\remove Forbid_line_break_engraver
\override Beam #'breakable = ##t
}
}
}
--
//=
- Peter O'Doherty
- http://www.peterodoherty.net
- m...@peterodoherty.net
- https://joindiaspora.com/people/70716
//=
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Subdivide beam bug 2.15.33?
Nick Payne nick.pa...@internode.on.net wrote in message
news:4f5acab6.8090...@internode.on.net...
I would expect that all four beams should be subdivided, but only the
second beam in the bar is being subdivided:
\version 2.15.33
\relative c' {
\set tupletSpannerDuration = #(ly:make-moment 1 4)
\set baseMoment = #(ly:make-moment 1 8) \set subdivideBeams = ##t
\times 4/6 { \repeat unfold 24 { c16 } } |
}
For the record, this was added as
http://code.google.com/p/lilypond/issues/detail?id=2386
--
Phil Holmes
Bug Squad
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line breaks within beamed tuplets
On 03/11/2012 11:42 AM, m...@apollinemike.com wrote: On Mar 11, 2012, at 11:40 AM, Peter O'Doherty wrote: Hi, Another question concerning tuplets: \remove Forbid_line_break_engraver \override Beam #'breakable = ##t Try adding: \override TupletBracket #'breakable = ##t Cheers, MS Sorry, that doesn't work. Still getting warning: forced break was overridden by some other event, should you be using bar checks? Best, Peter -- //= - Peter O'Doherty - http://www.peterodoherty.net - m...@peterodoherty.net - https://joindiaspora.com/people/70716 //= ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line breaks within beamed tuplets
Peter O'Doherty-2 wrote: Hi, Another question concerning tuplets: \remove Forbid_line_break_engraver \override Beam #'breakable = ##t only seem to work with a single stave. no, they are alive in the \Voice environment! hth Eluze -- View this message in context: http://old.nabble.com/line-breaks-within-beamed-tuplets-tp33480342p33480572.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aleatoric / modern notation
On 3/11/12 12:53 AM, James Harkins jamshar...@gmail.com wrote: At Sun, 11 Mar 2012 08:12:35 +0100, m...@apollinemike.com wrote: The best way to achieve that with current LilyPond is Scheme engravers. There have been a few examples of Scheme engravers posted on this list (if you search Scheme engraver you'll find one - there are also examples in the input/regression folder of the LilyPond source). You'd want to create one that begins and ends a spanner when it hears a given event (you can invent a BoxNoteEvent, for example) and acknowledges note columns in the interim, putting them in a grob-array called note-columns or what-have-you. Then, make a print method that extracts these note columns (or whatever grobs you're interested in) finds the min/max height and width, and draws a box at those dimensions. If you want to get fancy, you can add extra spacing width to the left of the first note column and the right of the last note column to make sure there are no collisions with the box and surrounding material. I see... would it be too much to ask you to send your engraver to me (off list if you prefer)? That's of course assuming you developed one for your own music. Normally I don't mind doing some research and experimentation on my own, but in this case -- You might offer a bounty to Mike or to David Kastrup, in which case they would write the custom engraver for you. HTH, Carl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lyric hyphen goes outside staff limits at line break
David Nalesnik david.nalesnik at gmail.com writes: Hi Zsolt, On Sat, Mar 10, 2012 at 4:43 PM, -Eluze eluzew at gmail.com wrote: Zsolt Cselényi wrote: For the above the first line is broken after three bla-s and the hyphen of the last bla sticks out completely on the right. hi I think the paper-width is very short, too - is that your intention? did you mean \cm Sorry, I can't reproduce this. The notes are so close together the hyphens are suppressed when I run this with 2.14.2. -David ___ lilypond-user mailing list lilypond-user at gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user Hi, of course in the _tiny_ example I used narrow paper (yes, 2.8 cm) to bring out the error. However, it also happens in case of normal paper size: every now and then when working with longer chants where syllables have to be broken at the end of line, the hyphen connecting the last syllable on the line to the one on the next sticks out. I don't get it why you can't reproduce it. Yes, hyphens are suppressed mid-line but the one at the end should not be: that's the one sticking out off-staff. Should I post another example with bigger paper longer music? How can I share a print-out to show it looks at my end? Thanks! Zsolt ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bar Lines Disappear with Staff Line Count Change
On Sat, Mar 10, 2012 at 12:32 PM, Mark Mathias d8val...@gmail.com wrote:
Why do Bar Lines disappear when reducing the Staff Line count? I've tried
several alterations to the layout context for score, but don't get the right
results.
\version 2.15.33
\relative c'' {
\override Staff . StaffSymbol #'line-count = #1
b4 s r r
b b8 b b b s4
b s s s
}
Thanks!
Mark
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
They're disappearing because LilyPond is sizing the barline to fit the
staff lines. With only one staff line, the staff symbol is thin, so
the barlines are shrunk to a very small size.
Kieren's suggestion works great. If you need only one staff line and
only one pitch, another possibility is to use a RhythmicStaff:
\new RhythmicStaff {
c4 c c c | c d e f
}
There are some differences between rhythmic staves and normal staves
with one barline. If you want multiple pitches, a normal staff might
be better.
Hope this helps!
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ANN: Frescobaldi 2.0.4
Valentin Villenave valen...@villenave.net writes: 2012/3/11 Janek Warchoł janek.lilyp...@gmail.com: Thanks and happy birthday to you! Frescobaldi is great! Yeah, I'm still not entirely convinced by the KDE-less version (in a couple months we should discuss it in the Report :-). Should improve portability. For me, KDE is a non-starter. I once compared using Emacs (with AUCTeX, preview-latex and lots of other stuff) as a TeX shell with a bare-bones no-nonsense KDE application, I think Kile (or whatever it was called at that time). It turned out that just starting the KDE application had about three times the memory footprint of a full Emacs session with various directory edits, graphical previews and several source files and stuff. Three times. Because it started all sorts of daemons. And its private footprint alone was comparable to that of Emacs. That's the sort of baggage you don't want to be dragging around unnecessarily. It is a tradeoff that might be ok if your main work environment is KDE anyway, but it makes an application uninteresting when this is not the case. I don't know what kind of functionality hit the removal of the KDE dependency carried with it. But as a step for increasing the user base, feasible platforms and overall appeal, this was certainly a good strategic choice. And it is not likely the KDE users will now jump ship and use some other application instead. I still need to do a lot of other stuff before I can tackle Emacs support of LilyPond again. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Feathered beams: More than one beam at the end?
On Mar 11, 2012, at 9:04 AM, James Harkins wrote:
Another question -- is there any way to make the narrow end of a feathered
beam show more than one beam? That is, as far as I can see, the beams taper
down to one point (as in this code snip) but the documentation doesn't show
any way to specify the number of beams you want at the end.
\version 2.14.2
\include english.ly
% \override Beam #'grow-direction = #LEFT
% % revert to non-feathered beams
% \override Beam #'grow-direction = #'()
\relative c'' {
\key d \major
\numericTimeSignature
r16
\override Beam #'grow-direction = #LEFT
\scaleDurations #'(2 . 1) { e32 [ e e e e e e ] }
\override Beam #'grow-direction = #'()
e16 e e4.
}
In this example, I'd like to indicate that the note duration at the end of
the feathered bit should be a 16th note (and the performed rhythm would merge
smoothly with the metered notes following). As shown, it kind of looks like
the notes should slow down to roughly an eighth note, and then the next 16th
notes would be played faster. Not the intent.
Writing by hand, I might start the feathered part with 32nd notes and merge
two of the beams down into one, leaving 16th notes at the end.
If it's impossible, I'll work around it with some explanatory text. Maybe a
viable feature request?
'tis a viable feature request.
Han-Wen and I had kicked this idea around last year: I think all the code is
there in beam.cc : it's just a question of someone reading it, understanding
(or re-understanding) it, adding a few lines and creating a property.
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aleatoric / modern notation
On Mar 11, 2012, at 5:33 AM, James Harkins wrote: Possibly a common question, sorry if asked and answered before, but Google failed me... I'm considering some aleatoric notation (so-called box notation) for a piece but couldn't find info in the manuals (the contemporary notation section of the 2.14.2 docs @ lilypond.org is empty), or in the LSR, or Google searches to find out how to realize it. By box notation I mean collections of gestures/phrases, enclosed in a box, with an arrow indicating to keep doing that until the arrow stops. The phrases could use normal rhythmic notation or proportional notation without stems/flags. Some time ago, somebody posted a link to Mike Solomon's granini di luce beccucciati da uccelli di silenzio as an example of contemporary notation. The attached pic from it illustrates more-or-less what I'm after (though I wouldn't need the slash). Thanks! James Hey James, The best way to achieve that with current LilyPond is Scheme engravers. There have been a few examples of Scheme engravers posted on this list (if you search Scheme engraver you'll find one - there are also examples in the input/regression folder of the LilyPond source). You'd want to create one that begins and ends a spanner when it hears a given event (you can invent a BoxNoteEvent, for example) and acknowledges note columns in the interim, putting them in a grob-array called note-columns or what-have-you. Then, make a print method that extracts these note columns (or whatever grobs you're interested in) finds the min/max height and width, and draws a box at those dimensions. If you want to get fancy, you can add extra spacing width to the left of the first note column and the right of the last note column to make sure there are no collisions with the box and surrounding material. Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aleatoric / modern notation
On Mar 11, 2012, at 8:53 AM, James Harkins wrote: At Sun, 11 Mar 2012 08:12:35 +0100, m...@apollinemike.com wrote: The best way to achieve that with current LilyPond is Scheme engravers. There have been a few examples of Scheme engravers posted on this list (if you search Scheme engraver you'll find one - there are also examples in the input/regression folder of the LilyPond source). You'd want to create one that begins and ends a spanner when it hears a given event (you can invent a BoxNoteEvent, for example) and acknowledges note columns in the interim, putting them in a grob-array called note-columns or what-have-you. Then, make a print method that extracts these note columns (or whatever grobs you're interested in) finds the min/max height and width, and draws a box at those dimensions. If you want to get fancy, you can add extra spacing width to the left of the first note column and the right of the last note column to make sure there are no collisions with the box and surrounding material. I see... would it be too much to ask you to send your engraver to me (off list if you prefer)? That's of course assuming you developed one for your own music. Normally I don't mind doing some research and experimentation on my own, but in this case -- Unfortunately, the way I created mine was way hackish and not at all extensible, intelligent, or suitable to your needs (I hijacked a beam grob). The best thing to do is go ahead w/ the score as if it were to have boxes and then put something like : c d %\startBoxedNotes e f g %\endBoxedNotes wherever you need it. There are enough people on this list who know Scheme that someone is likely to pop up w/ a more fleshed-out solution in the next 6 weeks, and if not, in 6 weeks (if not less), I'll have some time to give it a go. Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond 2.15.33 available as a FreeBSD port
Hello, Von: Graham Percival gra...@percival-music.ca Technical reasons? not many. Cultural reasons? they don't like binaries. Actually, there are two significant technical reasons: the official FreeBSD packages are usually a bit behind on updates, and if you're running an older version of FreeBSD, packages may simply no longer be available. dependencies), but require a non-standardized way to install (i.e. the shell script) and uninstall (i.e. the uninstall-lilypond script) lilypond. Other ports do that as well, Opera would be one of them. Granted, that one is more of a binary installation wrapped up in a port. Still, using ports vs. packages might result in a different version being installed :-o As for me, I was glad the official port was switched from the development branch to the stable branch some time ago. After all, the development version may contain a critical bug that you won't know about unless you're reading some of the mailing lists. As a sidenote: I did initially install Lilypond from ports while it was still building the devel version. I then encountered the user error regarding the \relative command I asked about some time ago. That made me try to install the FreeBSD source package that was offered at the time, but couldn't get it to work as per the instructions. I worked around this by combining the stable sources with the devel makefile :- Regards, Frank ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line breaks within beamed tuplets
On Mar 11, 2012, at 11:40 AM, Peter O'Doherty wrote: Hi, Another question concerning tuplets: \remove Forbid_line_break_engraver \override Beam #'breakable = ##t Try adding: \override TupletBracket #'breakable = ##t Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aleatoric / modern notation
At Sun, 11 Mar 2012 13:40:19 +, Carl Sorensen wrote: You might offer a bounty to Mike or to David Kastrup, in which case they would write the custom engraver for you. Thinking about that... either monetary or a delivery from a microbrewery? :-p This might be viable in the meantime. I already know how to make a zigzag using a glissando following it. http://lsr.dsi.unimi.it/LSR/Item?id=377 hjh -- James Harkins /// dewdrop world jamshar...@dewdrop-world.net http://www.dewdrop-world.net Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal. -- Whitman blog: http://www.dewdrop-world.net/words audio clips: http://www.dewdrop-world.net/audio more audio: http://soundcloud.com/dewdrop_world/tracks ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lyric hyphen goes outside staff limits at line break
Zsolt Cselényi wrote: Hi, of course in the _tiny_ example I used narrow paper (yes, 2.8 cm) to bring out the error. However, it also happens in case of normal paper size: every now and then when working with longer chants where syllables have to be broken at the end of line, the hyphen connecting the last syllable on the line to the one on the next sticks out. I don't get it why you can't reproduce it. Yes, hyphens are suppressed mid-line but the one at the end should not be: that's the one sticking out off-staff. Should I post another example with bigger paper longer music? How can I share a print-out to show it looks at my end? Thanks! Zsolt I'm not familiar with this music, but does \override LyricHyphen #'minimum-distance = #9 help? Eluze -- View this message in context: http://old.nabble.com/lyric-hyphen-goes-outside-staff-limits-at-line-break-tp33477550p33481269.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Creating a mini-system for a separate coda
Hi Eluze, 2012/3/10 -Eluze elu...@gmail.com: The first image is a scanned example of what I've been trying to reproduce, and the second where I've gotten so far—which is pretty close. The only thing missing is the systemStartBracket, and I'm stuck with no idea how to insert one in the middle of a system. Does anybody reading this happen to know the secret ingredient? I don't think I've ever seen a systemStartBracket not at the beginning of a score or a line - wondering if somebody finds a solution, though! some month ago I created the attached workaround. hi Harm congrats - now I wonder if (hope that) you're gonna put it in the LSR!? Eluze will do, as soon the LSR is updated. And I did my very best to get that rolling. :) Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond 2.15.33 available as a FreeBSD port
On Sun, Mar 11, 2012 at 11:15:57AM +0100, Valentin Villenave wrote: On Sun, Mar 11, 2012 at 12:49 AM, lilyp...@umpquanet.com wrote: By and large, the project is already providing what FreeBSD LilyPond users want and need: a good product, built from clean, open source code which is highly portable to run on a variety of platforms. ??Well done, all of you. Hi Jim, would you by any chance be able to do some benchmarking of the compiled port versus our binary distribution? It would certainly be interesting to see whether it can speed things up for some large ly scores. Cheers, Valentin. Hi, Valentin. I don't think I can accomplish that at the moment, but I will mail you off-list with a slightly more round-about method that might be more feasible for me. I wouldn't expect any speed difference, but I've never tested that assumption, since I rarely produce large scores. Jim ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lyric hyphen goes outside staff limits at line break
Hi Zsolt,
2012/3/11 -Eluze elu...@gmail.com:
Zsolt Cselényi wrote:
Hi, of course in the _tiny_ example I used narrow paper (yes, 2.8 cm) to
bring
out the error. However, it also happens in case of normal paper size:
every now
and then when working with longer chants where syllables have to be broken
at
the end of line, the hyphen connecting the last syllable on the line to
the one
on the next sticks out.
I don't get it why you can't reproduce it. Yes, hyphens are suppressed
mid-line
but the one at the end should not be: that's the one sticking out
off-staff.
Should I post another example with bigger paper longer music? How can I
share
a print-out to show it looks at my end?
Thanks!
Zsolt
I'm not familiar with this music, but does
\override LyricHyphen #'minimum-distance = #9 help?
Eluze
I've no solution but some observations:
\remove Bar_engraver causes some problems, \override SpacingSpanner
#'packed-spacing = ##t from gregorian.ly, too.
But it is possible to provoke the problem even without them. -
attached png (The last LyricHyphen of the line collides with the
BarLine.)
My attempt to alter the 'X-extent of the last stem of a line from
inside a LyricHyphen-override failed. And I don't know why. I can
change the color of the stem but not the 'X-extent! Overriding it
directly in the Voice works.
\version 2.14.2
#(define (lyric-hyphen-callback-test-2 hyphengrob)
(let* ((par (ly:grob-parent (ly:grob-parent hyphengrob X) X))
(st (ly:grob-object par 'stem))
(orig (ly:grob-original hyphengrob))
(siblings (if (ly:grob? orig)
(ly:spanner-broken-into orig)
'() )))
(if (and (= (length siblings) 2)
(eq? (car siblings) hyphengrob))
(begin
(ly:grob-set-property! st 'color red)
(ly:grob-set-property! st 'X-extent '(0 . 10))
myLayout = \layout {
indent = 18
\context {
\Score
\override NonMusicalPaperColumn #'line-break-permission = ##f
}
\context {
\Lyrics
\override LyricHyphen #'after-line-breaking =
#lyric-hyphen-callback-test-2
}
}
chant = {
\repeat unfold 23 { f' }
%\once \override Stem #'X-extent = #'(0 . 2)
f'
\break
f'1
}
verba = \lyricmode { \repeat unfold 24 { bla -- } bla }
\score {
\new StaffGroup
\new Staff
\new Voice = melody1 \chant
\new Lyrics = one \lyricsto melody1 \verba
\new Staff
\new Voice = melody2 \chant
\new Lyrics = two \lyricsto melody2 \verba
\layout { \myLayout }
}
Regards,
Harm
attachment: lyric-hyphen-test.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Did you receive my LilyPond messages?
2012/3/11 John Link johnl...@nyc.rr.com: Hi Thomas, I just joined the LilyPond list and have sent three messages but not received copies of them despite having specified in my settings that I am to receive copies of messages I send. I have received messages from you. Have you received any of my previous messages? Thanks, John Link http://www.cdbaby.com/all/johnlink http://www.myspace.com/johnlinkproject Hi John, I never received messages from you. Perhaps you should check your settings. I've cc'ed the user-list. Maybe someone else can give you more advice. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Feathered beams: More than one beam at the end?
At Sun, 11 Mar 2012 18:03:42 +0100, Thomas Morley wrote: Hi, last year I created a work-around to make feathered beams more variable. Thanks again to David Nalesnik for his great help. - http://old.nabble.com/Making-feathered-beams-more-variable-td32705102.html#a32790344 Now that I've replaced my eyeballs back in their sockets, I can say -- thanks for this! Your update of my example looks clean and conveys the intent. Thank you James -- James Harkins /// dewdrop world jamshar...@dewdrop-world.net http://www.dewdrop-world.net Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal. -- Whitman blog: http://www.dewdrop-world.net/words audio clips: http://www.dewdrop-world.net/audio more audio: http://soundcloud.com/dewdrop_world/tracks ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
