Re: Setting lytics to alternative endings

2022-12-16 Thread Jogchum Reitsma
Ah!  Thanks a lot.  Kieren also for taking the effort! regards, Jogchum Op 15-12-2022 om 16:27 schreef Jean Abou Samra: Le 15/12/2022 à 14:57, Kieren MacMillan a écrit : Hi Jogchum, I suppose it is very simple, but I can't find it in documentation, or here on the list. How can one set

Re: Installing 2.24

2022-12-16 Thread JxStarks
No, I haven't. Thank you for the direction. Jerry On Thu, Dec 15, 2022, 8:33 PM Jean Abou Samra wrote: > Le 16/12/2022 à 02:25, JxStarks a écrit : > > Greetings, > > > > I'm feeling rather foolish. I'm running under Windows 10 and use > > Frescobaldi (3.1.2) as my main interface with LilyPond.

Re: Setting lytics to alternative endings

2022-12-16 Thread Jogchum Reitsma
Op 15-12-2022 om 16:27 schreef Jean Abou Samra: <...> As said in another thread [1], I would recommend using the \repeat construct in the lyrics too: \version "2.23.82" theMusic = {   \repeat volta 2 {     g'4 4 4 4     \alternative { { f'1 } { c''1 } }   } } theLyrics = \lyricmode {  

Fwd: Setting lytics to alternative endings

2022-12-16 Thread Jogchum Reitsma
Have sent it to Xavier, in stead of to the list - apologies! Jogchum Op 15-12-2022 om 20:38 schreef Xavier Scheuer: On Thu, 15 Dec 2022 at 16:29, Jean Abou Samra wrote: > > > As said in another thread [1], I would recommend using the \repeat > construct in the lyrics too: > Hello, This is

Re: How to implement "f (second time p)" for midi?

2022-12-16 Thread David Kastrup
Kenneth Wolcott writes: > HI; > > Dumb question here. I'm sure that this is covered in the > documentation, but I have yet to find out where. > > Lilypond 2.22.2, MacOs (via homebrew). > > How to implement "f (second time p)" for midi? \volta 1 <>\f \volta 2 <>\p could possibly work.

Re: Fwd: Setting lytics to alternative endings

2022-12-16 Thread Jean Abou Samra
Le 16/12/2022 à 10:40, Jogchum Reitsma a écrit : Hi, without a doubt it is my bad, but while I've spend quite some time looking for this in the documentation, I didn't come across it. Looked, among a lot of other places, in

Re: Setting lytics to alternative endings

2022-12-16 Thread Kieren MacMillan
Hi Jean, > I think I was not clear explaining what is OK and what is not. The golden > rule is: *if a bit of music is repeated, in the actual performance by the > player, it should be enclosed in a \repeat block, otherwise it shouldn’t*. Maybe *that* should be included in the docs…? :)

Re: LilyPond 2.24.0 released!

2022-12-16 Thread Ralph Palmer
On Thu, Dec 15, 2022 at 1:43 PM Jonas Hahnfeld via LilyPond user discussion wrote: > We are proud to announce the release of GNU LilyPond 2.24.0. > LilyPond 2.24 is brought to you by > > Main Developers: > Jean Abou Samra, Colin Campbell, Dan Eble, Jonas Hahnfeld, Phil Holmes, > David Kastrup,

Re: Setting lytics to alternative endings

2022-12-16 Thread Jean Abou Samra
Le 16/12/2022 à 10:47, Jogchum Reitsma a écrit : Hi Jean, While this work in placing the words correctly, it is, in my case, not quite flawless. If I render the attached snippet, there is no "2"-bracket above the second alternative. But if you comment out the lyrics part, the "problem"

Re: Setting lytics to alternative endings

2022-12-16 Thread Kieren MacMillan
Hi Xavier, > This is also what is recommended in the documentation, there is even a whole > section dedicated to lyrics and repeats, and in particular repeats with > alternative (with special cases of melisma, extenders and hyphens, etc). > Cf. NR 2.1.2 Techniques specific to lyrics > Lyrics

Re: Setting lytics to alternative endings

2022-12-16 Thread Jean Abou Samra
> Le 16 déc. 2022 à 15:25, Kieren MacMillan a > écrit : > > In a certain way, the unfolded example is inconsistent, right? Shouldn’t it > be something like […] > > Otherwise, you have an example with music that has a \repeat command and > lyrics that don’t… This doc example is not a

Re: LilyPond 2.24.0 released!

2022-12-16 Thread H. S. Teoh
On Fri, Dec 16, 2022 at 10:33:58AM -0800, H. S. Teoh via LilyPond user discussion wrote: [...] > This latest release broke one of my scores. I have reduced the > problem to the following snippet: > > \version "2.18.2" > \score { > \tuplet 3/2 4 { \repeat tremolo 6 { 8( } }

Re: How to implement "f (second time p)" for midi?

2022-12-16 Thread Kenneth Wolcott
Hi David; Thank you for the hint. I successfully ran Lilypond 2.24.0 convert.ly on my source and successfully engraved it using Lilypond version 2.24.0. Now I'll look into the /volta idea. Thanks, Ken On Fri, Dec 16, 2022 at 7:16 AM David Kastrup wrote: > > Kenneth Wolcott writes: > > >

Re: How to implement "f (second time p)" for midi?

2022-12-16 Thread Kenneth Wolcott
Hi David; I have attached the updated Lilypond source. It looks like my attempt failed to implement your hint :-) Here's the results of my attempt to implement your idea... %% %% Here's my sanitized (long

Well, that's ist, Me too. Re: LilyPond 2.24.0 released!

2022-12-16 Thread Roland Goretzki
Hello Ralph, I think the same, and I'm thankful, too. A nice Christmas to all ponders. :-) Best Regards Roland You wrote:: > On Thu, Dec 15, 2022 at 1:43 PM Jonas Hahnfeld via LilyPond user discussion > wrote: > > > We are proud to announce the release of GNU LilyPond 2.24.0. > >

Re: How to implement "f (second time p)" for midi?

2022-12-16 Thread David Kastrup
Kenneth Wolcott writes: > Hi David; > > I have attached the updated Lilypond source. > > It looks like my attempt failed to implement your hint :-) Well, for one thing you might want to remove your \f_second_time_p phrases. For another, the error message occurs in the typeset output.

Re: How to implement "f (second time p)" for midi?

2022-12-16 Thread Kenneth Wolcott
Hi David; Thank you! I copied the right hand notes so that there would be a midi-specific version. I then reverted the changes I made to the right hand notes containing the \volta hint. I then modified the right hand notes for midi without the New Dynamic notation but with the \volta hint.

Re: LilyPond 2.24.0 released!

2022-12-16 Thread Jean Abou Samra
Le 16/12/2022 à 20:39, H. S. Teoh via LilyPond user discussion a écrit : Hmm. I'm running a local Linux build of 2.24.0 (commit 916ae4111441a9426fbb9c11f7c42735eccf0cac). That is not 2.24.0, but current master. 2.24.0 is the tag v2.24.0, which the branch stable/2.24 also currently points to.

Re: LilyPond 2.24.0 released!

2022-12-16 Thread H. S. Teoh
On Sat, Dec 17, 2022 at 12:52:27AM +0100, Jean Abou Samra wrote: > Le 16/12/2022 à 20:39, H. S. Teoh via LilyPond user discussion a écrit : > > Hmm. I'm running a local Linux build of 2.24.0 (commit > > 916ae4111441a9426fbb9c11f7c42735eccf0cac). > > > That is not 2.24.0, but current master.

Error when compiling snippet "Parenthesize a group of notes using a Scheme function"

2022-12-16 Thread Joseph Srednicki
I am running Lilypond 2.24.0 on Windows 11. I am trying the use the snippet entitled "Parenthesize a group of notes using a Scheme function" located at https://lsr.di.unimi.it/LSR/Snippet?id=902. I receive the following errors:

Re: Error when compiling snippet "Parenthesize a group of notes using a Scheme function"

2022-12-16 Thread Kieren MacMillan
Hi Joseph, If you use convert-ly on your files, it will update ParenthesesItem to Parentheses, which will eliminate the error. Hope that helps! Kieren.

Re: Error when compiling snippet "Parenthesize a group of notes using a Scheme function"

2022-12-16 Thread Carl Sorensen
On Fri, Dec 16, 2022 at 11:48 AM Joseph Srednicki wrote: > I am running Lilypond 2.24.0 on Windows 11. > > I am trying the use the snippet entitled "Parenthesize a group of notes > using a Scheme function" located at > https://lsr.di.unimi.it/LSR/Snippet?id=902. > > I receive the following

Re: LilyPond 2.24.0 released!

2022-12-16 Thread Paul Hodges
Your snippet compiles correctly (with the errors) on my Windows install of 2.24.0 Paul From: H. S. Teoh via LilyPond user discussion To: Sent: 16/12/2022 18:33 Subject: Re: LilyPond 2.24.0 released! On Thu, Dec 15, 2022 at 10:42:42PM +0100, Jonas Hahnfeld via LilyPond user

Re: LilyPond 2.24.0 released!

2022-12-16 Thread H. S. Teoh
On Thu, Dec 15, 2022 at 10:42:42PM +0100, Jonas Hahnfeld via LilyPond user discussion wrote: > We are proud to announce the release of GNU LilyPond 2.24.0. [...] This latest release broke one of my scores. I have reduced the problem to the following snippet: \version "2.18.2"

Re: Error when compiling snippet "Parenthesize a group of notes using a Scheme function"

2022-12-16 Thread Robin Bannister
Kieren MacMillan wrote: Hi Joseph, If you use convert-ly on your files, it will update ParenthesesItem to Parentheses, which will eliminate the error. Yes, but: The LSR snippets don't have a \version statement. If convert-ly doesn't help, insert the line \version "2.22.0" and try again.

Re: LilyPond 2.24.0 released!

2022-12-16 Thread H. S. Teoh
Hmm. I'm running a local Linux build of 2.24.0 (commit 916ae4111441a9426fbb9c11f7c42735eccf0cac). My configure command was just running autogen.sh with --prefix. Does that make a difference? --T On Fri, Dec 16, 2022 at 07:31:46PM +, Paul Hodges wrote: >Your snippet compiles correctly