Le samedi 27 mai 2023 à 17:17 -0400, Gregory Evans a écrit :
> Hi Everyone,
> Yes Andrew, that excerpt is from Mahnkopf: good eye!
>
> Thanks Karim, your override is a good step in the right direction for me.
>
> So now I guess what I'm looking for is a way to query the tuplet bracket for
>
Le samedi 27 mai 2023 à 17:38 -0400, msk...@ansuz.sooke.bc.ca a écrit :
> On Sat, 27 May 2023, Jean Abou Samra wrote:
>
> > Are you sure that this is the correct example? That the file chord.ly it
> > uses is the same as the one you sent? That LilyPond is the one you believe
> > and unpatched,
On Sat, 27 May 2023, David Kastrup wrote:
> which contains a delirious number of unbreakable spaces, code \xa0
> instead of \x20 as for a normal, breakable space.
Thanks! Correcting these seems to have fixed the problem, at least for
the moment.
I don't know why the old version needed *some*
On Sat, 27 May 2023, Jean Abou Samra wrote:
> Are you sure that this is the correct example? That the file chord.ly it
> uses is the same as the one you sent? That LilyPond is the one you believe
> and unpatched, etc. ?
Yes, using the chord.ly file I attached to my message, extracted from the
Hi Everyone,
Yes Andrew, that excerpt is from Mahnkopf: good eye!
Thanks Karim, your override is a good step in the right direction for me.
So now I guess what I'm looking for is a way to query the tuplet bracket
for its direction while tweaking the tuplet number.
regards,
greg
On Sat, May
msk...@ansuz.sooke.bc.ca writes:
> Here's a small example showing the problem:
>
> \include "chord.ly"
> music = { 1 }
> { \extractNote #3 \music }
>
> In version 2.21.0 that produces a whole-note rest. In version 2.24.1 with
> Guile 2.2 it gives this error output:
>
> GNU LilyPond 2.24.1
Le samedi 27 mai 2023 à 16:31 -0400, msk...@ansuz.sooke.bc.ca a écrit :
> Here's a small example showing the problem:
>
> \include "chord.ly"
> music = { 1 }
> { \extractNote #3 \music }
>
> In version 2.21.0 that produces a whole-note rest. In version 2.24.1 with
> Guile 2.2 it gives this
Back in 2015 people on the list helped me with extracting notes from
chords, in this thread:
https://lists.gnu.org/archive/html/lilypond-user/2015-09/msg00394.html
The solution from 2015 has broken now, in the transition between versions
2.21.0 and 2.24.1. I think it's because of changes in
I think it's this: that the installation link should be right next to the
download file links.
On Sat, May 27, 2023, 9:44 AM Jean Abou Samra wrote:
>
>
> Le 27 mai 2023 à 00:57, surfnaked a écrit :
>
> Thanks so much. Not sure if he tried all that but we’ll start again.
>
>
>
> You're
> Le 27 mai 2023 à 00:57, surfnaked a écrit :
>
> Thanks so much. Not sure if he tried all that but we’ll start again.
You're welcome. I would actually be quite curious to know what you tried and
where you looked before reaching out to the list. (As the author of
Hello,
in the following example (see attached edited pdf) I'd like to reduce
the distance between the suffixes. It looks like the distance between
the root and the first suffix is smaller than the distances between
the following suffixes.
\version "2.25.5"
\chords{
des:maj7.5+ fis:7.5+.9+.11+
}
Lib Lists wrote:
Replying to myself, as it might help someone else to give me some hints.
I made some progresses following the LSR example here:
https://lsr.di.unimi.it/LSR/Item?id=1057.
.
.
.
Here a MWE:
\version "2.25.5"
\chords {
aes2 cis
}
Specifically, I'd like to have all the
I'm just guessing, but is there a
(make-teeny-markup
? I'm thinking there might be since you can write
\markup \concat { "C" \teeny \sharp " minor" }
--
Knute Snortum
On Sat, May 27, 2023 at 5:56 AM Lib Lists wrote:
> For reference, I almost solved this by changing;
>
>
e new compound symbol somewhere in between the
> number and the note head. I would like the position to be readjusted so the
> number is still in the center of the line.
> -- next part --
> A non-text attachment was scrubbed...
> Name: image0.jpeg
> Type: ima
For reference, I almost solved this by changing;
(make-small-markup
into
(make-tiny-markup
Reference in the documentation:
https://lilypond.org/doc/v2.25/Documentation/extending/how-markups-work-internally
and then https://lilypond.org/doc/v2.25/Documentation/notation/font-markup
for the font
Music for oboe by Mahnkopf?
Hi Jean,
In the attached image, notice the parenthesized note head above some of the
tuplet numbers. If the bracket is down the annotation would be below the tuplet
number. I have been able to override the tuplet number to modify the text to be
whatever I want, however I was looking to automate
Replying to myself, as it might help someone else to give me some hints.
I made some progresses following the LSR example here:
https://lsr.di.unimi.it/LSR/Item?id=1057, adding the line
'make-musicglyph-markup' taken from here:
https://lsr.di.unimi.it/LSR/Snippet?id=1057
In the first snippet I
> Le 27 mai 2023 à 01:43, Gregory Evans a écrit
> :
>
>
> Hello,
> I am trying to imitate a notation that is sometimes found in scores where
> tuplets are of uncommon duration (I can provide an incipt if necessary). I
> have seen the ratio of a tuplet bracket annotated with a
> Le 27 mai 2023 à 01:10, William Rehwinkel via LilyPond user discussion
> a écrit :
>
> Hello Donna,
>
> macOS user here, what I do is download and unpack
> https://gitlab.com/lilypond/lilypond/-/releases/v2.24.1/downloads/lilypond-2.24.1-darwin-x86_64.tar.gz
> into my home directory at
20 matches
Mail list logo
