lilypond-user
[Top][All Lists]
Advanced

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

Re: Changing clef for same part?


From: Nick Vincent
Subject: Re: Changing clef for same part?
Date: Tue, 25 Mar 2014 11:28:44 +0000

Hi David,

Thanks for your help, your assistance is much appreciated. I was simply not looking for the right terms in the manual, and am still getting my head round some of the concepts!

Cheers,

Nick


On 25 March 2014 08:47, David Kastrup <address@hidden> wrote:
Nick Vincent <address@hidden> writes:

> Hi all,
>
> I have recently discovered LilyPond and have been really amazed by how
> powerful it is.  I am using it to transcribe brass parts for a band I have
> recently joined, so please excuse the possibly dumb question.
>
> I have a song where I would like the baritone sax and trombone to play the
> same notes.  I've worked out how to do this without typing all the notes
> out twice, but can't work out how to output the two scores with different
> clefs:
>
> barisax = \relative c { c' d e f }
>
>
> \bookpart {
>
> % Baritone sax: should be in treble clef
>
> \score { \transpose bes c' { \barisax } }
>
> }
>
>
> \bookpart {
>
> % Trombone: Should be in bass clef
>
> \score { \barisax }
>
> }
>
>
> Putting \clef inside the score block results in a syntax error.

A score block accepts exactly _one_ music _expression_.  Your \score
statements above, probably more by accident than design, fit that
restriction.  \clef "bass" is a music _expression_ of its own.  To group
multiple music expressions into one, you use { ... } (namely, you need
another level of braces here).

Usually one would be more specific though, and write something like
\new Staff \with { \clef "bass" } { ... }

in order to make sure that all of the music material is put in a single
staff.

> I'm sure this must be possible, but I have scoured the internet and
> the answer has eluded me so far.

That's somewhat strange as the LilyPond manuals are easily accessible
using "the internet" and naturally contain lots of examples where such
things are done.

--
David Kastrup


reply via email to

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