Re: Input parser

[Han-Wen Nienhuys]

address@hidden writes:
> >     Problem that remains, is that you will have to synchronize music
> >     expressions, i.e. putting the D and the G above each other in 

> Sorry to be picky, but could you explain this example?  It looks
> like 6 sequential notes- how am I reading this wrong?

opps, you're right, I meant

     { c4 c2 c4
       < { c8 c8 d8  }
         { g4    g16 a16 } >
     }
 
> >     Write a new backend for LilyPond. Currently, we have 2 (one for
> >     notation, one for MIDI). It would be mighty cool (and very
> >     convenient for people that want to export LilyPond to whatever
> >     format) if we could have a 3rd one; one that dumps some kind
> >     synchronized music events (for example, in XML). I think that in

> Yes and no.  Everyone has their own idea of what the "most natural"
> representative format is, I think, and you're right that notation,
> MIDI-tracks, and synchronized are probably the three main forms.
> But it's arguable that synchronized will help anyone any more than
> MIDI already does.  (RG, for one, is probably most similar to the
> MIDI universe in how it thinks about music data.)  That being said,
> MusicXML etc. looks very implementable and therefore usable by more
> projects.

(Well, if MIDI suits you fine, then it's easy: just use the midi
export option -- no programming needed at all)


-- 
Han-Wen Nienhuys   |   address@hidden    | http://www.cs.uu.nl/~hanwen/