Benutzer-Werkzeuge

Webseiten-Werkzeuge


musicxml2ly:sonata2_issues

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

musicxml2ly:sonata2_issues [2013/03/13 10:42] – Externe Bearbeitung 127.0.0.1musicxml2ly:sonata2_issues [2013/09/09 23:42] (aktuell) – gelöscht reinhold
Zeile 1: Zeile 1:
-===== Issues with the Sonata Nr. 2 ===== 
- 
-  * <del>In measures 83/84, musicxml2ly messes up the note offsets, so that starting in measure 84 in the bass staff the offsets are off and chords are no longer properly detected (i.e. the < .... > around the notes are missing in the lilypond file) and instead the notes of the chords are written out one after the other.</del> 
-  * <del>The grace notes in measures 152, 155, etc. (using Finale's counting!) are not converted to .ly!</del> 
-  * <del>The after-graces in measures 25 and 109 are not converted to .ly</del> 
-  * <del>musicxml2ly does not yet convert parenthesized note heads (measure 157 in Finale).</del> 
-  * Regarding the cadenza: I'm manually trying to adjust the lilypond file to see how cadenzas should be converted, but I'm running into all sorts of trouble. How should the lilypond code for Measure 164 (Finale counting) look? The problems are: 
-    * R1 in a cadenza is always printed in the middle of the measure 
-    * Measure numbering is messed up (it prints as if nothing before the cadenza exists!) 
-    * If I pad the measure with s2. before the cadenza, the cadenza is printed in the NEXT measure 
-    * There are some voices without a cadenza, which no longer align with the voices containing the cadenza. It looks as if each voice needs to have a cadenza of the same length, otherwise voice aligning will be messed up. And no, NR section 1.2.6.2 does not apply, since the "cadenza" there does not use \cadenzaOn / \cadenzaOff 
-  * In measure 16, the rests in the lowest voice are messed up. The culprit seems to be the dotted quarter rest, during which the key change comes after the first eight... This happens in a few places at the beginning of the piece. 
-  * In measures 25, the trill is converted to \trill\startTrillSpan, which is of course redundant and crates a duplicate "tr". 
-  * Several spurious \[ ...\] are inserted into the lilypond file. 
-  * Markups like "cresc." etc are duplicated (known issue) 
-  * <del>No barline is printed in lilypond before the last measure... The reason is that the skips in voices three and four at the and of the piece are not properly counted...</del> 
-  * The handling of skips (s8*.. or s1*...) is less than sub-optimal in musicxml2ly. In particular, the skips do not properly align to measure boundaries and completely ignore the time signature, so they are very hard to read. 
-  * For voices with skips, markups are assigned to the wrong position (i.e. if there are s4*15 skips and then an s4 skip with a markup attached, the output will be s4*16^\markup{...}, which assigns the markup to the very beginning of the skips...) 
-  * Insertion of \ottava in voices with skips does not work (the pending skips are not printed out before the octavation is printed to the .ly file). 
-  * Markups consisting of multiple parts, e.g. the "I. Allegro" are split up by musicxml2ly. 
-  * Voices containing multiple voices, always use \voiceOne/\voiceTwo, even if only one of the voices is active at a time (so all stems are pointing up instead of using \oneVoice) 
- 
-==== Finale Problems in the scores ==== 
- 
-  * In measure 92, Finale messes up the staccato dot in its PDF output. That happens in a lot of places, e.g. also in the upper staff in measure 130. 
-  * Finale messes up the measure numbering starting at measure 137/138 (bottom of page 8). Although Measure 137 is a complete measure, Finale counts the whole next measure as the same measure!!! As a result the third voice (the second bass voice) in lilypond is off by a measure... The same happens in measures 206/207 (last measure of II. Andante and first measure of III. Presto), which Finale counts as one measure! 
-  * In measure 165, the cadenza is not written out by Finale to the .xml file. Some of the notes of the cadenza have <type size="cue">16th</type>, while others simply have <type>16th</type>. Other than the "cue", there is nothing in the xml file that would mark that sequence of notes as a cadenza! consequently, I don't have any way to detect these notes as cadenzas. Actually, it couldn't find anything in the MusicXML specs about cadenzas... Thus, cadenzas are not implemented in musicxml2ly. 
-  * Parenthesized notes (measure 157) are NOT exported to MusicXML 
- 
- 
-==== Files ==== 
-  * Original Finale files: {{:lilypond:musicxml2ly:sonata_no_2.xml|MusicXML}}, {{:lilypond:musicxml2ly:sonata_2_finale.pdf|PDF}} 
-  * Converted Lilypond files: {{:lilypond:musicxml2ly:sonata_no_2.ly|Lilypond}}, {{:lilypond:musicxml2ly:sonata_2_lilypond.pdf|PDF}} 
-  * Corrected Lilypond files: {{:lilypond:musicxml2ly:sonata_no_2_fixed.ly|Lilypond}}, {{:lilypond:musicxml2ly:sonata_no_2_fixed.pdf|PDF}} 
- 
-=== Original files === 
-> On Wed, Aug 20, 2008 at 2:52 PM, Simon Bielman <simon@simonbielman.com> wrote: 
-> > I converted a Finale 2007 document to MusicXML, ran 'musicxml2ly', and 
-> > ran it through LilyPond.  Here are the results, along with the 
-> > Finale-imported .XML file and the .XML file itself: 
-> > 
-> > http://www.simonbielman.com/pdf/sonata_2_finale.pdf 
-> > http://www.simonbielman.com/pdf/sonata_2_lilypond.pdf 
-> > http://www.simonbielman.com/pdf/sonata_no_2.xml 
-> > 
-> > I posted this on the IMSLP forums, and was encouraged to post it here to 
-> > try and help the project out.  Hopefully this is useful! 
- 
  
musicxml2ly/sonata2_issues.1363171349.txt.gz · Zuletzt geändert: 2013/09/09 23:42 (Externe Bearbeitung)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki