How do I shift notes in one voice w/o shifting the other?
I searched for a way to shift notes horizontally but when I shift the
half-note chord in the first voice below, it shifts the second eighth-note
in the second voice, forcing it to stay to the right of the half-note. When
I tried adding something to shift the beamed eight-notes to the left, it
shifted only the first eighth-note, continuing to anchor the second to the
right of the half-note.
What I want is for the two eighth-notes to stay to the left, and for the
half-note to appear to the right of it.
This is what I have at the moment, with the shift commented out. (The "#10"
is just an experiment, not necessarily the final value.)
%%%
<<
{
% \once \override NoteColumn.force-hshift = #10
2~|
4\fermata s4 |
}
\\
{
d'8[ b8] s4 |
s4 d4 |
}
>>
\bar "|."
%%%
Re: solved; how to get system separator on both sides
> Yes thank you that works. perhaps could be put in snippet respository? [https://lsr.di.unimi.it/LSR/Item?id=1176](https://lsr.di.unimi.it/LSR/Item?id=1176) signature.asc Description: This is a digitally signed message part
solved; how to get system separator on both sides
Yes thank you that works. perhaps could be put in snippet respository?
On 2023-11-28 02:09, Jean Abou Samra wrote:
I don't think it's in a snippet, but you can do
\version "2.24.2"
\paper {
system-separator-markup = \markup \fill-line { \slashSeparator
\slashSeparator }
}
{ c' \break c' }
Re: Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error
Well, that worked. (I can now continue collating the parts of at least the first movement of Robert Fuchs' 4th string quartet (1916) into score past bar 195 where I left my project... ;) ) Thanks much!! On Tue, Nov 28, 2023 at 5:38 AM Eric wrote: > Well, that’s depressing, I thought I had. I’ll get on that- thanks! > > On Tue, Nov 28, 2023 at 01:51 Jonas Hahnfeld wrote: > >> On Tue, 2023-11-28 at 01:33 -0500, Eric wrote: >> > Installed 2.24.3 -docs using Macports, used convert-ly on a couple of >> > files I'd last worked on in June, and received the following (see >> > attached text file) after trying lilypond on one of those files and >> > adding the -V flag. I know that several solutions have been proposed, >> > including on this list back in June, e.g., but I can't figure out how >> > to apply them in my own case, sorry... >> >> Hi, >> >> your log file says that you are actually running LilyPond 2.24.2, which >> is incompatible with Ghostscript 10.02.1. Please update to the very >> latest version 2.24.3 that contains a fix, either via MacPorts or by >> downloading our official binaries. >> >> Cheers >> Jonas >> >
Re: Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error
Well, that’s depressing, I thought I had. I’ll get on that- thanks! On Tue, Nov 28, 2023 at 01:51 Jonas Hahnfeld wrote: > On Tue, 2023-11-28 at 01:33 -0500, Eric wrote: > > Installed 2.24.3 -docs using Macports, used convert-ly on a couple of > > files I'd last worked on in June, and received the following (see > > attached text file) after trying lilypond on one of those files and > > adding the -V flag. I know that several solutions have been proposed, > > including on this list back in June, e.g., but I can't figure out how > > to apply them in my own case, sorry... > > Hi, > > your log file says that you are actually running LilyPond 2.24.2, which > is incompatible with Ghostscript 10.02.1. Please update to the very > latest version 2.24.3 that contains a fix, either via MacPorts or by > downloading our official binaries. > > Cheers > Jonas >
Re: Extra space before line break before ossia staff
> Is this a bug? Yes , see https://gitlab.com/lilypond/lilypond/-/issues/4263 signature.asc Description: This is a digitally signed message part
Re: forgotten how to get system separator on both sides
I don't think it's in a snippet, but you can do
```
\version "2.24.2"
\paper {
system-separator-markup = \markup \fill-line { \slashSeparator
\slashSeparator }
}
{ c' \break c' }
```
signature.asc
Description: This is a digitally signed message part
Re: Extra space before line break before ossia staff
Solved with \set Staff.explicitKeySignatureVisibility = #end-of-line-invisible
\version "2.24.3"
\layout {
ragged-right = ##t
}
mainKey = {
\key es \major
}
\new StaffGroup {
\new Staff = main \relative {
\mainKey
g'1 |
\break
<<
{ g1 }
\new Staff \with {
alignAboveContext = main
}
{
\set Staff.explicitKeySignatureVisibility = #end-of-line-invisible %%
<-- The solution
\mainKey
g4 f g2 |
}
>>
}
}
Sent with Proton Mail secure email.
On Tuesday, November 28th, 2023 at 09:20, Ole V. Villumsen
wrote:
> It seems to me that when an ossia staff (or similar supplementary staff)
> happens to begin at a line break, Lilypond meaninglessly sets space apart for
> a key signature before the line break even though there is no key signature
> printed there. Is this a bug? Is there a workaround?
>
> The output from the snippet below is in the attachment. At the right end of
> the first staff there is extra space between the bar line and the end of the
> staff.
>
> In C major (no key signature) all is fine, there is no extra space.
>
> \version "2.24.3"
>
> \layout {
> ragged-right = ##t
> }
>
> mainKey = {
> \key es \major
> }
>
> \new StaffGroup {
> \new Staff = main \relative {
> \mainKey
> g'1 |
> \break
> <<
> { g1 }
> \new Staff \with {
> alignAboveContext = main
> }
> {
> \mainKey
> g4 f g2 |
> }
> >>
>
> }
> }
>
> Sent with Proton Mail secure email.
start-ossia-at-line-break.pdf
Description: Adobe PDF document
Extra space before line break before ossia staff
It seems to me that when an ossia staff (or similar supplementary staff)
happens to begin at a line break, Lilypond meaninglessly sets space apart for a
key signature before the line break even though there is no key signature
printed there. Is this a bug? Is there a workaround?
The output from the snippet below is in the attachment. At the right end of the
first staff there is extra space between the bar line and the end of the staff.
In C major (no key signature) all is fine, there is no extra space.
\version "2.24.3"
\layout {
ragged-right = ##t
}
mainKey = {
\key es \major
}
\new StaffGroup {
\new Staff = main \relative {
\mainKey
g'1 |
\break
<<
{ g1 }
\new Staff \with {
alignAboveContext = main
}
{
\mainKey
g4 f g2 |
}
>>
}
}
Sent with Proton Mail secure email.
start-ossia-at-line-break.pdf
Description: Adobe PDF document
