Re: Suppressing some errors in output but not others

2024-10-15 Thread Knute Snortum
On Tue, Oct 15, 2024 at 10:32 AM Kieren MacMillan < kie...@kierenmacmillan.info> wrote: > Hi Knute, > > > I've tried using that function, but I get a warning that the warning > wasn't found. I put this in my input file: > > #(ly:expect-warning "calculation-in-progress") > > Did you try > > #(ly:e

Re: Suppressing some errors in output but not others

2024-10-15 Thread Kieren MacMillan
Hi again, >>> > I've tried using that function, but I get a warning that the warning >>> > wasn't found. I put this in my input file: >>> > #(ly:expect-warning "calculation-in-progress") >> Did you try >> #(ly:expect-warning "cyclic dependency") > Hey, that worked! Thanks a lot. How strange

Re: Advice or tutorials for book publishing?

2024-10-15 Thread Dirck Nagy
Thank you, everyone! I am somewhat familiar with Scribus, never used LaTex before though, so perhaps I'll give that a try first, with something simple. THanks! dirck From: lilypond-user-bounces+dnagy=uwlax@gnu.org on behalf of Silvain Dupertuis Sent: Mon

Re: Change rhythm of broken chords (arpeggios)? Any tips, tricks or tools?

2024-10-15 Thread Eef Weenink
Thank you all, for your reactions. Great support!! I checked the solutions you have send. Maybe readers in future want to know my findings for their own use. - All of them are functional, and useful. But not the same 😉 Mark send this one: https://lsr.di.unimi.it/LSR/Snippet?id=346 defineTransf

Re: again struggling with simultanous / stacking voices

2024-10-15 Thread mskala
On Tue, 15 Oct 2024, Sebastian Menge wrote: > I came up with the following (hardly minimal) example. Lily gives me many > warnings, so I wonder if I could make it better - and easier. Here's what I get by trying to clean up your code; your code in the first score for comparison, followed by my ve

Re: 'tacet al fine' multi-measure rest

2024-10-15 Thread Kieren MacMillan
Hi Werner, > This is a very nice trick, thanks! Please submit it to the LSR, > since it is an easy solution for getting a tacet-al-fine rest > (and completely cirvumventing the real issue :-) I always try to solve the problem I have rather than the problem(s) I don’t have. ;) Submitted! Best

Re: again struggling with simultanous / stacking voices

2024-10-15 Thread Peter Chubb
> "Sebastian" == Sebastian Menge writes: Sebastian> [1 ] Hi Sebastian> I have a (organ) piece with different "voices"(?) stacking Sebastian> up to chords. Sebastian> Since this is rather homophonic, I'd not use individual Sebastian> voices - the slurs look ugly then. I think you need to .

again struggling with simultanous / stacking voices

2024-10-15 Thread Sebastian Menge
Hi I have a (organ) piece with different "voices"(?) stacking up to chords. Since this is rather homophonic, I'd not use individual voices - the slurs look ugly then. I came up with the following (hardly minimal) example. Lily gives me many warnings, so I wonder if I could make it better - and e

Re: again struggling with simultanous / stacking voices

2024-10-15 Thread Timothy Lanfear
I have the feeling I miss / don't understand something conceptually. I would like to understand why lily refuses to engrave the slur of the first fis. On the question of why the first tie does not appear: there is a note (a2) in the voice between the first and second fis1 that interrupts the

Re: Suppressing some errors in output but not others

2024-10-15 Thread Kieren MacMillan
Hi Knute, > I've tried using that function, but I get a warning that the warning wasn't > found. I put this in my input file: > #(ly:expect-warning "calculation-in-progress") Did you try #(ly:expect-warning "cyclic dependency") ?? If that doesn’t help, you’ll have to escalate it above my pay

Re: 'tacet al fine' multi-measure rest

2024-10-15 Thread Werner LEMBERG
>> This is a very nice trick, thanks! Please submit it to the LSR, >> since it is an easy solution for getting a tacet-al-fine rest >> (and completely cirvumventing the real issue :-) > > I always try to solve the problem I have rather than the problem(s) > I don’t have. ;) :-) > Submitted!

Re: [version 2.25.20] Odd behavior with unfold within volta repeat

2024-10-15 Thread Xavier Scheuer
On Tue, 15 Oct 2024 at 21:35, Nikolai Hedler wrote: > > Hello, Use the new syntax with the \alternative block outside of the \repeat volta block. Kind regards, Xavier

Re: [version 2.25.20] Odd behavior with unfold within volta repeat

2024-10-15 Thread Xavier Scheuer
On Tue, 15 Oct 2024 at 21:48, Nikolai Hedler wrote: > > The current documentation states that \alternative outside is the older syntax; I guess I'll keep doing it that way. Ah, my bad, I remembered the other way around. At least the old syntax gives the expected output. Kind regards, Xavier

Re: [version 2.25.20] Odd behavior with unfold within volta repeat

2024-10-15 Thread Nikolai Hedler
The current documentation states that \alternative outside is the older syntax; I guess I'll keep doing it that way. - Nikolai On Tue, Oct 15, 2024 at 3:42 PM Xavier Scheuer wrote: > On Tue, 15 Oct 2024 at 21:35, Nikolai Hedler wrote: > > > >> > Hello, > > Use the new syntax with the \alternat

[version 2.25.20] Odd behavior with unfold within volta repeat

2024-10-15 Thread Nikolai Hedler
The following behaves as expected: \repeat volta 2 { c1 \alternative { { d1 } { e1 } } } ... and produces a repeat section with alternate ending brackets; however, if an unfold is added thus: \repeat volta 2 { \repeat unfold 2 { c1 } \alternative { { d

Re: [version 2.25.20] Odd behavior with unfold within volta repeat

2024-10-15 Thread Xavier Scheuer
On Tue, 15 Oct 2024 at 21:54, Xavier Scheuer wrote: > > Ah, my bad, I remembered the other way around. > At least the old syntax gives the expected output. Sorry for the multiple messages within a short period of time. You can have the expected output and use the new syntax if you put the \repeat