[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Coda ahead of a line of its own

From: Jacques Menu
Subject: Re: Coda ahead of a line of its own
Date: Tue, 23 Dec 2014 20:34:00 +0100


Thanks for the detailed answers. Having two scores is a way to avoid the 
difficulty, but this implies that you should set bar numbers and mark numbers 
manually in the second (coda) score.

Would a \once\override of layout indent and something similar to the instrument 
name be a feasible solution?

A happy end of the year!


> Le 23 déc. 2014 à 16:55, David Kastrup <address@hidden> a écrit :
> Federico Bruni <address@hidden> writes:
>> 2014-12-23 16:31 GMT+01:00 Kieren MacMillan <address@hidden>:
>>> Hi all,
>>>>> I'd personally avoid using stopStaff for codas.
>>>>> Creating a new score for the coda is much easier
>>>> definitely a better idea, thanks
>>>> it's worth adding it to the LSR?
>>> It’s probably worth adding to the LSR…
>>> But I strongly disagree with the suggestion that it’s a "better solution”:
>>> it divides a single musical “piece” (work, expression, whatever) into two
>>> separate scores just to accomplish an engraving issue which should be as
>>> easy as using \repeat volta. Now everything (e.g., parts, midi, etc.)
>>> requires double-scoring or recombining of variables, etc.
>>> There’s a better way — we should try to make it happen.
>> Do we have an issue for this?
>> This is the only one I could find:
>> https://code.google.com/p/lilypond/issues/detail?id=3752
>> and I'm not sure what it really intends to do...
> Have a \repeat coda command for repeats with coda, and a \repeat fine
> command for repeats with fine.  I thought that was obvious.  If you find
> that the problem description is deficient, please add a comment to the
> issue.
> -- 
> David Kastrup
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user

reply via email to

[Prev in Thread] Current Thread [Next in Thread]