Thomas Morley-2 wrote
> No idea why alterBroken's not working, too late here to investigate.
>
> Anyway, below may give you a starting point for a different coding:
>
> \override Hairpin.after-line-breaking =
> #(lambda (grob)
> (let* ((orig (ly:grob-original grob))
>
2018-05-17 15:47 GMT+02:00 foxfanfare :
> Kieren MacMillan wrote
>> Hi foxfanfare,
>>
>>> Is it possible to adjust the padding of a broken hairpin after a line
>>> break?
>>
>> http://lilypond.org/doc/v2.18/Documentation/notation/modifying-bro
Kieren MacMillan wrote
> Hi foxfanfare,
>
>> Is it possible to adjust the padding of a broken hairpin after a line
>> break?
>
> http://lilypond.org/doc/v2.18/Documentation/notation/modifying-broken-spanners
>
> Hope that helps!
> Kieren.
> __
Hi foxfanfare,
> Is it possible to adjust the padding of a broken hairpin after a line break?
http://lilypond.org/doc/v2.18/Documentation/notation/modifying-broken-spanners
Hope that helps!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.i
Hi,
Is it possible to adjust the padding of a broken hairpin after a line break?
For instance:
\new PianoStaff
<<
\relative c' {
c4 d e f
\break
g f e d
}
\new Dynamics {
\override PianoStaff.Hairpin.to-barline = ##f
\override PianoStaff.Hairpin.after-li
Hi,
On Wed, Jul 2, 2014 at 3:37 AM, Thomas Morley
wrote:
>
>
> Overriding the 'after-line-breaking property will work, though.
> (Too lazy to turn it into a music-function)
>
>
Yes, it does. This is an unfortunate limitation of \alterBroken--the
spanner may not be broken at the time the proper
ntweaked output of your code is _exactly_ what I want to see
for a broken Hairpin.
Nevertheless, the reason alterBroken does not work here, seems to be
that during an override for Hairpin.height no broken Spanner is
recognized. See the output of this test-code:
\version "2.18.2"
\paper
2014-07-02 4:37 GMT+02:00 Javier Ruiz-Alma :
> The 2nd Hairpin.height value in \alterBroken seems to get ignored. Is
> this a limitation, or my bad syntax?
>
None of them. I thing it could be considered as a bug.
Cheers,
Pierre
___
lilypond-user mailin
The 2nd Hairpin.height value in \alterBroken seems to get ignored. Is this a
limitation, or my bad syntax?I'm dealing with a broken multi-bar hairpin. Not
being able to adjust heights per segment results in either too-narrow first or
too-wide second hairpin segment.
\version "2.18.2"
\paper
s me I won't
> run into quite as extreme a situation as your example :)
>
I always test with most extreme examples, hoping to notice all possible
problems. :D
> Checking my just-bought copy of Gould, I find on pg. 104 the rule that a
> broken hairpin should stop on the barline, wit
nd on pg. 104 the rule that a
broken hairpin should stop on the barline, with an example involving a key
change at the line break. Maybe LilyPond's behavior should be reported as a
bug (I couldn't find it listed, anyway) with your function as a workaround?
(One tiny thing: Mike went to
harm6 wrote:
>
> ...
>
The same. Attaching the file.
http://old.nabble.com/file/p32419760/testBrokenHairpin.ly
testBrokenHairpin.ly
--
View this message in context:
http://old.nabble.com/shorten-a-broken-hairpin-at-a-linebreak--tp32343028p32419760.html
Sent from the Gnu - Lilypo
s to Mike Solomon and David Nalesnik
%
http://old.nabble.com/shorten-a-broken-hairpin-at-a-linebreak--td32343028.html
#(define (last-bar grob)
;; return the X-coordinate of the last barline on a line
(let* ((sys (ly:grob-system grob))
(array (ly:grob-object sys 'all-elements)
On Thu, Sep 1, 2011 at 2:52 PM, harm6 wrote:
>
>
> Hi David,
>
> that's it !!
>
> I had experimented with the hairpin-origin, but I didn't manage to
> introduce
> it correct.
>
> Once more: thanks a lot!
>
You're very welcome!
___
lilypond-user mai
Once more: thanks a lot!
Harm
--
View this message in context:
http://old.nabble.com/shorten-a-broken-hairpin-at-a-linebreak--tp32343028p32382183.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-use
On Thu, Sep 1, 2011 at 2:22 PM, David Nalesnik wrote:
>
> Hi again, Harm --
>
>
In my eagerness, I did a rather poor job of cutting and pasting, so I'm
attaching the file :)
David
new-hairpin1.ly
Description: Binary data
___
lilypond-user mailing list
Hi again, Harm --
> One point left: I want each diminuendo of the broken siblings to be
> increased up to the barline.
>
Keep your fingers crossed, but I think I've located the problem...
You need to take into account the origin of the hairpin. So:
\version "2.14.2"
#(define (has-interface?
Hi Mike, hi David,
thanks a lot for all your help! You're great.
Best,
Harm
--
View this message in context:
http://old.nabble.com/shorten-a-broken-hairpin-at-a-linebreak--tp32343028p32381613.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabbl
Hi Harm,
> Using David's last-bar-Definition [ . . . ]
>
>
I just wanted to point out that my definition can be shortened a little (by
sorting in order from largest coordinate to smallest):
#(define (last-bar grob)
;; return the X-coordinate of the last barline on a line
(let* ((sys (ly:gr
On Sep 1, 2011, at 7:42 PM, harm6 wrote:
>
>
> Mike Solomon-2 wrote:
>>
>> More control over the length is always achievable by overriding the
>> stencil, as is the solution to the problem you pose above regarding the
>> closing diminuendi.
>>
>>
>
> Hi Mike,
>
> great work on the closing d
epeat unfold 2 { a } \break
% 5
\repeat unfold 8 { a } \break \key fis \major
% 13
\repeat unfold 2 { a } \break \key ees \major
% 15
\repeat unfold 17 {a} a\! \break \key ces\major
% 33 with new hairpin
a1\> a1 \break \key cis\major
% 35
a a\!
}
--
V
On Aug 31, 2011, at 5:30 PM, harm6 wrote:
>
>
> Mike Solomon-2 wrote:
>>
>> Hmm...I thought that after-line-breaking would be called after the bounds
>> were set, but I was wrong.
>>
>> Try:
>>
>> #(define (has-interface? grob interface)
>> (member interface
>> (assoc-get 'interfaces
\relative c' {
\override Hairpin #'stencil = #my-callback
c'1\> c1*5/8 s1*3/8
\break
\key cis\major
d2 e e1*7/8 s1*1/8\!
}
Would any such increased / improved control be feasible in the context
of the solu
On Aug 30, 2011, at 4:28 PM, harm6 wrote:
>
>
> Mike Solomon-2 wrote:
>>
>> How about:
>>
>> \version "2.14.0"
>>
>> #(define (has-interface? grob interface)
>> (member interface
>> (assoc-get 'interfaces
>>(ly:grob-property grob 'meta
>>
>> #(define (find-sys
c'1\< c
\break
\key cis\major
d2 e e1
\break
\key es\major
\time 2/2
f2 g
\break
\key e\major
\time 4/4
a b\!
}
I will try to play around with your settings, hopin
On Tue, Aug 30, 2011 at 9:02 AM, harm6 wrote:
>
>
> David Nalesnik-2 wrote:
> >
> >
> > OK, this should do it!
> >
> > Now all you have to do is call \eraseBrokenHairpin -- no arguments needed
> > -- and it should handle positioning of the whiteout box. I'm guessing
> > that
> > this would be ea
rs?
>
> Best,
> David
>
Hi David,
thanks for your work on my function. I will study the additions and I can
confirm the "tiny trace of hairpins" even if using your hairpin-1.ly
Best,
Harm
--
View this message in context:
http://old.nabble.com/shorten-a-broken-hairpin
On Tue, Aug 30, 2011 at 1:59 AM, Mike Solomon wrote:
>
> How about:
>
>
Mike --
Wow. So that's how it's done!
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On Aug 29, 2011, at 11:56 PM, David Nalesnik wrote:
>
>
> On Mon, Aug 29, 2011 at 4:50 PM, David Nalesnik
> wrote:
>
> \relative c' {
>\override Hairpin #'color = #red
>\key ces\major
>\eraseBrokenHairpin #(list 41 23 15 0 13 0) ;; recast as offsets
> from line-wi
>
> Hi, again --
>
> I'm not sure how to handle the positioning on the first line, hence the
> list of offsets in the input.
>
OK, this should do it!
Now all you have to do is call \eraseBrokenHairpin -- no arguments needed
-- and it should handle positioning of the whiteout box. I'm guessing
>
>
> Not sure about calculating the other end of the whiteout box (from position
> of the barline, I suppose).
>
Hi, again --
More experimenting yielded this, which automates the calculation of the
width of the whiteout stencil. I'm not sure how to handle the positioning
on the first line, henc
On Mon, Aug 29, 2011 at 4:50 PM, David Nalesnik wrote:
>
> \relative c' {
>\override Hairpin #'color = #red
>\key ces\major
>\eraseBrokenHairpin #(list 41 23 15 0 13 0) ;; recast as offsets
> from line-width
>
Oops, sorry -- above comment should use %% instead of ;;
Da
On Mon, Aug 29, 2011 at 3:25 PM, harm6 wrote:
>
>
> harm6 wrote:
> Anyone with a better idea?
>
Hi, Harm --
I've been playing around with your function and experimenting with ways to
automate calculation of the whiteout box extents. I recast it to accept
offsets from the current line-width, so
harm6 wrote:
>
> Hi,
>
> how can I shorten the first part of a broken hairpin to avoid the printing
> under a new KeySignature (or KeyCancellation, TimeSignature etc) at a
> linebreak?
>
> Thanks!
> Harm
>
It could be done this way:
\version "2.14.2&qu
Hi,
how can I shorten the first part of a broken hairpin to avoid the printing
under a new KeySignature (or KeyCancellation, TimeSignature etc) at a
linebreak?
I tried (with no success):
\version "2.14.2"
\pointAndClickOff
\paper { ragged-right = ##f }
lengthHairpinBoth =
#(de
35 matches
Mail list logo
