Re: musicxml2ly: proposals concerning tagline, conversion info, <source>-element and midi-output

[Patrick Schmidt]

Am 17.09.2011 um 17:01 schrieb Reinhold Kainhofer:

> Am Saturday, 17. September 2011, 16:50:33 schrieben Sie:
>> I'd like to change (and add) some minor things in musicxml2ly, but before I
>> make a patch I wanted to make sure that no-one objects:
>> 
>> 1) tagline: musicxml2ly currently uses the contents of  the
>> <software>-element for the LilyPond-tagline. So the tagline at the end of
>> a piece engraved by LilyPond actually contains information as to the
>> encoding software of the .xml-file. As this information is also saved in a
>> custom LilyPond-variable named "encodingsoftware" and the converted file
>> is actually engraved by LilyPond I'd suggest to comment out/delete the
>> following line in musicxml2ly in order to print out the standard
>> LilyPond-tagline (Music engraving by LilyPond...):
>> 
>>    set_if_exists ('tagline', ids.get_encoding_software ())
> 
> Okay.
> 
>> 2) conversion info: right now the conversion info at the top of the
>> generated .ly-file says e.g.:
>> 
>>    % automatically converted from filename
>> 
>> I'd like to change that to:
>> 
>>    % automatically converted with musicxml2ly from filename
> 
> Sounds fine.
> 
>> 3) <source>-element: musicxml2ly currently doesn't know the
>> <source>-element. I'd like to add it.
> 
> What would be the conversion result of a <source> element?
Michael Good uses the <source> element for publishing information as to the 
original edition. (See MusicXML 3.0 Tutorial, pp 16 and identity.mod)
I'd suggest a custom LilyPond-variable named "source" or "publisherinfo", e.g.:

\header {
  publisherinfo = "(Based on) Bach-Gesellschaft Ausgabe, Band 19
Leipzig: Breitkopf & Härtel, 1871. Plate B.W. XIX."
}

> 
>> 4) MIDI: musicxml2ly currently automatically comments out the midi-output
>> in the generated .ly-files. Why not leave it in by default?
> 
> If the user is interested, he can always add \midi{} himself. By default, 
> lilypond doesn't create midi, so it makes sense to me to not add midi by 
> default in musicxml2ly, either.
Okay.
> 
> You might add a cmd line option to create a midi block (and a layout block to 
> make sure a pdf is created, too).
Sounds good! I'll see what I can do.

Thanks,
patrick
> 
> Cheers,
> Reinhold
> 
> 
> -- 
> ------------------------------------------------------------------
> Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
> * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
> * http://www.fam.tuwien.ac.at/, DVR: 0005886
> * LilyPond, Music typesetting, http://www.lilypond.org