Re: [Rosegarden-devel] Extending Lilypond export

[Chris C. <chr...@fe...>]

Peter Mogensen writes:
> After
> thinking a bit about it, I realize that using Rosegarden/Lilypond for
> arranging band music can be made a lot easier simply by improving the
> Lilypond export. Looking at the Rosegarden source, I can see that this
> would be pretty straight forward.

Those are words I like to hear - especially the last bit!

> I'm thinking of features like:
> 
> * Separating score-definition from voice definition, making it easier to
> edit the Lilypond file to build different scores by combining voices in
> different ways.

Yes.  We currently output legit but badly-structured Lilypond and doing it "right" in structural terms would be an excellent next move.  This is probably trickier than the other points in your list but well worth tackling. 

> * Adding as much info as possible to each voice. Ex: Currently
> "transposition" is not exported.

Great. 

> * Adding an option to let GM percussion Tracks be exported with Lilypond
> percussion notation.

Rosegarden's own Instrument has a percussion property that can (and should) be queried here - this is what is used for the Percussion Matrix (if you're running Rosegarden from CVS) and will be used for percussion staffs one day (feel free to implement those too!). 

> * Fixing a few bugs like octavated clefs not being exported as such.

Splendid. 

Yep, we'd love to see any work in these areas.  The Lilypond export code has had several people work on it but has no overall "owner" so you won't be trading on anyone's toes.  Any questions about it, just ask. 


Chris