[EMAIL PROTECTED] writes:
> > I typed in a four part tune and found that the time signature had to
> > be declared in each part. This seems strange because the time stuff
> > is handled by the score context, so I should only have to declare one
> > time signature for the music, it seems. The following version
> > works,
> >
> > Could you send a faulty example?
>
> The version I sent before was faulty. It gave a warning message.
> Here it is again:
>
> \score{
> \type StaffGroup < \time 3/2;
I get a time sig in all staffs with this one. The warning is about
the \time. It is put on a staff by itself. Since the \time `command'
(excusez le mot) has no duration, the staff is immediately removed.
I can't think of anything more elegant right now than putting \time in
either one of the staffs.
> > I could make \relative not look `inside' a \transpose.
>
> So if you did \relative \transpose MUSIC then the MUSIC would be read
> without any relative behavior?
yep.
> You already DO have to do \transpose \relative inside a .fly file for
> useful behavior, so this would be no loss.
>
> One disadvantage of printing a warning as Mats suggested is that
> you'll always see the warning if you use "\transpose \relative" inside
> a .fly file.
Yes. I don't like the warning message either. We'll add it if there
is any demand
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
