Re: why must a full measure rest (2/2) have a direction that will cause a collision?

2021-09-20 Thread Kenneth Wolcott
Here's the resultant pdf...attached. On Mon, Sep 20, 2021 at 7:54 PM Kenneth Wolcott wrote: > > Thanks, Carl. > > Here's the erroi stream with the reduced Lilypond code. > > Thanke, > Ken > > GNU LilyPond 2.22.1 > Processing `Hungarian_March_from_La_Damnation_de_Faust_MWE.ly' > Parsing... >

Re: why must a full measure rest (2/2) have a direction that will cause a collision?

2021-09-20 Thread Kenneth Wolcott
Thanks, Carl. Here's the erroi stream with the reduced Lilypond code. Thanke, Ken GNU LilyPond 2.22.1 Processing `Hungarian_March_from_La_Damnation_de_Faust_MWE.ly' Parsing... Interpreting music...[8][8] Preprocessing graphical objects... Interpreting music... MIDI output to

Re: why must a full measure rest (2/2) have a direction that will cause a collision?

2021-09-20 Thread Carl Sorensen
On 9/20/21, 7:10 PM, "lilypond-user on behalf of Kenneth Wolcott" wrote: see attachment of what looks fine (to me) even though I received the warnings... On Mon, Sep 20, 2021 at 6:06 PM Kenneth Wolcott wrote: > > why must a full measure rest (2/2) have a direction

Re: why must a full measure rest (2/2) have a direction that will cause a collision?

2021-09-20 Thread Kenneth Wolcott
see attachment of what looks fine (to me) even though I received the warnings... On Mon, Sep 20, 2021 at 6:06 PM Kenneth Wolcott wrote: > > why must a full measure rest (2/2) have a direction that will cause a > collision? > > I tried using \stemDown, but that had no effect. > > warning: >

why must a full measure rest (2/2) have a direction that will cause a collision?

2021-09-20 Thread Kenneth Wolcott
why must a full measure rest (2/2) have a direction that will cause a collision? I tried using \stemDown, but that had no effect. warning: blah.ly:34:7: warning: cannot resolve rest collision: rest direction not set { d,1\rest d,1\rest d,1\rest d,1\rest b1\rest b1\rest }

Re: dynamic "p" followed by hairpin crescendo on the same level, how?

2021-09-20 Thread Pierre-Luc Gauthier
Hi Kenneth, {1\p\< <>\!} Or : {\clef bass e,1\p\< <>\!} Hope this helps. Le lun. 20 sept. 2021, à 19 h 58, Kenneth Wolcott a écrit : > > HI; > > dynamic "p" followed by hairpin crescendo on the same level, how? > > See attached screenshot. > > Thanks, > Ken Wolcott -- Pierre-Luc Gauthier

dynamic "p" followed by hairpin crescendo on the same level, how?

2021-09-20 Thread Kenneth Wolcott
HI; dynamic "p" followed by hairpin crescendo on the same level, how? See attached screenshot. Thanks, Ken Wolcott

Re: Extending the width of a glissando

2021-09-20 Thread Lukas-Fabian Moser
Sure, I didn't mean that transforms weren't well-documented. I just suggest a paragraph of NR documentation, possibly linking back to the IR, simply because the kind of technical language we use in IR isn't obvious to understand for most users I would guess (linear transform? complex number?

Re: Extending the width of a glissando

2021-09-20 Thread David Kastrup
Jean Abou Samra writes: > Le 20/09/2021 à 23:55, David Kastrup a écrit : >> Jean Abou Samra writes: >> >>> Le 20/09/2021 à 23:31, David Kastrup a écrit : Jean Abou Samra writes: > Thoughts? One would have to look at the most typical use cases > to decide on an interface.

Re: Extending the width of a glissando

2021-09-20 Thread Jean Abou Samra
Le 20/09/2021 à 23:55, David Kastrup a écrit : Jean Abou Samra writes: Le 20/09/2021 à 23:31, David Kastrup a écrit : Jean Abou Samra writes: Thoughts? One would have to look at the most typical use cases to decide on an interface. Anything wrong with using a ly:transform? type? It's

Re: Extending the width of a glissando

2021-09-20 Thread David Kastrup
Jean Abou Samra writes: > Le 20/09/2021 à 23:31, David Kastrup a écrit : >> Jean Abou Samra writes: >> >>> Thoughts? One would have to look at the most typical use cases >>> to decide on an interface. >> Anything wrong with using a ly:transform? type? It's straightforward to >> create and

Re: Extending the width of a glissando

2021-09-20 Thread David Kastrup
Jean Abou Samra writes: > Thoughts? One would have to look at the most typical use cases > to decide on an interface. Anything wrong with using a ly:transform? type? It's straightforward to create and manipulate. -- David Kastrup

Re: Extending the width of a glissando

2021-09-20 Thread Jean Abou Samra
Le 20/09/2021 à 23:31, David Kastrup a écrit : Jean Abou Samra writes: Thoughts? One would have to look at the most typical use cases to decide on an interface. Anything wrong with using a ly:transform? type? It's straightforward to create and manipulate. I had already forgotten about

Re: Extending the width of a glissando

2021-09-20 Thread Jean Abou Samra
Le 20/09/2021 à 22:02, Lukas-Fabian Moser a écrit : Question to the experts: Am I right in thinking that the documentation is misleading here? That is also my understanding. The rotation property works on a stencil using its own extents, performing the equivalent of ly:stencil-rotate,

Re: Extending the width of a glissando

2021-09-20 Thread Lukas-Fabian Moser
Question to the experts: Am I right in thinking that the documentation is misleading here? That is also my understanding. The rotation property works on a stencil using its own extents, performing the equivalent of ly:stencil-rotate, not ly:stencil-rotate-absolute. After that, LilyPond

Re: Extending the width of a glissando

2021-09-20 Thread Jean Abou Samra
Le 20/09/2021 à 17:23, Werner LEMBERG a écrit : If I understand it correctly, the "reference point" of a layout object should be its relative (0,0) coordinate. It is possible to display that point using a small function: [...] It would be very nice if appendix A.8, "The Emmentaler font", could

Re: Extending the width of a glissando

2021-09-20 Thread Jean Abou Samra
Le 20/09/2021 à 15:36, Lukas-Fabian Moser a écrit : Hi Peter, One thing puzzles me about the documentation when it comes to placement - it continually refers to the 'reference point' for an object.  I sort of understand what it means, but it doesn't seem to be defined anywhere. For

Re: Extending the width of a glissando

2021-09-20 Thread Werner LEMBERG
> If I understand it correctly, the "reference point" of a layout object > should be its relative (0,0) coordinate. It is possible to display > that point using a small function: [...] It would be very nice if appendix A.8, "The Emmentaler font", could display the metrics boxes as given in the

Re: Ornamentation in Bach's piece

2021-09-20 Thread Martin Straeten
here my workround for this: graceSchleifer = #(define-music-function (parser location note) (ly:music?) (make-music 'SequentialMusic 'elements (list #{ \once \override Voice.NoteHead #'stencil = #ly:text-interface::print \once \override Voice.NoteHead #'X-extent =

Re: Extending the width of a glissando

2021-09-20 Thread Lukas-Fabian Moser
Hi Peter, One thing puzzles me about the documentation when it comes to placement - it continually refers to the 'reference point' for an object.  I sort of understand what it means, but it doesn't seem to be defined anywhere. For instance - to rotate a hairpin you have to specify the

Re: Extending the width of a glissando

2021-09-20 Thread Peter Toye
Hello Lukas-Fabian, Thanks again. I was looking at the wrong place in the documentation. There's a fine line to be drawn between tweaking and changing a default when you only want to do it once.   One thing puzzles me about the documentation when it comes to placement - it continually refers

Re: Printing two staves in the same place (overlaying)

2021-09-20 Thread Xavier Scheuer
On Mon, 20 Sept 2021 at 11:26, Daniel Benjamin Miller wrote: > > This works quite well for overlaying two staves. > > Now, I want to do something a little more complex, but in the same way, and I'm trying to figure out the vertical axis group tweak necessary for doing this. > > I want to have two

Re: Printing two staves in the same place (overlaying)

2021-09-20 Thread Daniel Benjamin Miller
You have a few options, depending on the degree of alignment you do want between the staves. \version "2.22.0" staffI = \new Staff \fixed c' { g4 a b a8 g | fis4 e f2 } staffII = \new Staff \fixed c'' { c2 d4 b, | c4 d bes,2 } zeroSpacing = \with { \override

Re: \addlyrics in ossia staff

2021-09-20 Thread Lukas-Fabian Moser
Thanks David, Lukas-Fabian got there first! You'd think so, but I staked my claim years ago: commit e6895cdbcf30f3683a8c1b1c50dbb1b154ca6bdb Author: David Kastrup Date: Mon Aug 3 09:23:40 2015 +0200 :-) I think it's quite hard to produce an example of easy and convenient modern-day

Re: \addlyrics in ossia staff

2021-09-20 Thread David Kastrup
Peter Toye writes: > Thanks David, > > > Lukas-Fabian got there first! You'd think so, but I staked my claim years ago: commit e6895cdbcf30f3683a8c1b1c50dbb1b154ca6bdb Author: David Kastrup Date: Mon Aug 3 09:23:40 2015 +0200 Issue 4537/1: Let \addlyrics accept an optional context mod

Re: Ornamentation in Bach's piece

2021-09-20 Thread Jun Tamura
Hello Martin, > 2021/09/20 15:46、Martin Straeten のメール: > > here my workround for this: > > graceSchleifer = > #(define-music-function (parser location note) (ly:music?) > (make-music 'SequentialMusic >'elements (list #{ > \once \override Voice.NoteHead #'stencil = >

Re: Musical Theatre-Style Bar Numbers

2021-09-20 Thread antlists
On 20/09/2021 04:38, Calvin Ransom wrote: Hello everyone, I’m transposing a musical theatre book and sometimes the bar numbers contain letters then go back to normal numbering. Here is an example for the Bar Numbering that I am looking for: 1 2 3 3a 3b 3c 4 5 6 Does anyone know how to do