I basically did as you suggested (although DevNull -> Devnull).
\theCadenza went into a separate file which was then \included in solo
and accompaniment.
The results are indescribable. Here is a sample page:
http://spamguy.cwru.edu/misc/images/violink.jpg
To summarise: the cadenza printed, fol
[EMAIL PROTECTED] writes:
> As far as I can understand, Han-Wen's suggestion was to do
> soloPart = \notes{
>...
>\theCadenzaw
>...
> }
>
> and
>
> accompaniment = \notes{
>...
>\context DevNull \theCadenza
>...
> }
>
> and since there is no such thing as a DevNull contex
As far as I can understand, Han-Wen's suggestion was to do
soloPart = \notes{
...
\theCadenzaw
...
}
and
accompaniment = \notes{
...
\context DevNull \theCadenza
...
}
and since there is no such thing as a DevNull context, LilyPond should
just ignore the cadenza music when typesetting
Do you mean something like this:
theCadenza = \notes \relative d'' {
STUFF
}
thePart = \notes {
MAIN STUFF
\context DevNull = "cadenzaMusic" << \theCadenza >>
MORE STUFF
}
If so, lily complained
warning: Cannot find or create `DevNull' called `cadenzaMusic'
I'm toying with this not because I'm to
On Tuesday 09 March 2004 15:38, Will Oram wrote:
> As described in a previous e-mail, I have a helluva large cadenza
> printed for solo violin. It is unmeasured, and it probably has a
> length only calculatable using 32nd notes. If I want to start tutti
> playing back up after the cadenza, what do
