RE: Removing the key signature without loosing accidentials

[Sven Axelsson]

OK, that would be:

\context {
  \Staff
  \override KeySignature #'transparent = ##t
}

That seems to put accidentials on all the notes instead. Bagpipe music is a
bit special. The scale is somewhat like D major (with two sharps) but it is
written with no accidentials. But I still want the option to have "special"
accidentials visible, so my current solution with
\remove "Key_engraver"
\remove "Accidental_engraver"
doesn't work right here. The reason I'm not just pretending to use C major is
that I want a midi file that sounds at least somewhat like the real thing.
Perhaps another solution is to apply the correct pitch only on generating the
midi file. Can this be done?

-- 
P/S Sven Axelsson, The Murray Pipes & Drums of Gothenburg
 

> -----Original Message-----
> From: Mats Bengtsson [mailto:address@hidden 
> Sent: den 3 januari 2005 12:56
> To: Sven Axelsson
> Cc: address@hidden
> Subject: Re: Removing the key signature without loosing accidentials
> 
> Why not simply use the property 'transparent' of the KeySignature
> layout object?
> 
>     /Mats
> 
> Sven Axelsson wrote:
> > Hello List.
> > 
> > This question is for Lilypond 2.4.2.
> > 
> > I've recently started to use Lilypond for typesetting music 
> for the Highland
> > Bagpipe, having used MusicTeX for many years before. The 
> bagpipe specific
> > stuff is working fine - I started out with Andrew McNabb's 
> definitions and
> > changed a lot of stuff to better suit my previous work.
> > 
> > One peculiarity for bagpipe music is that it is written as 
> in C major (no
> > accidentials) when it actually is using a \key a 
> \mixolydian. I am dealing
> > with this now by brute force:
> > 
> > \layout {
> >   \context {
> >     \Staff
> >     \remove "Key_engraver"
> >     \remove "Accidental_engraver"
> >   }
> > }
> > 
> > But this means that I can't use accidentials on the (very 
> few) places where
> > they actually should be used. I guess I can always do e.g. 
> c^\markup{\flat},
> > but it isn't the same. Is there a better way?
> >