Re: Undertie in lyrics to show no breath

On Wed 20 Jul 2022 at 11:34:58 (+0100), mancunius wrote: > Hello. In the following example I want the undertie to be placed between the > 2 “O sacrum convivium” lines of lyrics, to indicate that no breath should be > taken by the singers - as per the normal choral convention. (cf. the >

Re: woodwind-diagram overrides

Am Mittwoch, den 20. Juli 2022 um 22:00:53 Uhr (+0200) schrieb David Kastrup: > Well, that's more or less what > > #(begin > > ... > > ) > > does. Wow, cool! I assume #'defines than work in the top-level, right? Should've thougt of that but admittedly my scheme is a bit rusty... -- Orm

Re: woodwind-diagram overrides

Orm Finnendahl writes: > Hi, > > Am Mittwoch, den 20. Juli 2022 um 13:14:25 Uhr (-0600) schrieb Carl Sorensen: >> The way to do this is to write the plain scheme code files as lilypond >> files. >> >> Put the functions in a .ly file. >> >> Preface each function with # (to put the parser into

Re: woodwind-diagram overrides

On Wed, Jul 20, 2022 at 1:57 PM Orm Finnendahl < orm.finnend...@selma.hfmdk-frankfurt.de> wrote: > Hi, > > Am Mittwoch, den 20. Juli 2022 um 13:14:25 Uhr (-0600) schrieb Carl > Sorensen: > > The way to do this is to write the plain scheme code files as lilypond > > files. > > > > Put the

Re: woodwind-diagram overrides

Hi, Am Mittwoch, den 20. Juli 2022 um 13:14:25 Uhr (-0600) schrieb Carl Sorensen: > The way to do this is to write the plain scheme code files as lilypond > files. > > Put the functions in a .ly file. > > Preface each function with # (to put the parser into scheme mode). Thanks, I'm aware of

Re: woodwind-diagram overrides

On Wed, Jul 20, 2022 at 1:08 PM Orm Finnendahl < orm.finnend...@selma.hfmdk-frankfurt.de> wrote: > Hi, > > > Alternatively: Is there a way to load the necessary scheme code of the > functions in question by defining some \include statement for plain > scheme code files in the .ly file, ensuring

woodwind-diagram overrides

Hi, for a new piece I need to display Oboe woodwind fingering diagrams according to the book "The Techniques of Oboe Playing" by Peter Veale. Lilypond's standard woodwind fingerings for oboe in non graphic mode are similar, but have some significant differences to the method used in the book

Re: Snippet doesn't work in unstable version

Am Mi., 20. Juli 2022 um 18:43 Uhr schrieb Martín Rincón Botero < martinrinconbot...@gmail.com>: > Hello, > > I grabbed this snippet a while ago from somewhere™ which puts a box > around music (an "improvisation box"). It works perfectly in Lilypond > 2.22.1, but not in Lilypond 2.23.3+. Does

Snippet doesn't work in unstable version

Hello, I grabbed this snippet a while ago from somewhere™ which puts a box around music (an "improvisation box"). It works perfectly in Lilypond 2.22.1, but not in Lilypond 2.23.3+. Does somebody know how to make it work in more recent versions? This is the snippet: \version "2.19.15" \header

Re: openmusic

Sorry missed the subject- So i am reposting. Dear Andrew, Yes I do, since i wrote this library and maintaine it. It generates .ly files starting from Om Score objects. Example (screeshot) I have a dev ongoing still not released yet. If you find, need some improvements please do say so. I

Re: Moving a tie in a chord

On Wed, Jul 20, 2022 at 6:06 AM Thomas Morley wrote: > You could do > > \relative a,, { > \clef bass > \time 6/8 > > 4.(~ > > \once \override TieColumn.tie-configuration = #'((-1 . 1)(-10 . -1)) > > q8 ) | > } > > Also, see NR about TieColumn.tie-configuration Thank you, Harm.

Undertie in lyrics to show no breath

Hello. In the following example I want the undertie to be placed between the 2 “O sacrum convivium” lines of lyrics, to indicate that no breath should be taken by the singers - as per the normal choral convention. (cf. the commented-out \breathe command in the music itself.) As it currently

Re: Change to \rest markup in 2.23

Jean Abou Samra writes: > Le 20/07/2022 à 14:57, David Kastrup a écrit : >> The rule was used for converting all the old stuff in the repo, so it >> wasn't broken at one point of time. This would suggest either a Python >> update effect or some editing. Or for some reason this particular input

Re: Moving a tie in a chord

Am Mi., 20. Juli 2022 um 02:17 Uhr schrieb Knute Snortum : > > I'm trying to adjust the Y position of a tie in a chord, but I'm > having trouble. What works for a single tie doesn't seem to work for > a chord: > > %%% > \version "2.22.2" > > moveTie = { > \once \override Tie.staff-position = -5

Re: Change to \rest markup in 2.23

Thomas Morley writes: > Am Mi., 20. Juli 2022 um 14:29 Uhr schrieb David Kastrup : >> >> David Kastrup writes: >> >> > Jean Abou Samra writes: >> > >> >> Le 20/07/2022 à 05:57, David F. a écrit : >> >>> In 2.23, the rest markup command changed from taking a string to taking >> >>> a duration.

Re: Change to \rest markup in 2.23

Le 20/07/2022 à 14:57, David Kastrup a écrit : The rule was used for converting all the old stuff in the repo, so it wasn't broken at one point of time. This would suggest either a Python update effect or some editing. Or for some reason this particular input escapes the pattern match.

Re: Change to \rest markup in 2.23

Am Mi., 20. Juli 2022 um 14:29 Uhr schrieb David Kastrup : > > David Kastrup writes: > > > Jean Abou Samra writes: > > > >> Le 20/07/2022 à 05:57, David F. a écrit : > >>> In 2.23, the rest markup command changed from taking a string to taking a > >>> duration. > >>> > >>> \version "2.22" > >>>

Re: Change to \rest markup in 2.23

David Kastrup writes: > Jean Abou Samra writes: > >> Le 20/07/2022 à 05:57, David F. a écrit : >>> In 2.23, the rest markup command changed from taking a string to taking a >>> duration. >>> >>> \version "2.22" >>> \markup \rest #"4.." >>> >>> \version "2.23" >>> \markup \rest { 4.. } >>> >>>

Re: Automatization

20 juil. 2022 11:29:09 Valentin Petzel : > first of all you can achieve the same thing maybe slightly more transparently > like this, which also allows for modification of the stencil: Thank you all for these solutions. The one presented by Xavier suits me perfectly as I use different templates

Re: Change to \rest markup in 2.23

Jean Abou Samra writes: > Le 20/07/2022 à 05:57, David F. a écrit : >> In 2.23, the rest markup command changed from taking a string to taking a >> duration. >> >> \version "2.22" >> \markup \rest #"4.." >> >> \version "2.23" >> \markup \rest { 4.. } >> >> It would be nice if this change were

Re: Change to \rest markup in 2.23

Le 20/07/2022 à 05:57, David F. a écrit : In 2.23, the rest markup command changed from taking a string to taking a duration. \version "2.22" \markup \rest #"4.." \version "2.23" \markup \rest { 4.. } It would be nice if this change were backward compatible, at least for a version or two.

Re: Change to \rest markup in 2.23

Am Mi., 20. Juli 2022 um 05:58 Uhr schrieb David F. : > > In 2.23, the rest markup command changed from taking a string to taking a > duration. > > \version "2.22" > \markup \rest #"4.." > > \version "2.23" > \markup \rest { 4.. } > > It would be nice if this change were backward compatible, at

Re: openmusic

There's this: https://github.com/openmusic-project/omlily I don't know if it is currently under development. Andrew

Re: openmusic

New to me. I read that it can make scores. What format does it use for this? About the only way you would get output into lilypond is via Music XML. Does it support this? On 20/07/2022 8:10 pm, Stefan Thomas wrote: does anyone of You use openmusic in conjunction with lilypond? I would like

openmusic

Dear community, does anyone of You use openmusic in conjunction with lilypond? I would like to know how to export a patch to lilypond. A small example or any hint would be very appreciated! Best, Stefan

Re: Automatization

Hello Vincent, first of all you can achieve the same thing maybe slightly more transparently like this, which also allows for modification of the stencil: #(define (white-under grob) (grob-interpret-markup grob (markup #:vcenter #:whiteout #:pad-x 1 (ly:grob-property grob 'text

Re: debug scheme part working with Frescobaldi

Eef Weenink wrote: I have several lines of scheme, somewhere is probably an syntax error. The only message I get is form lilypond log: there is an error in the line # begin etcetera. (that is the first line of the scheme segment). I want to zoom in, and see what specific problem there is,

Re: Automatization

Le 20/07/2022 à 09:40, Xavier Scheuer a écrit : You can put the overrides (without \once) in your layout block. It's so obvious once you tell me! Thanks Xavier. -- Vincent Gay Envoyé depuis mon saxo-phone :) https://myrealbook.vintherine.org/ - http://photos.vintherine.org/

Re: Automatization

On Wed, 20 Jul 2022 at 09:35, Vincent Gay wrote: > > Hello everyone, > > I use the inlineMMRN function below whenever I think of it to display the number of bars of rests IN the staff. I find that it gains in readability when the scores are a bit heavy with textual indications. > > > The problem

Automatization

Hello everyone, I use the inlineMMRN function below whenever I think of it to display the number of bars of rests IN the staff. I find that it gains in readability when the scores are a bit heavy with textual indications. The problem is in the "every time I think of it". Is there by any

Re: debug scheme part working with Frescobaldi

I don't know if this is helpful but debug print statements, the last resort of the desperate, are sometimes useful. % simple debug print #(define (dbg . args)    "Simple debug console print."    (cond     ((not (null? args)) (display (car args)) (display " ") (apply dbg (cdr

Re: debug scheme part working with Frescobaldi

Le 20/07/2022 à 08:22, Eef Weenink a écrit : I use 2.22 and arranger.ly  (from Giles Thibault) My question is more general. (and maybe mostly related to Frescobaldi as an enviroment). I have several lines of scheme, somewhere is probably an syntax error. The only

Re: debug scheme part working with Frescobaldi

I use 2.22 and arranger.ly (from Giles Thibault) My question is more general. (and maybe mostly related to Frescobaldi as an enviroment). I have several lines of scheme, somewhere is probably an syntax error. The only message I get is form lilypond log: there is an error in