I would be a happy man if the notorious Issue 34 could be resolved. I
spend a lot of time having to put grace note spacers in complex scores
to get the vertical alignment working. Each one I do, I wish I knew
enough about lilypond internals to contribute a fix. It's not clear to
me why this one is
Le 12/10/2020 à 08:46, Martín Rincón Botero a écrit :
Thanks for the link Jean. 8 years old issue? Ouch!
We work hard to fix all bugs found in LilyPond. Sometimes that's just
difficult, and sometimes we just have too many of them. Also, LilyPond
is so complex that nobody understands all of i
> Sorry to hear that… I guess there’s always my hand-crafted method. =)
Nothing else seems to do the job :-).
www.martinrinconbotero.com
On 12. Oct 2020, 16:03 +0200, Kieren MacMillan ,
wrote:
>
> Sorry to hear that… I guess there’s always my hand-crafted method. =)
Hi Martín,
> I guess a MWE doesn't always point you in the right direction. The MWE works
> great. This is how Harm's solution looks in its real context:
Sorry to hear that… I guess there’s always my hand-crafted method. =)
Cheers,
Kieren.
Kieren MacMillan, co
I guess a MWE doesn't always point you in the right direction. The MWE
works great. This is how Harm's solution looks in its real context:
[image: image.png]
Adding or deleting \temporary and playing with different values for
Score.SpacingSpanner.common-shortest-duration and
Score.GraceSpacing.com
Hi all,
Here’s what looks best to me:
%%%
\version "2.21.2"
foo = {
\newSpacingSection
\temporary \override Score.SpacingSpanner.strict-note-spacing = ##t
\temporary \override Score.SpacingSpanner.common-shortest-duration =
#(ly:make-moment 1/20)
\temporary \override Score.GraceSpacing.comm
No matter what value I try, the accidental of the grace note collides in
the score :-(.
[image: image.png]
Am Mo., 12. Okt. 2020 um 15:44 Uhr schrieb Martín Rincón Botero <
martinrinconbot...@gmail.com>:
> ah, \newSpacingSection was missing :-).
>
> www.martinrinconbotero.com
> On 12. Oct 2020,
yep, that doesn’t work for one measure
www.martinrinconbotero.com
On 12. Oct 2020, 15:37 +0200, Kieren MacMillan ,
wrote:
> Hi Martín,
>
> > Thanks for the idea, but strict-note-spacing causes all types of collisions
> > in my score (although it works perfectly for my MWE).
>
> So why not just o
Oh, because uniform-stretching can be only can only be changed for the whole
score, I believed it’s the same for strict-note-spacing. I’ll try that.
www.martinrinconbotero.com
On 12. Oct 2020, 15:37 +0200, Kieren MacMillan ,
wrote:
> Hi Martín,
>
> > Thanks for the idea, but strict-note-spacing
ah, \newSpacingSection was missing :-).
www.martinrinconbotero.com
On 12. Oct 2020, 15:43 +0200, Thomas Morley , wrote:
> Am Mo., 12. Okt. 2020 um 15:40 Uhr schrieb Martín Rincón Botero
> :
> >
> > Oh, because uniform-stretching can be only can only be changed for the
> > whole score, I believed
Am Mo., 12. Okt. 2020 um 15:40 Uhr schrieb Martín Rincón Botero
:
>
> Oh, because uniform-stretching can be only can only be changed for the whole
> score, I believed it’s the same for strict-note-spacing. I’ll try that.
>
> www.martinrinconbotero.com
> On 12. Oct 2020, 15:37 +0200, Kieren MacMill
Hi Martín,
> Thanks for the idea, but strict-note-spacing causes all types of collisions
> in my score (although it works perfectly for my MWE).
So why not just override it for that measure? ;)
Cheers,
Kieren.
Kieren MacMillan, composer (he/him/his)
‣ website:
>
> How about:
>
> \layout {
> \context {
> \Score
> \override SpacingSpanner.strict-note-spacing = ##t
> \override SpacingSpanner.common-shortest-duration = #(ly:make-moment
> 1/20)
> \override GraceSpacing.common-shortest-duration = #(ly:make-moment
> 1/64)
> }
> }
>
> <<
>
Harm,
> How about:
WOW! Nicely done.
Kieren.
Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info
Am Mo., 12. Okt. 2020 um 12:13 Uhr schrieb Martín Rincón Botero
:
>
> Dear Kieren,
>
> thank you for that suggestion. Albeit tedious having to fix each note
> manually like this, it works!
>
> Am So., 11. Okt. 2020 um 21:26 Uhr schrieb Kieren MacMillan
> :
>>
>> Hi Martín,
>>
>> > Anyways, I coul
Dear Kieren,
thank you for that suggestion. Albeit tedious having to fix each note
manually like this, it works!
Am So., 11. Okt. 2020 um 21:26 Uhr schrieb Kieren MacMillan <
kieren_macmil...@sympatico.ca>:
> Hi Martín,
>
> > Anyways, I couldn't make use of any of your suggestions. I couldn't
>
I think the engines are completely different, but at least it shows that
other programs can do it. Not that this means anything.
Actually it would be interesting to hear from the advanced developers
exactly why, in a nutshell, this presents apparently insurmountable
difficulties. That may help
FWIW, MuseScore seems to get this right. Perhaps its corresponding part of the
code (wherever it might hide) could serve as inspiration for a fix for
Lilypond? —Please excuse my ignorance if this is technically nonsense! :-).
www.martinrinconbotero.com
On 12. Oct 2020, 09:04 +0200, Andrew Bernar
I would be a happy man if the notorious Issue 34 could be resolved. I
spend a lot of time having to put grace note spacers in complex scores
to get the vertical alignment working. Each one I do, I wish I knew
enough about lilypond internals to contribute a fix. It's not clear to
me why this one is
Thanks for the link Jean. 8 years old issue? Ouch!
www.martinrinconbotero.com
On 11. Oct 2020, 21:59 +0200, Jean Abou Samra , wrote:
> > Using \override Score.SpacingSpanner.strict-grace-spacing = ##t seems
> > only useful when no grace notes are used immediately after the bar
> > line and no acci
On 11/10/2020 21:26, Kieren MacMillan wrote:
Note that I had to unfold the \repeat in the lower staff, in order to easily
apply the tweak to the correct moment. This is one of the [many!] reasons I use
the edition-engraver: you can inject the tweak at an exact moment, regardless
of how the
Using \override Score.SpacingSpanner.strict-grace-spacing = ##t seems
only useful when no grace notes are used immediately after the bar
line and no accidentals are used, which seems like a function for a
very limited use case
This is a known issue:
https://gitlab.com/lilypond/lilypond/-/issu
Hi Martín,
> Anyways, I couldn't make use of any of your suggestions. I couldn't figure
> out how to apply the mentioned tweaks.
Here’s one possibility:
\version "2.20.0"
fixa = \tweak NoteColumn.X-offset #-3 \etc
fixb = \tweak NoteColumn.X-offset #-2 \etc
fixc = \tweak Accidental.X-exten
That’s not exactly what I meant… =)
Yes, lol, I noticed that after reading about the edition-engraver.
Interestingly, the edition-engraver reminds me of Abjad's modus operandi,
which I'm learning at the moment.
Anyways, I couldn't make use of any of your suggestions. I couldn't figure
out how to
Hi Martín,
> I didn’t know the edition-engraver manages the issue.
That’s not exactly what I meant… =)
You can adjust the spacing "inline" [p.s. Next time, send an MWE, and I’d
actually show you how!], but I find it useful and helpful to put all my tweaks
in an edition — then, when newer vers
Thank you for your quick answer! I’ll try that! I didn’t know the
edition-engraver manages the issue.
www.martinrinconbotero.com
On 11. Oct 2020, 19:07 +0200, Kieren MacMillan ,
wrote:
> Hi Martín,
>
> > I wanted to ask how do you deal with grace notes (not immediately after the
> > bar line) i
Hi Martín,
> I wanted to ask how do you deal with grace notes (not immediately after the
> bar line) incorrectly taking too much horizontal space from normal notes.
Tweaks (X-extent, extra-spacing-width, etc.).
Specifically: using the edition-engraver.
Hope that helps!
Kieren.
_
Hello all,
I wanted to ask how do you deal with grace notes (not immediately after the
bar line) incorrectly taking too much horizontal space from normal notes.
Using \override Score.SpacingSpanner.strict-grace-spacing = ##t seems only
useful when no grace notes are used immediately after the bar
28 matches
Mail list logo
