Damn webmail ... I've got it! The result is a bit of a mess but it seems to work.
I store all my notes in a voiceXxx.ly file, so my voiceTromnbone file now contains a "\transpose c' bf" if the part's in Bb. And all my formatting and score stuff is in a partXxx.ly file, so if I'm outputting a Bb part, that contains a "\transpose bf c'". Apologies if I've been a bit dense, but it didn't cross my mind until after bouncing all this around that I could have two \transpose directives, which would have the net effect of cancelling each other out. I think it's one of those "obvious when you know how" moments :-) Cheers, Wol [EMAIL PROTECTED] wrote: > I'm coming at it from a very different angle. I don't give a damn about MIDI, > and I'm using lilypond as a music-typesetting program (which, indeed, I > thought it was). And I play an instrument which, in a different way, is as > unusual as the horn changing pitch half-way through a piece. Depending on the > whim of the composer (well, not quite), music for me can be written in C or > in Bb. When I'm looking at my .ly files, I can't say "that's the trombone, > therefore those notes are concert pitch". When I saw the transpose directive, > I missed the bit about "midi only", and thought "great - I can enter the > notes in Bb, and that will tell lilypond how to convert it to C". > > I *really* *don't* *want* to have half my music with a "transpose bf c" > directive in it, and the other half with "transpose c bf" in it. The current > option is to transpose all the Bb parts in my head as I enter them (or work > out how to get that editor to do it for me). It'd be nice if lily could do it > for me. > _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user