Ooops, that one escaped me…:

  In: <measure width=246.96 number=45>

JM

> Le 1 mai 2017 à 01:00, Jacques Menu Muzhic <imj-muz...@bluewin.ch> a écrit :
> 
> Hello Don,
> 
> Thanks for the invoice.
> 
> With MuseScore 2.0.3 and musicxml2ly 2.19.55, I get the same as you:
> 
> menu@macbookprojm:~/Documents/LaTeX/PartitionsLilypond/regular > musicxml2ly 
> Mr_BojanglesJMI.xml 
> musicxml2ly: Reading MusicXML from Mr_BojanglesJMI.xml ...
> musicxml2ly: warning: overfull measure? Expected: 34, Difference: -1/8
>   In: <measure width=246.96 number=45>
> 
>   In: <part id=P1>
> 
>   In: <score-partwise >
> 
> musicxml2ly: Converting to LilyPond expressions...
> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
> musicxml2ly: warning: Negative skip -1/8 (from position 139/4 to 277/8)
> musicxml2ly: Output to `Mr_BojanglesJMI.ly <http://bojanglesjmi.ly/>'
> musicxml2ly: warning: Encountered unprocessed marker 
> <musicxml2ly_conversion.EndingMarker instance at 0x106114b48>
> 
> musicxml2ly: Converting to current version (2.19.55) notations ...
> 
> 
> It turns out that:
> 
>       1) musicxml2ly does not like multiple <words/> attached to one note (a 
> rest here):
> 
>     <measure number="27" width="168.46">
>       <direction placement="below">
>         <direction-type>
>           <words>can modulate to D7
> </words>
>           <words> and repeart &quot;Please&quot;
> </words>
>           <words> on verse 5</words>
>           </direction-type>
>         </direction>
>       <note>
>         <rest/>
>         <duration>6</duration>
>         <voice>1</voice>
>         </note>
>       </measure>
> 
> They get translated as separate items:
> 
>             \alternative { {
>                     _ "can modulate to D7" _ "on verse 5" | % 28
>                     R2. }
>                 } _ "and repeart " Please"" \bar "||"
>             }
> 
> 
>       2) measure 45 has an extra eighth rest (under "1. 2."), hence the « 
> overfull measure » message. It’s a pity that the faulty input line it not 
> indicated, though:
> 
>     <measure number="45" width="246.96">
>       <barline location="left">
>         <ending number="1" type="start"/>
>         </barline>
>       <note>
>         <rest/>
>         <duration>4</duration>
>         <voice>1</voice>
>         <type>half</type>
>         </note>
>       <note>
>         <rest/>
>         <duration>2</duration>
>         <voice>1</voice>
>         <type>quarter</type>
>         </note>
>       <note>
>         <rest/>
>         <duration>1</duration>
>         <voice>1</voice>
>         <type>eighth</type>
>         </note>
>       <barline location="right">
>         <bar-style>light-heavy</bar-style>
>         <ending number="1" type="stop"/>
>         <repeat direction="backward"/>
>         </barline>
>       </measure>
> 
> The measure number can be computed, given that there are 2 divisions to a 
> quarter note in part « P1 »:
>         <divisions>2</divisions>
> 
> 3/4 gives 6 divisions per full measure, and there are no time signature 
> changes, so 271/6 = 45.166666666666667, hence measure 45.
> 
> HTH!
> 
> JM
> 
> 
>> Le 30 avr. 2017 à 18:59, Don Gingrich <gingr...@internode.on.net 
>> <mailto:gingr...@internode.on.net>> a écrit :
>> 
>> On Sun, 30 Apr 2017 14:09:50 Jacques Menu Muzhic wrote:
>>> Hello Don,
>>> 
>>> I found a slight bug in MuseScore 2.0.3 recently (wrong order of some XML
>>> markups in export), that will be fixed in 2.04.
>>> 
>>> Coud you send me your origianl MuseScore file privately? I’d like to perform
>>> some experiments.
>>> 
>>> Thanks!
>>> 
>>> JM
>> 
>> musicXML2ly output follows: (note that I renamed the ML file so that I 
>> didn't 
>> clobber the lilypond file that I'd worked on.)
>> 
>> 
>> musicxml2ly Mr_Bojangles2.xml
>> musicxml2ly: Reading MusicXML from Mr_Bojangles2.xml ...
>> musicxml2ly: warning: overfull measure? Expected: 34, Difference: -1/8
>>  In: <measure width=247.17 number=45>
>> 
>>  In: <part id=P1>
>> 
>>  In: <score-partwise >
>> 
>> musicxml2ly: Converting to LilyPond expressions...
>> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
>> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
>> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
>> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
>> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
>> musicxml2ly: warning: Negative skip -1/8 (from position 34 to 271/8)
>> musicxml2ly: warning: Negative skip -1/8 (from position 139/4 to 277/8)
>> musicxml2ly: Output to `Mr_Bojangles2.ly <http://bojangles2.ly/>'
>> musicxml2ly: warning: Encountered unprocessed marker <__main__.EndingMarker 
>> instance at 0x7fd119655638>
>> ----------------------------------
>> musicxml2ly --version
>> musicxml2ly (LilyPond) 2.18.2
>> 
>> Copyright (c) 2005--2012 by
>>    Han-Wen Nienhuys <han...@xs4all.nl <mailto:han...@xs4all.nl>>,
>>    Jan Nieuwenhuizen <jann...@gnu.org <mailto:jann...@gnu.org>> and
>>    Reinhold Kainhofer <reinh...@kainhofer.com 
>> <mailto:reinh...@kainhofer.com>>
>> 
>> This program is free software.  It is covered by the GNU General Public
>> License and you are welcome to change it and/or distribute copies of it
>> under certain conditions.  Invoke as `lilypond --warranty' for more
>> information.
>> ------------------------------------------------------------
>> 
>> I hope this is useful.
>> 
>> Cheers,
>> 
>> -Don
>> 
> 

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to