Ambitus_engraver causes ghost laissezVibrer ties on first note of Voice

Do you like ghosts? Putting an LV tie on the first note of a Voice in which there is an ambitus generates two unwelcome "ghost" LV ties floating unattached above and below the note, in addition to the desired single LV tie that is properly attached to the note.  Here is the MWE (see also

Re: Horizontal spacing per measure?

On Wed, 23 Mar 2022 at 13:41, Molly Preston wrote: > Hello. > > I am wondering if there is any way of changing the horizontal spacing. I > would like the first two measures to have more room than the third measure. > The cross-staff beaming I think needs more room and I am not sure how to do >

Horizontal spacing per measure?

Hello. I am wondering if there is any way of changing the horizontal spacing. I would like the first two measures to have more room than the third measure. The cross-staff beaming I think needs more room and I am not sure how to do this other than moving the third measure to the next line. I

Re: Problem rendering all scores

Thanks H.S.Teoh and David Wright for your replies! Teoh you were right, it wasn´t related to lilypond...I look at the manjaro forum link you send me and applied the solution they suggested and worked! I thought was something with lilypond because was the only application I had a problem,

Re: Problem rendering all scores

On Tue 22 Mar 2022 at 14:19:59 (-0700), H. S. Teoh wrote: > On Tue, Mar 22, 2022 at 08:36:45PM +, James.Correa wrote: > >I start to have this problem with lilypond after an update to > >python 3.8 , I am on Manjaro KDE. > >Every time I try to engrave a score I got this message: > >

Re: 'baroque' time signatures

Leo Correia de Verdier writes: > I added necessary supporting code like Michael (and a voice filled > with repeated half notes, so I could hear the tempo) and got it to > compile compile correctly with tempo changes (at least alternating > fast and slow sections) on Lilypond 2.19.82 Frescobaldi

Re: 'baroque' time signatures

I added necessary supporting code like Michael (and a voice filled with repeated half notes, so I could hear the tempo) and got it to compile compile correctly with tempo changes (at least alternating fast and slow sections) on Lilypond 2.19.82 Frescobaldi 3.1.3, so I wouldn't think that is the

Re: 'baroque' time signatures

Many thanks Michael for your comments. Unfortunately, due to my reluctance (and perhaps inability) of using Port and Terminal, I am obliged to use \version 2.20.2 with Frescobaldi 3.1.3, which maybe are the cause of my midi problems. Anyway, many thanks again for your help Mario Mario

Re: Problem rendering all scores

On Tue, Mar 22, 2022 at 08:36:45PM +, James.Correa wrote: >Hi everybody, >I start to have this problem with lilypond after an update to >python 3.8 , I am on Manjaro KDE. >Every time I try to engrave a score I got this message: > >Starting lilypond 2.23.5

Re: 'baroque' time signatures

Here is my MWE (structure of lilypond coding regarding part of “Combattimento di Tancredi e Clorinda” by Claudio Monteverdi): MWE means I can take the code and compile it. And then it shows the problem. I tried to amend your code as follows: I surrounded it with: \version "2.23.5" \include

Re: 'baroque' time signatures

Here is my MWE (structure of lilypond coding regarding part of “Combattimento di Tancredi e Clorinda” by Claudio Monteverdi): \key do\major \time 3/2 \set Score.measureLength = #(ly:make-moment 6 2) \tempo \breve. = 70 s\breve.*20\break \time 4/4 \set

Problem rendering all scores

Hi everybody, I start to have this problem with lilypond after an update to python 3.8 , I am on Manjaro KDE. Every time I try to engrave a score I got this message: Starting lilypond 2.23.5 [Kintsugi-James-Correa.ly]... /usr/local/lilypond/usr/bin/lilypond: error while loading shared

Re: 'baroque' time signatures

Hi Mario, please always include the list as well. Sorry Michael for my ignorance, but what is the meaning of the acronym MWE? MWE == Minimum Working Example It means a piece of code as short as possible that just shows the faulty or suspicious behaviour. That greatly helps others to help

Re: 'baroque' time signatures

And what \tempo should be adopted in order to have a medium-fast midi output? \tempo \breve. = 100 or 200 or 300 seem not changing midi output. For me \tempo \breve. = 100 or 200 or 300 does change the tempo rather distinctively. However you probably want something along the line of \breve. =

Re: 'baroque' time signatures

Any suggestion regarding this ? And what \tempo should be adopted in order to have a medium-fast midi output? \tempo \breve. = 100 or 200 or 300 seem not changing midi output. Many thanks for any suggestion. Mario Mario Bolognani mario.bolog...@gmail.com

Re:

Upon checking, that was the version I was using. When I tried to use the tutorial, and follow along and click on each image, I kept on getting "file not found", so I followed the written instructions myself and got the files I had attached above. Thanks On Tue, 22 Mar 2022 at 11:26, Michael

Re:

Sorry, I have been away from my computer for some time. Thank you very much! Michael D On Mon, 21 Mar 2022 at 03:48, Phil Holmes wrote: > I don't know what version of nwc2ly you're using, but I rewrote the > original one to use for converting nwc text files to liliypond. There > are

Re: Scope of context properties

Thanks! That makes sense! Simply, order of precedence and where a property is defined cause such behavior, I see. Akikazu On 2022/03/22 21:00, Jean Abou Samra wrote: Le 22/03/2022 à 05:01, Masaki, Akikazu a écrit : Hello all, In Learning Manual 3.3.4 Modifying context properties

Re: Cross-staff glissando with crescendo and dynamics

Hi David! The issue, put in a slightly simplified way, is that the Voice context to which the dynamics are attached has moved away from the Staff under which the dynamics were originally aligned, leaving lilypond ”in doubt” about under what staff the \mp should be. The answer in the linked

Re: Cross-staff glissando with crescendo and dynamics

Le 22/03/2022 à 13:36, David Santamauro a écrit : Hi, I'm not understanding the warnings I'm getting with the following snippet. I've included a possible work-around that is musically identical, but visually unappealing: %% \version "2.22.2" \include "english.ly" \score {   \new

Re: Cross-staff glissando with crescendo and dynamics

So I figured it out based on: https://lists.gnu.org/archive/html/lilypond-user/2016-07/msg00266.html Not an unreasonable solution, but I still don't quite understand the underlying issue. Thanks From: David Santamauro Date: Tuesday, March 22, 2022 at 8:36 AM To: lilypond-user@gnu.org Cc:

Cross-staff glissando with crescendo and dynamics

Hi, I'm not understanding the warnings I'm getting with the following snippet. I've included a possible work-around that is musically identical, but visually unappealing: %% \version "2.22.2" \include "english.ly" \score { \new PianoStaff \with { instrumentName = "Harp" } << \new

Re: Scope of context properties

Le 22/03/2022 à 05:01, Masaki, Akikazu a écrit : Hello all, In Learning Manual 3.3.4 Modifying context properties http://lilypond.org/doc/v2.22/Documentation/learning/modifying-context-properties.html "--- The clefGlyph property will take effect only if it is set in the Staff context, but

Re: Displaying typesetting information at compile time

Le 22/03/2022 à 09:15, Richard Shann a écrit : Perfect! Thanks, I should have thought to track down documentation for page-post-process ... Richard Ahem, well, like with a number of Scheme interfaces, that documentation is nonexistent. Jean

Re: Time signature guide

I hadn’t seen David’s reply until after I posted, otherwise I wouldn't have basically repeated his answer. A disadvantage of the << … \\ … >> syntax in this case is that it applies \voiceTwo to \melody (it has all its stems turned down, for instance). While you can reset that with \oneVoice I

Re: Time signature guide

Thank you so much, you offered two similar and valid solutions! Regards Il giorno lun 21 mar 2022 alle ore 10:19 Leo Correia de Verdier < leo.correia.de.verd...@gmail.com> ha scritto: > I’m not sure I understood your question right, but I think the usual way > to do it would be to write the

Re: Displaying typesetting information at compile time

On Mon, 2022-03-21 at 17:28 +0100, Jean Abou Samra wrote: > > > Le 21/03/2022 à 17:24, Richard Shann a écrit : > > On Sun, 2022-03-20 at 20:09 +0100, Jean Abou Samra wrote: > > > > > [...] perhaps there is something altogether > > simpler? > > > > In that case, just output the info at the