Hu Haipeng wrote:
this doesn't work at all.
The hidden breathe sign strangely leaves an apostrophe like sign
This apostrophe is the breathe glyph; so I suppose the #'transparent
override wasn't being effective. My workaround did work for your snippet
(as my attachment for sighted read
Dear Robin,
> It is as if the arpeggio code doesn't notice the staff change.
> Here is a workaround which doesn't prevent a collision but disguises it.
> Insert a transparent breathing sign after s2 in the right hand:
> \once \override BreathingSign #'transparent = ##t \breathe
Thanks, but unfo
Hu Haipeng wrote:
the arpeggio sign collides with the a'4 natural of the treble
It is as if the arpeggio code doesn't notice the staff change.
Here is a workaround which doesn't prevent a collision but disguises it.
Insert a transparent breathing sign after s2 in the right hand:
Hello,
I'm coming to the final adjustment of my overture while a bug troubles me so
much. In the below harp excerpt, the arpeggio sign collides with the a'4
natural of the treble.
Regards
Haipeng
\version "2.13.57"
\paper {
ragged-right = ##t
}
upper = \relative c'' {
\cl
Hi Jay, hi Neil,
All of this conversation has been added as
http://code.google.com/p/lilypond/issues/detail?id=601
I've been myself experiencing similar problems with cross-staff
arpeggios, because I use the following trick in my piano parts:
I remove the "Time_signature_engraver" from the Staff
Great! Thanks that worked wonderfully. Thanks!
On Fri, Mar 28, 2008 at 2:41 PM, Neil Puttock <[EMAIL PROTECTED]> wrote:
> Hi Jay,
>
> I've noticed this happening recently. As a workaround I've been
> setting #'infinite-spacing-height = ##t whenever it occurs.
>
> Here's a related example with o
Hi Jay,
I've noticed this happening recently. As a workaround I've been
setting #'infinite-spacing-height = ##t whenever it occurs.
Here's a related example with one stave and two voices where the
arpeggio collides with the time signature:
\version "2.11.42"
\paper { ragged-right = ##t }
\new St
When using cross staff arpeggios a collision can occur if accidentals
cause the arpeggio to be moved to the left too much.
(Possible related issue: 556)
Thanks!
-Jay
\version "2.11.42"
\paper
{
ragged-right = ##t
}
\book
{
\new PianoStaff
<<
\set PianoStaff.connectArpeggios = ##
Werner LEMBERG escreveu:
>> nowadays, I push to the hwn branch, which I occasionally sync with
>> master.
>
> Why that? Such kind of bug fixes isn't experimental, isn't it?
because I'm lazy. Pushing a single commit to a different branch means
I have to check out that branch, cherry pick, recompi
> nowadays, I push to the hwn branch, which I occasionally sync with
> master.
Why that? Such kind of bug fixes isn't experimental, isn't it?
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-li
Werner LEMBERG escreveu:
>> I fixed this,
>>
>> http://code.google.com/p/lilypond/issues/detail?id=255
>
> Did you? I miss it in git.
nowadays, I push to the hwn branch, which I occasionally sync with
master.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond
> I fixed this,
>
> http://code.google.com/p/lilypond/issues/detail?id=255
Did you? I miss it in git.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Jay Anderson escreveu:
> I see that issue 10 is closed
> (http://code.google.com/p/lilypond/issues/detail?id=10). However, I'm
> still seeing similar behavior. The attached is from the actual score.
> If I take out the accidentals it looks right. I can also remove the
> acciacatura from the low voi
I see that issue 10 is closed
(http://code.google.com/p/lilypond/issues/detail?id=10). However, I'm
still seeing similar behavior. The attached is from the actual score.
If I take out the accidentals it looks right. I can also remove the
acciacatura from the low voice to keep the arpeggio on the c
14 matches
Mail list logo
