Re: Extracting pitch of first note, then assign duration

Hello everyone, You might find some hints in a piece I have done lately: a score of  J.S. Bach's Well-Tempered Clavier Praeludium I Where I wrote functions to create the score programmatically (like extract groups of five

Writing Scheme in Lilypond to control glyph used for custom custos function

Hello everyone, I'm writing a function that places a custos after the double bar to give singers an indication of the pitch of their next note. Usually, custos are are used within a piece, but in chant, I have verses that are part of new scores, and it is helpful to indicate the pitch of the

Re: Extracting pitch of first note, then assign duration

Hello Lucas, Yes, this works perfectly. I did not know *first* existed! I stole the example from https://lilypond.org/doc/v2.20/Documentation/notation/substitution-function-examples However, I still need to find a way to automagically manage the stem direction of the custos, since the notes may

Re: Extracting pitch of first note, then assign duration

Hi Matthew, Am 07.03.21 um 20:03 schrieb Matthew Fong: I am in the process of writing a note replacement function that allows me to place a custos anywhere I might need. I am stuck on writing a function that extracts the pitch of the first note, given a list of notes, and then forcing a

Extracting pitch of first note, then assign duration

Hello everyone, I am in the process of writing a note replacement function that allows me to place a custos anywhere I might need. I am stuck on writing a function that extracts the pitch of the first note, given a list of notes, and then forcing a duration of 1/4. Any pointers would be

Re: Forcing articulations inside slurs

On Sun, Mar 7, 2021 at 1:11 PM Valentin Petzel wrote: > Hello Silvain, > > In fact the aforementioned > > \override Script.avoid-slur = #' inside > > is the proper way to do this. > Cheers, > Valentin > Perfect! Thanks Valentin. Be well, Ralph -- Ralph Palmer Brattleboro, VT USA (he, him,

Re: Forcing articulations inside slurs

Yes, for sure, this is the proper way. Actually, I just looked into the documentation et found a way to move the position, and saw your message after I posted (too quickly) what I had found... Le 07.03.21 à 19:08, Valentin Petzel a écrit : Hello Silvain, In fact the aforementioned \override

Re: Forcing articulations inside slurs

Hello Silvain, In fact the aforementioned \override Script.avoid-slur = #'inside is the proper way to do this. Overriding positions should only be done if you really need it, as it is unflexible and thus won’t react to future changes. Thus the proper way to do this is to tell Lilypond what

Re: Workaround for (not-allowed) numbers in variable names?

On Sun 07 Mar 2021 at 14:48:08 (+), Peter Toye wrote: > The 2.22 documentation is obviously better here: > > The name of a variable should not contain (ASCII) numbers, multiple > underscores, multiple dashes or space characters. All other characters > Unicode provides are allowed, for

Re: Workaround for (not-allowed) numbers in variable names?

The 2.22 documentation is obviously better here: The name of a variable should not contain (ASCII) numbers, multiple underscores, multiple dashes or space characters. All other characters Unicode provides are allowed, for example Latin, Greek, Chinese or Cyrillic. Non-adjacent single

Re: Forcing articulations inside slurs

I found something in the documentation... \relative c'' {   \clef treble   \key d \major   \time 4/4 *\override Slur.positions = #'(4 . 4)*   d4-_( d-_ d-_ d-_) } Need at least 4 for the tweak to worl Le 07.03.21 à 14:51, Ralph Palmer a écrit : Greetings - Thanks for all your work and help!

Re: Forcing articulations inside slurs

On Sun, Mar 7, 2021 at 8:56 AM Jean Abou Samra wrote: > \override Script.avoid-slur = #'inside > d4-_( d-_ d-_ d-_) > } > Thanks, Jean - I could remember dealing with the problem somehow in the past, but could not remember or find the solution. All the best, Ralph -- Ralph Palmer

Re: Workaround for (not-allowed) numbers in variable names?

Hello, Browsing the documentation, I did not find anything about variable names with allowing non-alphabetic characters. Did I miss something? Here are extracts the 2.20 documentation == 3.1.1 Introduction to the LilyPond file structure <3.1.1

Re: Forcing articulations inside slurs

Le 07/03/2021 à 14:51, Ralph Palmer a écrit : Greetings - Thanks for all your work and help! I'm trying to force portato marks inside slurs. I've attached a MWE. I've tried searching both the regular LilyPond documentation and the LSR, with no luck. Can someone please point me in the right

Forcing articulations inside slurs

Greetings - Thanks for all your work and help! I'm trying to force portato marks inside slurs. I've attached a MWE. I've tried searching both the regular LilyPond documentation and the LSR, with no luck. Can someone please point me in the right direction, either in the documentation, the LSR, or

Re: Workaround for (not-allowed) numbers in variable names?

Peter Toye writes: > Thanks for putting me right yet again. I'm not quite sure what you > mean by 'resized'. q4 is surely legal? Sure, but it's two chords, not one. -- David Kastrup

Re: Workaround for (not-allowed) numbers in variable names?

Thanks for putting me right yet again. I'm not quite sure what you mean by 'resized'. q4 is surely legal? Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - Sunday, March 7, 2021, 12:09:30 PM, David Kastrup wrote: > Peter Toye writes: >> I asked this

Re: Workaround for (not-allowed) numbers in variable names?

My personal view is that variables are important concepts and deserve a separate section somewhere - possibly 3.1.6 as a separate part of 'File Structure'. I note that the preceding section on markup text does not contain any detailed syntax definition - not even a link to the relevant section.

Re: Workaround for (not-allowed) numbers in variable names?

> Yes, it's documented in the Notation Reference Manual section 3.1.5 > File Structure. It doesn't seem the obvious place to put the syntax > of variable names. Well, there is a proper index entry... However, documentation for the 'foo.1.bar.2' trick is still missing. Do you have a better

LSR 1122 "Naturalize music"

Hi all, I cross-post this to user- and devel-list: The unapproved LSR-snippet: https://lsr.di.unimi.it/LSR/Item?u=1=1122 basically duplicates the doc-tagged: https://lsr.di.unimi.it/LSR/Snippet?id=266 If nobody speaks up I'll delete it soon. Cheers, Harm

Re: Workaround for (not-allowed) numbers in variable names?

Peter Toye writes: > I asked this question some time ago, and David Kastrup was kind enough > to put me right. > > The problem , as you mentioned, is in the way that numbers are used > for durations. Consider the following code: > > chord = > chord2= > > c1 \chord2 > > Should the second

Re: Workaround for (not-allowed) numbers in variable names?

Yes, it's documented in the Notation Reference Manual section 3.1.5 File Structure. It doesn't seem the obvious place to put the syntax of variable names. Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - > Message: 4 > Date: Sat, 6 Mar 2021 21:30:56 +0900

Re: Workaround for (not-allowed) numbers in variable names?

I asked this question some time ago, and David Kastrup was kind enough to put me right. The problem , as you mentioned, is in the way that numbers are used for durations. Consider the following code: chord = chord2= c1 \chord2 Should the second element be interpreted as 2 or 1? I imagine

Re: Workaround for (not-allowed) numbers in variable names?

田村淳 writes: > Thank you! > > Now I understand that keys separated by periods, for example, > StaffGrouper.staff-staff-spacing.basic-distance = #7 > is a way to access a nested alist easily. Yes, and it has been like that a long time. Being able to access it with

Re: Workaround for (not-allowed) numbers in variable names?

Thank you! Now I understand that keys separated by periods, for example, StaffGrouper.staff-staff-spacing.basic-distance = #7 is a way to access a nested alist easily. Jun > 2021/03/07 17:26、Jean Abou Samra のメール: > > Le 07/03/2021 à 03:03, 田村淳 a écrit : > >> Hello David, >> >>> gamme.1 is

Re: How to get bounding NoteColumns of the first of consecutive TextSpanners

Le 06/03/2021 à 17:47, Thomas Morley a écrit : Hi Jean, [...] I took the liberty to modify your engraver, You must not do this. All of the code I write is forbidden form disclosure and restrictively licensed such that modification is not allowed. The code itself destroys itself when it has

Re: Workaround for (not-allowed) numbers in variable names?

Le 07/03/2021 à 03:03, 田村淳 a écrit : Hello David, gamme.1 is not a variable name. It takes gamme to be an alist, and the entry under key 1 is what is addressed here. Since you showed the Scheme equivalent below, I guess the above is a part of LilyPond syntax, or something the LilyPond