Re: Issue 1724 -> 620 : workaround?
On 24 July 2011 21:46, Xavier Scheuer wrote: > > Thanks Neil! > > It works great. I'll use it as a workaround until Mike's fix is OK and > pushed. Thank you Mike too. Good luck. I did not notice first but Neil's workaround produces a strange message in the console when compiling: […] Interpreting music... #()[8]##()##()###()##[16]()##()#[24]###()##()###()[32]#()#()[40]##()()[48]##()##()##()##()[56]#()[64]()#()#()[72]##() Preprocessing graphical objects... […] This has no bad consequences and as I said the result is good. Cheers, Xavier -- Xavier Scheuer ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue 1724 -> 620 : workaround?
On Mon 25 Jul 2011, 09:21 Xavier Scheuer wrote: > On 24 July 2011 21:46, Xavier Scheuer wrote: > > > > Thanks Neil! > > > > It works great. I'll use it as a workaround until Mike's fix is OK and > > pushed. Thank you Mike too. Good luck. > > I did not notice first but Neil's workaround produces a strange message > in the console when compiling: That was (display (ly:grob-parent g X)) I guess. You can comment it out. > […] > Interpreting music... #()[8]# >#()## >()### >()##[16]()# >#()### PaperColumn >##[24]# PaperColumn >##()# PaperColumn >#()## PaperColumn >#()[32]#()# DynamicText >()[40]##()# PaperColumn >### PaperColumn >()[48]##()# PaperColumn >#()## PaperColumn >()##()[56]# PaperColumn >### PaperColumn >#()## PaperColumn >##[64]()# DynamicText >()#()[72]## PaperColumn >() > Preprocessing graphical objects... > […] > > This has no bad consequences and as I said the result is good. > > Cheers, > Xavier > > -- > Xavier Scheuer > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: multiple timesignatures
Am 23.07.2011 19:38, schrieb Reinhold Kainhofer: Am Samstag, 23. Juli 2011, 19:28:08 schrieb Ruud van Silfhout: However, I thought now compoundMeters made it into lily, it is also time that multiple meters should make it into lily as a logical successor :-). Actually, dual times (like 3/4 5/4) are not easy to support in lilypond, because lilypond relies on the time signature to calculate the measure length (the | are just checks, they don't cause a new measures!). For dual times, each measure length might be either of the two values, possibly with no logical structure, so lilypond does not have any information about the measure length. (For dual times like 3/4 6/8 which have the same length the measure length is not a problem, but now lilypond doesn't know which automatic beaming to apply to a measure...) As I understand the OP, he would want to supply the actual \time - just suppress the printing of the time signature. So this shouldn't be a problem. Cheers, Reinhold ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Regarding the Table of Contents.
Greetings All, I am nearing the completion of a massive project for piano, four hands. Using the wonderful piece of code supplied by Robin Bannister (see link below), I have successfully formatted separate Secondo and Primo parts. Is there a way to influence the toc:page element into returning the new resulting page numbers rather than the literal number of pages which have transpired? Many thanks. Hwaen Ch'uqi http://lists.gnu.org/archive/html/lilypond-user/2011-06/msg9.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
changing PianoPedalBracket-style
Dear community,
I've changed the PianoPedalBracket-style.
It works fine, but the end of the pedal-line isn't convincing for me.
Is there a way to change it?
\version "2.14.1"
right = { c'1 }
left = { \clef bass
\override Staff.PianoPedalBracket #'style = #'zigzag %works fine, only the
ending isn't nice
\override PianoStaff.PianoPedalBracket #'style = #'bracket \set
PianoStaff.pedalSustainStyle = #'mixed
\clef bass c16->\sustainOn r16 r8 r4 r2 \sustainOff
}
\score {
\new PianoStaff
<< \new Staff \right
\new Staff \left >>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: changing PianoPedalBracket-style
Hello Thomas
Stefan Thomas schrieb:
> Dear community,
> I've changed the PianoPedalBracket-style.
> It works fine, but the end of the pedal-line isn't convincing for me.
> Is there a way to change it?
>
> \version "2.14.1"
>
> right = { c'1 }
> left = { \clef bass
either this:
> \override Staff.PianoPedalBracket #'style = #'zigzag %works fine, only the
> ending isn't nice
or this:
> \override PianoStaff.PianoPedalBracket #'style = #'bracket \set
> PianoStaff.pedalSustainStyle = #'mixed
Try this (simply removes the ending):
\override Staff.PianoPedalBracket #'edge-height = #'(1.0 . 0)
> \clef bass c16->\sustainOn r16 r8 r4 r2 \sustainOff
> }
>
> \score {
> \new PianoStaff
> << \new Staff \right
> \new Staff \left >>
> }
Dieter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Last staff -coda staff- position
Hi Lily's.
I'm trying to clearly put apart a single coda staff from the rest of the
part. Pretty sure a common thing.
The thing is I'm lost :)
The file structure its easy (example):
###
\version 2.14.1
melody = { a a a a | c c c c | blah blah blah blah large one voice part }
% a simple 3 bars coda.
codaPart = { b b b b | d d d d | a2. r4 \bar "|." }
\score {
\melody
% clearly blank space for separating coda from part. As minimum of the
default space or lets say height of a staff.
% try adding lots of \break s do nothing ;)
\codaPart
}
###
There's these old treat including these kind of thing but its rather
confusing: "Codas - STILL can't get it
right..."
Thanks
tdy.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: changing staffgroup-staff-spacing
Dear Keith, dear Community,
I tought I could also solve problem in the below quoted snippet with and
override of minimum-Y-extent. But unfortunately, I get a bad collision
between dynamics and and the next staff:
\version "2.14.1"
re = { \change Staff = right }
li = { \change Staff = left }
primoA = \relative c''' {
\crescTextCresc
\override PianoStaff.DynamicText #'minimum-Y-extent = #'(-12 . 0) % this
results in a strange-looking result!
bes16\< as f d \times 4/5 {a16-.[ e-. \li b-. fis-. c-.]} \ottava
#-1 \times 2/3 {f,16-. bes,-. es,-.}
a,16-.\ff \ottava #0 r r4 | %klaviereinsright 46
}
primoB = { \clef bass
#(ly:export (skip-of-length primoA))
}
secondoA = \relative a'{
\times 4/5 { a16-.[ e-. \li b-. fis-. c-.] } \times 2/3 { f,16-.[ bes,-.
ees,-.]} \re r 8 r 2
}
secondoB = { \clef bass #(ly:export (skip-of-length secondoA)) }
\score {
<<
\new PianoStaff
<< \new Staff ="right" \primoA
\new Staff ="left" \primoB >>
\new PianoStaff
<< \new Staff ="right" \secondoA
\new Staff ="left" \secondoB >>
>>
}
2011/7/24 Keith OHara
> On Sat, 23 Jul 2011 03:52:07 -0700, Stefan Thomas <
> kontrapunktstefan@googlemail.**com >
> wrote:
>
> I think, the thing with the "skyline-horizontal-padding" should be also a
>> part of the documentation. At least I didn't find it there.
>>
>>
> Right. Both this and the minimum-Y-extent are mentioned only in the
> Internals Reference, "user back-end properties", with other things that
> people rarely need to use. These two could probably benefit from an example
> in the main documentation. You can write a documentation addition and
> suggest a place to put it in the manual. I'll think about doing so as well,
> and post if I do.
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Fwd: Last staff -coda staff- position
Sorry!!!
Forgot to add a \break before the \coda. At list one is needed. But it would
be great to be able to add more vertical space to that break.
the example again with the \break:
###
\version 2.14.1
melody = { a a a a | c c c c | blah blah blah blah large one voice part }
% a simple 3 bars coda.
codaPart = { b b b b | d d d d | a2. r4 \bar "|." }
\score {
\melody
\break
% clearly blank space for separating coda from part. As minimum of the
default space or lets say height of a staff.
% try adding lots of \break s do nothing ;)
\codaPart
}
###
Thanks again!!!
tdy.
-- Forwarded message --
From: Pato Press
Date: 2011/7/25
Subject: Last staff -coda staff- position
To: lilypond-user@gnu.org
Hi Lily's.
I'm trying to clearly put apart a single coda staff from the rest of the
part. Pretty sure a common thing.
The thing is I'm lost :)
The file structure its easy (example):
###
\version 2.14.1
melody = { a a a a | c c c c | blah blah blah blah large one voice part }
% a simple 3 bars coda.
codaPart = { b b b b | d d d d | a2. r4 \bar "|." }
\score {
\melody
% clearly blank space for separating coda from part. As minimum of the
default space or lets say height of a staff.
% try adding lots of \break s do nothing ;)
\codaPart
}
###
There's these old treat including these kind of thing but its rather
confusing: "Codas - STILL can't get it
right..."
Thanks
tdy.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Last staff -coda staff- position
On 25 July 2011 21:00, Pato Press wrote: > > Sorry!!! > > Forgot to add a \break before the \coda. At list one is needed. But it would > be great to be able to add more vertical space to that break. Have you seen the two following snippets on the LSR? "Positioning segno and coda (with line break)" http://lsr.dsi.unimi.it/LSR/Item?id=190 "Positioning segno and coda (without line break)" http://lsr.dsi.unimi.it/LSR/Item?id=198 Cheers, Xavier -- Xavier Scheuer ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: changing staffgroup-staff-spacing
On Mon, 25 Jul 2011 11:52:06 -0700, Stefan Thomas
wrote:
I thought I could also solve problem in the below quoted snippet with and
override of minimum-Y-extent. But unfortunately, I get a bad collision
between dynamics and and the next staff:
The crescendo to ff spans a line of music that crosses staves. LilyPond lets
you cross any number of staves, but to do so she ignores collisions of spanners
that cross staves. You might want to use #(ly:set-option 'debug-skylines) to
see outlines of what items get space reserved for them.
The crescendo runs through the ottava bracket even without the override.
Extending the ff downward with (-12 . 0) lowered the cresc. , but did not push
the next staff down because the ff is part of a line that Lilypond believes is
allowed to cross staves.
I would place the dynamics in the lower primo staff
primoB = { \clef bass
\crescTextCresc
s2\< s8 s8\ff s4
}
If you need the dynamics in their logical voice (for MIDI output?) the you
could use
\once\override DynamicLineSpanner #'Y-offset = #-19
before the note with the \< to specify where you want the dynamics line
relative to the *upper* staff (its original staff).
I recommend you use "\once" before any override of minimum-Y-extent, and use it
on items that are fixed to a staff. In this case the only solid item I see is the last
rest in secundoA
\once\override Rest #'minimum-Y-extent = #'(0 . 6)
r2
Four-hand modern piano music will be very frustrating, or maybe very rewarding,
to typeset.
Stefan.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Last staff -coda staff- position
Thanks Xavier these http://lsr.dsi.unimi.it/LSR/Item?id=190 snippet helps a
lot!
I'll paste the tweaked snippet:
###
\version "2.14.1"
call = {
% These is taken from the above snippet
\cadenzaOn
\stopStaff
\once \override TextScript #'word-space = #1.5
\once \override TextScript #'X-offset = #8
\once \override TextScript #'Y-offset = #1.5
s1*0^\markup { \center-column { "D.S. al Coda" \line { \musicglyph
#"scripts.segno" \musicglyph #"scripts.tenuto" \musicglyph #"scripts.coda" }
} }
% Tweaking for having more space
\repeat unfold 2 {
\repeat unfold 4 {
s1*4
\bar ""
}
\break
\once \override Staff.Clef #'stencil = ##f
\once \override Staff.KeySignature #'stencil = ##f
}
\break
\startStaff
\cadenzaOff
}
% Testing area
melo = {
\repeat unfold 4 {a4}
\mark \markup { \musicglyph #"scripts.segno" }
\repeat unfold 4 {b4}
\repeat unfold 4 {c4}
\mark \markup { \musicglyph #"scripts.coda" }
\repeat unfold 4 {d4}
\bar "||"
}
codamelo = {
\mark \markup { \musicglyph #"scripts.coda" }
c'2\upbow^\fermata r2 | d2^\fermata r2 | es2.:32^\fermata r4
\bar "|."
}
\layout {
ragged-last = ##t
}
\score {
\relative c'' {
\time 4/4
\melo
\call
\codamelo
}
}
#
Thanks again!
tdy.
2011/7/25 Xavier Scheuer
> On 25 July 2011 21:00, Pato Press wrote:
> >
> > Sorry!!!
> >
> > Forgot to add a \break before the \coda. At list one is needed. But it
> would
> > be great to be able to add more vertical space to that break.
>
> Have you seen the two following snippets on the LSR?
>
> "Positioning segno and coda (with line break)"
> http://lsr.dsi.unimi.it/LSR/Item?id=190
> "Positioning segno and coda (without line break)"
> http://lsr.dsi.unimi.it/LSR/Item?id=198
>
> Cheers,
> Xavier
>
> --
> Xavier Scheuer
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shaping slurs --- both broken and unbroken
2011/7/24 David Nalesnik > Hello, all -- > > > This is on the LSR, at least. >> > http://lsr.dsi.unimi.it/LSR/Item?id=639 >> > > Just thought I'd let you know that Dmytro's function as given on the > earlier thread incorporates an older version of my slur-shaping function. > I've modified it since, and this newer version appears on the LSR in the > same spot. (It can now be easily adapted to work with grobs having fewer > than 8 control-points -- TupletBracket, for example -- without changing the > loop.) In the attached file, I've incorporated the rewrite in Dmytro's > function. > > Thanks! > > David > > This is a great function. The result is so much nicer. I'd very much like for the the slur to be printed this way out of the box. Isn't it possible for lilypond to compute the angles between the notes inside the slur? -Marc ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
