Re: parenthesizing arpeggios
Thank you very much, I will try this out later today.
By overriding the stencil directly you have already solved my other problem
that I didn't even post so far ;-)
Now I can write a macro
editorialArpeggio = {
\once \override Arpeggio ...
}
I need this because I place all my editor's additions in an extra file. They
are then processed through a "draftMode.ily" to color them while I'm still in
the editing process ...
Best
Urs
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
David Nalesnik schrieb:
Hi again!
Here's something that works for arpeggios. The attached file is a bit large
because I needed to include several functions from stencil.scm to draw the
parentheses.
Oh, what ever was I thinking! No need at all for all that duplicated code...
This is all you need:
\version "2.15.36"
\relative c' {
\override Arpeggio #'stencil = #(lambda (grob)
(parenthesize-stencil (ly:arpeggio::print grob) 0.1 0.5 0.5 0.2))
\override Arpeggio #'before-line-breaking = #(lambda (grob)
(set! (ly:grob-property grob 'X-extent)
(ly:stencil-extent (ly:grob-property grob 'stencil) X)))
\repeat unfold 4 {
-\arpeggio
}
-\arpeggio
-\arpeggio
-\arpeggio
-\arpeggio
}
-David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: parenthesizing arpeggios
Hi again!
> Here's something that works for arpeggios. The attached file is a bit
> large because I needed to include several functions from stencil.scm to
> draw the parentheses.
>
Oh, what ever was I thinking! No need at all for all that duplicated
code...
This is all you need:
\version "2.15.36"
\relative c' {
\override Arpeggio #'stencil = #(lambda (grob)
(parenthesize-stencil (ly:arpeggio::print grob) 0.1 0.5 0.5 0.2))
\override Arpeggio #'before-line-breaking = #(lambda (grob)
(set! (ly:grob-property grob 'X-extent)
(ly:stencil-extent (ly:grob-property grob 'stencil) X)))
\repeat unfold 4 {
-\arpeggio
}
-\arpeggio
-\arpeggio
-\arpeggio
-\arpeggio
}
-David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: parenthesizing arpeggios
Hi Urs,
On Sun, Apr 22, 2012 at 6:37 PM, Urs Liska wrote:
> Dear listers,
>
> I thought it should be simple and straightforward, but I don't understand
> how to put an arpeggio in brackets.
> If I use this code I only get a very small parenthesis:
>
> \version "2.15.36"
> \relative c' {
> %\once \override ParenthesesItem #'font-size = #6
> -\parenthesize \arpeggio
> }
>
> If I use the (commented out) override, I get a much bigger parenthesis but
> this doesn't work at all, because it is too wide and round.
> Is there a possibility to put brackets around objects and let the brackets
> adapt to the height of the objects (like spanners)?
>
Here's something that works for arpeggios. The attached file is a bit
large because I needed to include several functions from stencil.scm to
draw the parentheses. (I included parenthesize-stencil, commented out, so
you can see what the numbers in my override refer to.)
The override of 'before-line-breaking is necessary for horizontal spacing.
Sorry I don't have a simple solution involving ParenthesesItem. Perhaps
someone else will have an idea.
Best,
David
parenthesize-arpeggio.ly
Description: Binary data
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: barcheck warning when using Timing.measurePosition in polyphonic music
On 22/04/12 22:12, Federico Bruni wrote:
Hi,
just a nitpick...
In NR 1.2.3, Upbeats, Known issues and warnings
\set Timing.measurePosition is recommended instead of \partial when
the partial measure occurs after the beginning of the piece.
Single voice music compiles fine and without warnings:
\version "2.15.36"
\relative c'' {
\time 4/4
\partial 2 g2 |
g1 |
\set Timing.measurePosition = #(ly:make-moment -2 4)
g2 |
g1 |
}
Polyphonic music compiles fine but I get a barcheck warning:
\version "2.15.36"
\new Staff <<
\new Voice = "first" \relative c'' {
\time 4/4
\partial 2 g2 |
g1 |
\set Timing.measurePosition = #(ly:make-moment -2 4)
g2 |
g1 |
}
\new Voice= "second" \relative c' {
\time 4/4
\partial 2
c2 |
c1 |
\set Timing.measurePosition = #(ly:make-moment -2 4)
c2 |
c1 |
}
>>
The warning is:
warning: barcheck failed at: -1/2
If you replace
\set Timing.measurePosition = #(ly:make-moment -2 4)
with
\set Score.measureLength = #(ly:make-moment 2 4)
you don't get a barcheck error.
Nick
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
parenthesizing arpeggios
Dear listers,
I thought it should be simple and straightforward, but I don't
understand how to put an arpeggio in brackets.
If I use this code I only get a very small parenthesis:
\version "2.15.36"
\relative c' {
%\once \override ParenthesesItem #'font-size = #6
-\parenthesize \arpeggio
}
If I use the (commented out) override, I get a much bigger parenthesis
but this doesn't work at all, because it is too wide and round.
Is there a possibility to put brackets around objects and let the
brackets adapt to the height of the objects (like spanners)?
Thanks for hints
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: multiple tags
James writes:
> Is is possible to have simultaneous multiple tags?
> I'm trying:
> \version "2.14.2"
>
> control = {
> s1*2
> \tag #'threes { \time 3/4 s2. }
> \tag #'twos { \time 2/4 s2 } }
> tset = \relative c' {
> c4 d e f
> \tag #'up {g4 a b c }
> \tag #'down { g4 f e d }
> \tag #'threes { g4 f e }
> \tag #'twos { g2 } }
>
> \score {
> \new Staff << {
> \keepWithTag #'threes
> \control } {
> \keepWithTag #'up
> \keepwithTag #'threes
> \tset } >> }
> \score {
> \new Staff << {
> \keepWithTag #'twos
> \control } {
> \keepWithTag #'down
> \keepWithTag #'twos
> \tset } >> }
>
> but lilypond is not happy with the doubled tags.
What makes you think that? It is quite happy, but if you ask it to
remove every tag except #'twos, and then remove every remaining tag
except #'down, naturally nothing will be left. \keepWithTag does not
make sense with nested expressions: you need to use \removeWithTag in
this case.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
multiple tags
Is is possible to have simultaneous multiple tags?
I'm trying:
\version "2.14.2"
control = {
s1*2
\tag #'threes { \time 3/4 s2. }
\tag #'twos { \time 2/4 s2 } }
tset = \relative c' {
c4 d e f
\tag #'up {g4 a b c }
\tag #'down { g4 f e d }
\tag #'threes { g4 f e }
\tag #'twos { g2 } }
\score {
\new Staff << {
\keepWithTag #'threes
\control } {
\keepWithTag #'up
\keepwithTag #'threes
\tset } >> }
\score {
\new Staff << {
\keepWithTag #'twos
\control } {
\keepWithTag #'down
\keepWithTag #'twos
\tset } >> }
but lilypond is not happy with the doubled tags.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: how to post
James, you wrote Sunday, April 22, 2012 9:33 PM How do I not top-post? Start your post with "> I'm top-posting", or anything beginning with ">" Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
how to post
I have a question, but every time I try to post it, gmane complains that I'm top-posting. How do I not top-post? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Make Tie a Slur
Am 22.04.2012 15:05, schrieb Nils:
I have 70 pieces with ties and slurs here. They are already in
Lilypond with the correct syntax.
Now my publisher says he wants that ties look like slurs.
I couldn't disagree more but I have no choice here.
Any suggestions how make the ties look like slurs without changing
them all manually?
>
> The end results are ties that look like slurs. And slurs should look
> like slurs as well :) The idea is a more curved version. When I asked
> the publisher for an example he told me the real slurs are perfectly
> fine.
Well it doesn't look exactly like a slur. But your publisher might be
satisfied with the Tie ratio:
\relative c'' {
c~ c
c( c)
\override Tie #'details #'ratio = #2
c~c
}
This does not change the start and end position of the tie but it is
more curved.
> He sees no distinction between a slur and a tie. For him it is
> only the context which decides if it is a slur or a tie. This is so
> wrong, but what can I do...
I heard this from several musicians that just read the score. They look
at each note (or slur or tie ...) only for the fraction of a second.
Regards,
Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: String Bass Notation
I'm a doublebass student at Music Acadamy in Zagreb..this should be a bartok pizzicato..i didn't heard that there is an articulation like this and would have a diferent meaning. I aggree with tim that it is easyer to write.. On Sun, Apr 22, 2012 at 5:46 AM, Mark Mathias wrote: > I'm a bass player who studied with Larry Hurst in the early 70s and > a public school string teacher, so I've seen a lot of notation, but never > what you are describing. The snap pizzicato has the line drawn vertically > through the top of the circle only and the thumb symbol (a fingering > indication --- very unlikely in the situation you describe) is a circle > with the vertical line extending downward from the bottom. Both are > implemented in LilyPond: > c4\snappizzicato c\thumb > > HTH! > Mark > > On Thu, Apr 19, 2012 at 1:48 PM, Tim Roberts wrote: > >> -Eluze wrote: >> > Tim Roberts wrote: >> >> This is a hand-drawn score. I'm thinking that they probably meant snap >> >> pizzicato, and it was easier to draw the line all the way through than >> >> to stop part way through. Snap pizzicato would fit in the context, and >> >> I have found no source that shows the exact "phi" symbol. Have any of >> >> you string players seen that notation? >> > sorry, I didn't find this score - am i missing something? >> >> No, I didn't attach an image because I didn't get a chance to grab a >> copy. I "assumed" my description would be sufficient... >> >> -- >> Tim Roberts, t...@probo.com >> Providenza & Boekelheide, Inc. >> >> >> ___ >> 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 > > -- *Nesmotren govori kao da mačem probada, a jezik je mudrih iscjeljenje. Izreke 12:18* ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Make Tie a Slur
Am 22.04.2012 15:05, schrieb Nils:
Sun, 22 Apr 2012 14:47:57 +0200
schrieb Urs Liska:
Am 21.04.2012 17:53, schrieb Pavel Roskin:
Quoting Nils:
Hello,
I have 70 pieces with ties and slurs here. They are already in
Lilypond with the correct syntax.
Now my publisher says he wants that ties look like slurs.
I couldn't disagree more but I have no choice here.
Any suggestions how make the ties look like slurs without changing
them all manually?
It may be possible to write an engraver that would get tie events,
hide ties and create slurs instead. But I see little motivation to
do something that won't improve music typesetting.
You may want to replace ties with macros that can expand to a slur
or to a tie.
%% Insane publisher
%tieStart = (
%tieEnd = )
% Sane publisher
tieStart = ~
tieEnd = {}
{ c'' \tieStart c'' \tieEnd }
I don't think this is something the OP wants to do as he has 70
finished pieces.
What he wants is a general override to achieve the desired look,
isn't it?
Nils, you might get help if you tell us what it is you want to
achieve. Maybe post images of the current and the desired output?
Best
Urs
The end results are ties that look like slurs. And slurs should look
like slurs as well :) The idea is a more curved version. When I asked
the publisher for an example he told me the real slurs are perfectly
fine. He sees no distinction between a slur and a tie. For him it is
only the context which decides if it is a slur or a tie. This is so
wrong, but what can I do...
While it is not impossible to regexp my way through the files I would
be happy to find a less intrusive solution since I want to use the
files for myself in the end privately. With real ties.
Nils
Then please make a few tiny examples comparing real ties and real slurs
instead of them.
Probably I won't be of much help then (although I may try).
But this would be a concrete question which probably would trigger some
assistance on this list ;-)
Best
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Make Tie a Slur
Sun, 22 Apr 2012 14:47:57 +0200
schrieb Urs Liska :
> Am 21.04.2012 17:53, schrieb Pavel Roskin:
> > Quoting Nils :
> >
> >> Hello,
> >>
> >> I have 70 pieces with ties and slurs here. They are already in
> >> Lilypond with the correct syntax.
> >>
> >> Now my publisher says he wants that ties look like slurs.
> >> I couldn't disagree more but I have no choice here.
> >>
> >> Any suggestions how make the ties look like slurs without changing
> >> them all manually?
> >
> > It may be possible to write an engraver that would get tie events,
> > hide ties and create slurs instead. But I see little motivation to
> > do something that won't improve music typesetting.
> >
> > You may want to replace ties with macros that can expand to a slur
> > or to a tie.
> >
> > %% Insane publisher
> > %tieStart = (
> > %tieEnd = )
> >
> > % Sane publisher
> > tieStart = ~
> > tieEnd = {}
> >
> > { c'' \tieStart c'' \tieEnd }
> >
> I don't think this is something the OP wants to do as he has 70
> finished pieces.
> What he wants is a general override to achieve the desired look,
> isn't it?
>
> Nils, you might get help if you tell us what it is you want to
> achieve. Maybe post images of the current and the desired output?
>
> Best
> Urs
The end results are ties that look like slurs. And slurs should look
like slurs as well :) The idea is a more curved version. When I asked
the publisher for an example he told me the real slurs are perfectly
fine. He sees no distinction between a slur and a tie. For him it is
only the context which decides if it is a slur or a tie. This is so
wrong, but what can I do...
While it is not impossible to regexp my way through the files I would
be happy to find a less intrusive solution since I want to use the
files for myself in the end privately. With real ties.
Nils
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Make Tie a Slur
Am 21.04.2012 17:53, schrieb Pavel Roskin:
Quoting Nils :
Hello,
I have 70 pieces with ties and slurs here. They are already in Lilypond
with the correct syntax.
Now my publisher says he wants that ties look like slurs.
I couldn't disagree more but I have no choice here.
Any suggestions how make the ties look like slurs without changing them
all manually?
It may be possible to write an engraver that would get tie events,
hide ties and create slurs instead. But I see little motivation to do
something that won't improve music typesetting.
You may want to replace ties with macros that can expand to a slur or
to a tie.
%% Insane publisher
%tieStart = (
%tieEnd = )
% Sane publisher
tieStart = ~
tieEnd = {}
{ c'' \tieStart c'' \tieEnd }
I don't think this is something the OP wants to do as he has 70 finished
pieces.
What he wants is a general override to achieve the desired look, isn't it?
Nils, you might get help if you tell us what it is you want to achieve.
Maybe post images of the current and the desired output?
Best
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
barcheck warning when using Timing.measurePosition in polyphonic music
Hi,
just a nitpick...
In NR 1.2.3, Upbeats, Known issues and warnings
\set Timing.measurePosition is recommended instead of \partial when the
partial measure occurs after the beginning of the piece.
Single voice music compiles fine and without warnings:
\version "2.15.36"
\relative c'' {
\time 4/4
\partial 2 g2 |
g1 |
\set Timing.measurePosition = #(ly:make-moment -2 4)
g2 |
g1 |
}
Polyphonic music compiles fine but I get a barcheck warning:
\version "2.15.36"
\new Staff <<
\new Voice = "first" \relative c'' {
\time 4/4
\partial 2 g2 |
g1 |
\set Timing.measurePosition = #(ly:make-moment -2 4)
g2 |
g1 |
}
\new Voice= "second" \relative c' {
\time 4/4
\partial 2
c2 |
c1 |
\set Timing.measurePosition = #(ly:make-moment -2 4)
c2 |
c1 |
}
>>
The warning is:
warning: barcheck failed at: -1/2
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Flatten a tie without hardcoding control points?
James On 22 April 2012 04:50, James Harkins wrote: > At Sat, 21 Apr 2012 11:24:50 +0100, > James wrote: >> If you can come up with a simple example, we (or you even) could add >> it to the LilyPond snippet repository > > Like this, perhaps? I can add it if this looks OK. I guess - I am no judge, but it seems ok. However I would, if possible add some 'mark up' text somewhere so someone can see the difference without having to read the code separately. For example see: http://lsr.dsi.unimi.it/LSR/Item?id=375 james ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
