bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bad clef change collision when alternating piano staves


From: Malte Meyn
Subject: Re: Bad clef change collision when alternating piano staves
Date: Mon, 9 Oct 2017 10:09:40 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0

Hi Ophir,

this bug hasn’t been fixed yet but there’s a cleaner solution than tweaking X-offsets and X-extents: Temporarily use another voice.

Cheers,
Malte

\version "2.18.2"

\new PianoStaff <<
  \new Staff = "RH" \relative a' {
    \clef treble
    <<
      \new Voice {
        s2
        a8[ b c d]
      }
      \new Voice {
        a8
        \change Staff = "LH" \clef treble a_1
        \change Staff = "RH"              a
        \change Staff = "LH"              a_2
        \clef bass
        cis,, d e f
      }
    >>
    e''2
  }
  \new Staff = "LH" \relative a, {
    \clef bass
    a8 s2..
    e'2
  }
>>

Am 09.10.2017 um 05:23 schrieb Ophir Lifshitz:
Hello,

Can someone please triage this bug?

Thanks again,
Ophir

On Sun, Jan 31, 2016 at 4:57 PM, Ophir Lifshitz <address@hidden>
wrote:

Hello,

Would it be possible to triage this bug I reported 3 months ago?

Thanks,
Ophir

On Fri, Jan 1, 2016 at 10:03 AM, Ophir Lifshitz <
address@hidden> wrote:

Hello again,

Has anyone been able to triage this bug yet?

Thanks,
Ophir

On Wed, Oct 28, 2015 at 11:31 AM, Ophir Lifshitz <
address@hidden> wrote:

I was browsing through recent bugs on the new tracker and found this
one: http://sourceforge.net/p/testlilyissues/issues/4642/

I wonder whether it is related?

Ophir

On Tue, Oct 27, 2015 at 6:15 PM, Ophir Lifshitz <
address@hidden> wrote:

And so in that case, probably something like \hideNotes r ...
\unHideNotes will be sufficient.

Ophir

On Tue, Oct 27, 2015 at 6:10 PM, Ophir Lifshitz <
address@hidden> wrote:

Hello again,

Yes, thank you Pierre. I believe that will work temporarily, but I'm
still mostly convinced it's a bug that needs to be fixed.

For example, change the space s4. near the bottom of the file between
three eighth rests r r r (clef change is – mostly – properly spaced)
and two rests plus a space r r s (collision). It seems that Lilypond
can't detect the RH's note's presence in the 4th position of the LH staff,
and it only detects the presence of a LH note/rest starting somewhere in
the 4th position.

Ophir

On Tue, Oct 27, 2015 at 6:01 PM, Pierre Perol-Schneider <
address@hidden> wrote:

Oops, sorry, too fast reading...

How about :

\version "2.19.22"
\new PianoStaff <<
     \new Staff = "RH" \relative a' {
         \clef treble
         a8
         \change Staff = "LH" \clef treble a_1
         \change Staff = "RH"              a
         \change Staff = "LH"
         \tweak X-extent #'(0 . -2)
         \tweak X-offset #-3.3 a_2
         \clef bass
         \change Staff = "RH"
         \tweak X-extent #'(-7 . 1.3) a
     }
     \new Staff = "LH" \relative a, {
         \clef bass
         a8 s4. cis8_3
     }




2015-10-27 22:37 GMT+01:00 Ophir Lifshitz <address@hidden
:

Hi Pierre,

I'm afraid that override only makes the issue worse by shifting the
clef left. I might have been unclear, but the clef change belongs after
note 2 and directly before the sharped note 3, and not in the small space
between notes 1 and 2. Shifting it left makes it look like note 2 is
notated in bass clef, but it is not. Ultimately more space is needed on the
staff between notes 2 and 3 to fit the bass clef before note 3.

Ophir

On Tue, Oct 27, 2015 at 5:28 PM, Pierre Perol-Schneider <
address@hidden> wrote:

Hi Ophir,

Try :
\once\override Staff.Clef.X-extent = #'(0 . 3.5) \clef bass

Cheers,
~Pierre

2015-10-27 22:05 GMT+01:00 Ophir Lifshitz <
address@hidden>:

Hello all,

I believe there is a bug in making space for clef changes. You can
find the
MWE here: http://lilybin.com/gs2oks/7

The notes labeled 1 and 2 on the lower LH staff are both notated
in treble
clef. But because space wasn't made for the bass clef change, the
bass clef
misleadingly appears slightly before note 2. I would have instead
expected
to see a lot of space made between notes 2 and 3 where the clef
can fit
properly. The clef change before note 1 shows that Lilypond can
indeed make
space for clef changes.

If not a bug, what is the best way to fix the collision?

Thanks in advance,
Ophir

P.S. The MWE was gradually simplified (1 <
http://lilybin.com/gs2oks/1> 2
<http://lilybin.com/gs2oks/2> 3 <http://lilybin.com/gs2oks/3> 4
<http://lilybin.com/gs2oks/4> current <http://lilybin.com/gs2oks/7>)
in
case anyone is curious for the source
<https://www.youtube.com/watch?v=3Dw1Huh_Tfg&feature=
youtu.be&t=2m51s>.
Also attached are the source and an image in case of linkrot.

_______________________________________________
bug-lilypond mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-lilypond










_______________________________________________
bug-lilypond mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-lilypond




reply via email to

[Prev in Thread] Current Thread [Next in Thread]