[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: problems with cues
From: |
Peter Gentry |
Subject: |
RE: problems with cues |
Date: |
Tue, 17 Dec 2019 15:34:24 -0000 |
You did help David your response forces me think more clearly - when you
make a definite statement I take it on board.
I know full well how difficult it is when someone is thrashing about in
another's area of expertise and not expressing themselves clearly.
I really don't mind what might be seen as testy remarks.
If your ranting forces me to find a solution then that's good - I may even
learn something.
Cheers
-----Original Message-----
From: David Kastrup <address@hidden>
Sent: 16 December 2019 13:17
To: Peter Gentry <address@hidden>
Cc: Lilypond Users <address@hidden>; address@hidden
Subject: Re: problems with cues
"Peter Gentry" <address@hidden> writes:
> This issue has been resolved with help from David.
Unless one of the more helpful Davids on this list pitched in in private, I
would not say that I had nearly enough information available to contribute
anything that could in good conscience be called "help".
This is probably an impressively amicable rewording (a feat I am notoriously
bad at) of "Davids incessive ranting inspired me to look for the solution
myself which I ultimately did find".
> Should anyone be interested all the files can be found at
> sunscales.co.uk under the composer Farrenc.
>
>
>
> I did get a bit confused with \cueDuring and \transposedCueDuring..
The basic question here is whether LilyPond's behavior changed in a manner
that stopped previously working documents from compiling, and whether this
was something that convert-ly would have been able to fix, or should have
been able to fix but wasn't.
--
David Kastrup