Unexpected placement of accidental
Hello,
Please see the example below. I tried running it in 2.22 and 2.23 as well,
and got the same result. Am I missing an obvious reason that the c-natural
accidental is placed so far to the left?
\version "2.24.0"
\language "english"
\relative {
\clef bass
\key a \major
% unexpected placement of "c-natural" accidental
s4*3
% expected placement shown here
\break
}
Thanks,
-Ahanu
Re: Frescobaldi & edition engraver
Hello, Le 05/01/2023 à 01:21, Michael Dietz a écrit : Hi, after a few years, I come back to LilyPond. I just installed the latest stable version 2.24. Thanks a lot for it. Working on Ubuntu 22.04, I now have two issues: - How to use Frescobaldi (I really enjoyed it but it crashes on startup) - How to get the latest edition engraver (I heavily used it) 1. Frescobaldi While Frescobaldi is still in the Ubuntu packages, it does crash when starting it with the following message: Traceback (most recent call last): File "/usr/share/frescobaldi/frescobaldi_app/qpageview/highlight.py", line 209, in paintEvent super().paintEvent(ev) # first paint the contents File "/usr/share/frescobaldi/frescobaldi_app/qpageview/shadow.py", line 43, in paintEvent rect = ev.rect().adjusted(-width, -width, width / 2, width / 2) TypeError: adjusted(self, int, int, int, int): argument 1 has unexpected type 'float' I tried to fix all those int/float type issues but after fixing a lot of them, I finally gave up. Is there a recipe to install and use Frescobaldi on Ubuntu? Flatpak. https://github.com/frescobaldi/frescobaldi/issues/1433#issuecomment-1132051619 (This is really getting on my nerves, I can't believe this Ubuntu update is still stuck after 9 months of Ubuntu Jammy “stable LTS” with an unusable Frescobaldi...) 2. OpenLilyLib I still have a local copy of OpenLilyLib (with master on 75adb418 from 2015-07-07). Is there a more recent version of it and in particular the edition engraver? In a Git repository, you can normally update by simply running $ git pull Best, Jean OpenPGP_signature Description: OpenPGP digital signature
Frescobaldi & edition engraver
Hi, after a few years, I come back to LilyPond. I just installed the latest stable version 2.24. Thanks a lot for it. Working on Ubuntu 22.04, I now have two issues: - How to use Frescobaldi (I really enjoyed it but it crashes on startup) - How to get the latest edition engraver (I heavily used it) 1. Frescobaldi While Frescobaldi is still in the Ubuntu packages, it does crash when starting it with the following message: Traceback (most recent call last): File "/usr/share/frescobaldi/frescobaldi_app/qpageview/highlight.py", line 209, in paintEvent super().paintEvent(ev) # first paint the contents File "/usr/share/frescobaldi/frescobaldi_app/qpageview/shadow.py", line 43, in paintEvent rect = ev.rect().adjusted(-width, -width, width / 2, width / 2) TypeError: adjusted(self, int, int, int, int): argument 1 has unexpected type 'float' I tried to fix all those int/float type issues but after fixing a lot of them, I finally gave up. Is there a recipe to install and use Frescobaldi on Ubuntu? 2. OpenLilyLib I still have a local copy of OpenLilyLib (with master on 75adb418 from 2015-07-07). Is there a more recent version of it and in particular the edition engraver? Best, Michael
Re: weird fonts in volta endings
Le 04/01/2023 à 22:42, Flaming Hakama by Elaine a écrit :
Hi,
I was hoping someone could help me figure out how to fix this font issue.
For quite some number of years,
I've been using this function that prints custom text for volta ending
labels.
But now it is producing strange results.
The image from the below MWE is attached, it shows that some of the
letters are being rendered in a much smaller and different font than
the rest. This includes letters f, s, r, n, m
The font you are seeing is LilyPond's standard music font, the Feta
font, and these are the letters used for dynamics.
The volta text is normally a number, and Feta has its own numbers
for that (which are similar to fingerings), therefore the text
under a volta bracket is typeset using a music font. If that
font doesn't contain any glyph for a particular letter, you
get a fallback text font. This is controlled through the font-encoding
property: fetaText → music font, latin1 → text font. Try
\version "2.24.0"
voltaDoubleCustom = #(define-music-function (repMusicCommon repEndingA
repMusicA repEndingB repMusicB) (ly:music? markup? ly:music? markup?
ly:music?) #{
\set Score.repeatCommands = #'(start-repeat)
$repMusicCommon
\set Score.repeatCommands =
#(list (list 'volta
#{ \markup \override #'(font-encoding . latin1)
#repEndingA #}))
$repMusicA
\set Score.repeatCommands =
#(list (list 'volta #f)
'end-repeat
(list 'volta
#{ \markup \override #'(font-encoding . latin1)
#repEndingB #}))
$repMusicB
\set Score.repeatCommands = #'((volta #f))
#})
{
\voltaDoubleCustom
{ c''8 8 8 8 8 8 8 8 }
\markup "first"
{ c''8 8 8 8 8 8 8 8 }
\markup "second"
{ c''8 8 8 8 8 8 8 8 }
}
There is a much simpler way, though:
\version "2.24.0"
{
\repeat volta 2 {
c''8 8 8 8 8 8 8 8
\alternative {
\volta 1 {
\once \override Score.VoltaBracket.font-encoding = #'latin1
\once \override Score.VoltaBracket.text = "first"
c''8 8 8 8 8 8 8 8
}
\volta 2 {
\once \override Score.VoltaBracket.font-encoding = #'latin1
\once \override Score.VoltaBracket.text = "second"
c''8 8 8 8 8 8 8 8
}
}
}
}
Best,
Jean
OpenPGP_signature
Description: OpenPGP digital signature
weird fonts in volta endings
Hi,
I was hoping someone could help me figure out how to fix this font issue.
For quite some number of years,
I've been using this function that prints custom text for volta ending
labels.
But now it is producing strange results.
The image from the below MWE is attached, it shows that some of the letters
are being rendered in a much smaller and different font than the rest.
This includes letters f, s, r, n, m
\version "2.22.0"
voltaDoubleCustom = #(define-music-function (repMusicCommon repEndingA
repMusicA repEndingB repMusicB) (ly:music? markup? ly:music? markup?
ly:music?) #{
\set Score.repeatCommands = #'(start-repeat)
$repMusicCommon
\set Score.repeatCommands = #(list (list 'volta repEndingA))
$repMusicA
\set Score.repeatCommands = #(list (list 'volta #f) 'end-repeat (list
'volta repEndingB))
$repMusicB
\set Score.repeatCommands = #'((volta #f))
#})
{
\voltaDoubleCustom
{ c''8 8 8 8 8 8 8 8 }
\markup "first"
{ c''8 8 8 8 8 8 8 8 }
\markup "second"
{ c''8 8 8 8 8 8 8 8 }
}
Please let me know if you have any advice.
Thanks,
Elaine Alt
415 . 341 .4954 "*Confusion is
highly underrated*"
ela...@flaminghakama.com
Producer ~ Composer ~ Instrumentalist ~ Educator
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
On Wed, Jan 4, 2023 at 9:00 AM wrote:
> Send lilypond-user mailing list submissions to
> lilypond-user@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> or, via email, send a message with subject or body 'help' to
> lilypond-user-requ...@gnu.org
>
> You can reach the person managing the list at
> lilypond-user-ow...@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
> Today's Topics:
>
>1. Allowing a collision (Paul Hodges)
>2. Re: Allowing a collision (Jean Abou Samra)
>
>
>
> -- Forwarded message --
> From: Paul Hodges
> To: lilypond-user Mailinglist
> Cc:
> Bcc:
> Date: Wed, 4 Jan 2023 16:24:40 +
> Subject: Allowing a collision
> I have a score which has two staves, for unrelated instruments. To
> reproduce the composer's notation, I occasionally need to join the stems of
> simultaneous notes on the two staves.
>
> In a piano staff this is catered for using the \crossStaff command.
> However, in my case this is inapplicable; so I am trying either to lengthen
> the stems on one staff or to draw a line joining them, using \markup.
>
> However, whichever method I try, LilyPond prevents the extended stem/line
> from reaching note on the other staff, because it prevents the collision
> from happening.
>
> Is there a way to turn off the collision avoidance for this specific item
> in isolation?
>
> Regards,
> Paul
>
>
>
> -- Forwarded message --
> From: Jean Abou Samra
> To: Paul Hodges , lilypond-user Mailinglist <
> lilypond-user@gnu.org>
> Cc:
> Bcc:
> Date: Wed, 4 Jan 2023 17:27:31 +0100
> Subject: Re: Allowing a collision
> Le 04/01/2023 à 17:24, Paul Hodges a écrit :
> > I have a score which has two staves, for unrelated instruments. To
> > reproduce the composer's notation, I occasionally need to join the
> > stems of simultaneous notes on the two staves.
> >
> > In a piano staff this is catered for using the \crossStaff command.
> > However, in my case this is inapplicable; so I am trying either to
> > lengthen the stems on one staff or to draw a line joining them, using
> > \markup.
> >
> > However, whichever method I try, LilyPond prevents the extended
> > stem/line from reaching note on the other staff, because it prevents
> > the collision from happening.
> >
> > Is there a way to turn off the collision avoidance for this specific
> > item in isolation?
>
>
> The real question is: why is \crossStaff inapplicable for you?
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
Re: Allowing a collision
Because although I've used it a lot, I set it up initially a year ago and had forgotten that I'd had to add the Span_stem_engraver to the PianoStaff context. Once reminded of that, I can of course see that it can equally be added to the StaffGroup context that I'm using. Thanks, Paul From: Jean Abou Samra To: Paul Hodges , lilypond-user Mailinglist Sent: 04/01/2023 16:27 Subject: Re: Allowing a collision Le 04/01/2023 à 17:24, Paul Hodges a écrit : > I have a score which has two staves, for unrelated instruments. To > reproduce the composer's notation, I occasionally need to join the > stems of simultaneous notes on the two staves. > > In a piano staff this is catered for using the \crossStaff command. > However, in my case this is inapplicable; so I am trying either to > lengthen the stems on one staff or to draw a line joining them, using > \markup. > > However, whichever method I try, LilyPond prevents the extended > stem/line from reaching note on the other staff, because it prevents > the collision from happening. > > Is there a way to turn off the collision avoidance for this specific > item in isolation? The real question is: why is \crossStaff inapplicable for you?
Re: Allowing a collision
Le 04/01/2023 à 17:24, Paul Hodges a écrit : I have a score which has two staves, for unrelated instruments. To reproduce the composer's notation, I occasionally need to join the stems of simultaneous notes on the two staves. In a piano staff this is catered for using the \crossStaff command. However, in my case this is inapplicable; so I am trying either to lengthen the stems on one staff or to draw a line joining them, using \markup. However, whichever method I try, LilyPond prevents the extended stem/line from reaching note on the other staff, because it prevents the collision from happening. Is there a way to turn off the collision avoidance for this specific item in isolation? The real question is: why is \crossStaff inapplicable for you? OpenPGP_signature Description: OpenPGP digital signature
Allowing a collision
I have a score which has two staves, for unrelated instruments. To reproduce the composer's notation, I occasionally need to join the stems of simultaneous notes on the two staves. In a piano staff this is catered for using the \crossStaff command. However, in my case this is inapplicable; so I am trying either to lengthen the stems on one staff or to draw a line joining them, using \markup. However, whichever method I try, LilyPond prevents the extended stem/line from reaching note on the other staff, because it prevents the collision from happening. Is there a way to turn off the collision avoidance for this specific item in isolation? Regards, Paul
Feathered beams issue
When I feather these beams, the third beam is simply absent. I suppose this is a bug (or an undocumented "limitation"?), but is there a practical workaround? I guess I also need to make the beam thickness less so that the structure becomes more visible, though I suspect that will be less of a problem when I add the \featherDurations command. Regards, Paul FeatheredBeamsIssue.pdf Description: Adobe PDF document FeatheredBeamsIssue.ly Description: Binary data
