Folks,
How about: [... very elegant solution ...]
While Harm's solution is great, I'm under the impression that it
shouldn't be needed, i.e., that LilyPond's behaviour classifies as a
bug. I tried to boil the example down to its essentials:
\version "2.20.0"
\new PianoStaff
<<
\new
Folks,
How about: [... very elegant solution ...]
While Harm's solution is great, I'm under the impression that it
shouldn't be needed, i.e., that LilyPond's behaviour classifies as a
bug. I tried to boil the example down to its essentials:
\version "2.20.0"
\new PianoStaff
<<
\new
Stefan, you wrote 25/12/2020 21:56:18
Subject: Re: how to move a clef horizontally
Dear Thomas and Kieran,
thanks for Your replies.
It seems, that the solution of Thomas works better for me.
I would like to know what
\once \override PianoStaff.NoteColumn.force-hshift = 1.5
does.
The best
Dear Thomas and Kieran,
thanks for Your replies.
It seems, that the solution of Thomas works better for me.
I would like to know what
> \once \override PianoStaff.NoteColumn.force-hshift = 1.5
>
does.
Thanks,
Stefan
Am Do., 24. Dez. 2020 um 23:51 Uhr schrieb Thomas Morley <
Am Mi., 23. Dez. 2020 um 15:25 Uhr schrieb Stefan Thomas
:
>
> Dear community,
> I would like to know, how I can avoid the collision between the treble clef
> and the note b in the below quoted example:
> % SNIP
> \version "2.20.0"
> global = { \key e \major \time 4/4 }
> Up = { \change
Hi Stefan,
Not sure if you found a solution yet?
Here’s one possibility.
Hope it helps!
Kieren.
% SNIP
\version "2.20.0"
global = { \key e \major \time 4/4 }
Up = { \change Staff="upper" \voiceTwo }
Down = { \change Staff="lower" \voiceOne }
upper = {
\clef "bass"
\global
dis'4
Dear community,
I would like to know, how I can avoid the collision between the treble clef
and the note b in the below quoted example:
% SNIP
\version "2.20.0"
global = { \key e \major \time 4/4 }
Up = { \change Staff="upper" \stemDown }
Down = { \change Staff="lower" \stemUp }
upper = {
