Re: program error: mis-predicted force

[Jacques Menu Muzhic]

Hello Auke,

Here is what I get with 2.19.55:

Starting lilypond 2.19.55 [Untitled (2)]...
Processing 
`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-cgabe6rk/tmpsguji5sa/document.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
programming error: bounds of this piece aren't breakable.
continuing, cross fingers
Layout output to 
`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-UUq5m5'...
Converting to `document.pdf'...
Deleting `/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T//lilypond-UUq5m5'...
Success: compilation successfully completed
Completed successfully in 0.8 ».

JM

> Le 10 mai 2017 à 21:52, Partitura Organum  a écrit :
> 
> Hi all,
> 
> Every now and again I see this error when engraving a score"program error: 
> mis-predicted force" and then a bunch of numbers. But the score looks okay so 
> I ignore it. And since the error never comes with a line in the music file 
> where the error originates I never know what is actually wrong.
> 
> Tonight it happened again. This time I have been able to narrow down the 
> source of the error to the next snippet (sort of "Minimal Error Throwing 
> Example") :
> 
> %% start
> 
> \version "2.19.59"
> 
> #(set-global-staff-size 18)
> 
> \score {
>  \new Staff
>\relative c'' {
>  \key bes \major
>   es4 d c8 cis d bes
>  \grace {a16 c}
>  }
> }
> 
>  end
> 
> All elements are needed for the error to occur. With another 
> global-staff-size: no error. Remove one of the notes: no error. Remove the 
> key signature: no error. Remove a grace note: no error
> 
> So, what am I doing wrong here?
> 
> Regards,
> Auke
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

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

Re: lilypond-user Digest, Vol 174, Issue 51

[Johan Vromans]

On Sun, 14 May 2017 13:45:22 +, Ian Ring  wrote:

> If your MusicXML contains a literal copyright character, it's invalid
> XML. Find-and-replace that to  or change it into (c) and you'll be
> good to go.

Not quite. Provided the Copyright symbol is encoded in the same encoding
as the XML document (UTF-8 (usually) or UTF-16).

In the case at hand, the Copyright symbol was 0xa9, which is a ISO-8859.1
or similar encoding.

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

Re: XML to .ly and Lilypond, again

[Johan Vromans]

On Sun, 14 May 2017 16:06:47 +0200, Urs Liska  wrote:

> But can that be? Shouldn't MusicXML allow arbitrary regular Unicode
> characters?

Yes, but the file should be encoded using a single encoding. In this case,
some parts of the file are UTF-8 encoded while other parts are UTF-16.


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

Re: XML to .ly and Lilypond, again

[Phil Holmes]

- Original Message - 
From: "Urs Liska" 

To: 
Sent: Sunday, May 14, 2017 3:06 PM
Subject: Re: XML to .ly and Lilypond, again





Am 14.05.2017 um 16:03 schrieb Phil Holmes:

I've just confirmed Ian Ring's suggestion - removing the copyright
symbol allows the conversion to continue, but results in text with
spurious null characters.


But can that be? Shouldn't MusicXML allow arbitrary regular Unicode
characters?
Urs



My understanding is the XML is like HTML and requires special characters to 
be escaped.


--
Phil Holmes 



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

Re: XML to .ly and Lilypond, again

[Urs Liska]

Am 14.05.2017 um 16:03 schrieb Phil Holmes:
> I've just confirmed Ian Ring's suggestion - removing the copyright
> symbol allows the conversion to continue, but results in text with
> spurious null characters.

But can that be? Shouldn't MusicXML allow arbitrary regular Unicode
characters?
Urs

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: XML to .ly and Lilypond, again

[Phil Holmes]

- Original Message - 
From: "Phil Holmes" 

To: "Leszek Wronski" ; 
Sent: Sunday, May 14, 2017 2:31 PM
Subject: Re: XML to .ly and Lilypond, again


- Original Message - 
From: "Leszek Wronski" 

To: 
Sent: Friday, May 12, 2017 12:54 PM
Subject: Re: XML to .ly and Lilypond, again



Dear Phil,

I read through the 2 pages of comments at the link you provided. Is
the ultimate suggestion the one in your last comment, that is, "I
believe this patch requires Python 2.7, and we ship 2.4. As a result,
windows users can no longer use musicxml2ly." ?

If so, I should just mention that I'm getting the errors on an Ubuntu
16.04 system with Python version 2.7.12.

Cheers,

Leszek.


OK - I've done some more looking at this.  Using a test file produced by 
Sibelius, I get no problems using musicxml2ly on Ubuntu 14.04, Python 
2.7.6. I think it would be helpful if people with other Ubuntu/Pytho 
versions could check an XML file (I can email my test to anyone who can 
check) to see whether the incorrect encoding of text is happening.


If I try the same file on Windows, with LilyPond 2.19.43, all is well. 
With 2.19.44 I get the same errors as Leszek:


Traceback (most recent call last):
 File "C:\Program Files (x86)\LilyPondV2.19.44\usr\bin\musicxml2ly.py", 
line 3269, in ?

   main()
 File "C:\Program Files (x86)\LilyPondV2.19.44\usr\bin\musicxml2ly.py", 
line 3263, in main

   voices = convert(filename, options)
 File "C:\Program Files (x86)\LilyPondV2.19.44\usr\bin\musicxml2ly.py", 
line 3175, in convert

   score_information.print_ly(printer)
 File "out/musicexp.py", line 855, in print_ly
 File "out/musicexp.py", line 848, in format_header_strings
 File "out/musicexp.py", line 123, in newline
 File "C:\Program Files 
(x86)\LilyPondV2.19.43\usr\lib\python2.4\codecs.py", line 501, in write

   return self.writer.write(data)
 File "C:\Program Files 
(x86)\LilyPondV2.19.43\usr\lib\python2.4\codecs.py", line 178, in write

   data, consumed = self.encode(object, self.errors)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xa9 in position 39: 
unexpected code byte


However, if I try a file with a simpler header (e.g. 
02d-Rests-Multimeasure-TimeSignatures.xml in the regtest suite), then the 
script runs successfully, but I get an output file with spurious nulls in 
text fields:


\header {
texidoc =
"Multi-Measure 
rests should 
always 
  be 
converted into 
durations that 
are a multiple 
of the time 
  
signature."


}

So it looks clear that something probably introduced in 
https://sourceforge.net/p/testlilyissues/issues/4751/ is causing encoding 
problems on Windows.  As I say, I can't reproduce the problem on Linux.


--
Phil Holmes



I've just confirmed Ian Ring's suggestion - removing the copyright symbol 
allows the conversion to continue, but results in text with spurious null 
characters.


--
Phil Holmes 



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

Re: lilypond-user Digest, Vol 174, Issue 51

[Ian Ring]

If your MusicXML contains a literal copyright character, it's invalid XML. 
Find-and-replace that to  or change it into (c) and you'll be good to go.

I've had to do that with XML output from MuseSore.
Cheers

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

Re: XML to .ly and Lilypond, again

[Phil Holmes]

- Original Message - 
From: "Leszek Wronski" 

To: 
Sent: Friday, May 12, 2017 12:54 PM
Subject: Re: XML to .ly and Lilypond, again



Dear Phil,

I read through the 2 pages of comments at the link you provided. Is
the ultimate suggestion the one in your last comment, that is, "I
believe this patch requires Python 2.7, and we ship 2.4. As a result,
windows users can no longer use musicxml2ly." ?

If so, I should just mention that I'm getting the errors on an Ubuntu
16.04 system with Python version 2.7.12.

Cheers,

Leszek.


OK - I've done some more looking at this.  Using a test file produced by 
Sibelius, I get no problems using musicxml2ly on Ubuntu 14.04, Python 2.7.6. 
I think it would be helpful if people with other Ubuntu/Pytho versions could 
check an XML file (I can email my test to anyone who can check) to see 
whether the incorrect encoding of text is happening.


If I try the same file on Windows, with LilyPond 2.19.43, all is well.  With 
2.19.44 I get the same errors as Leszek:


Traceback (most recent call last):
 File "C:\Program Files (x86)\LilyPondV2.19.44\usr\bin\musicxml2ly.py", 
line 3269, in ?

   main()
 File "C:\Program Files (x86)\LilyPondV2.19.44\usr\bin\musicxml2ly.py", 
line 3263, in main

   voices = convert(filename, options)
 File "C:\Program Files (x86)\LilyPondV2.19.44\usr\bin\musicxml2ly.py", 
line 3175, in convert

   score_information.print_ly(printer)
 File "out/musicexp.py", line 855, in print_ly
 File "out/musicexp.py", line 848, in format_header_strings
 File "out/musicexp.py", line 123, in newline
 File "C:\Program Files 
(x86)\LilyPondV2.19.43\usr\lib\python2.4\codecs.py", line 501, in write

   return self.writer.write(data)
 File "C:\Program Files 
(x86)\LilyPondV2.19.43\usr\lib\python2.4\codecs.py", line 178, in write

   data, consumed = self.encode(object, self.errors)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xa9 in position 39: 
unexpected code byte


However, if I try a file with a simpler header (e.g. 
02d-Rests-Multimeasure-TimeSignatures.xml in the regtest suite), then the 
script runs successfully, but I get an output file with spurious nulls in 
text fields:


\header {
texidoc =
"Multi-Measure 
rests should 
always 
  be 
converted into 
durations that 
are a multiple 
of the time 
  
signature."


}

So it looks clear that something probably introduced in 
https://sourceforge.net/p/testlilyissues/issues/4751/ is causing encoding 
problems on Windows.  As I say, I can't reproduce the problem on Linux.


--
Phil Holmes 



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

Re: XML to .ly and Lilypond, again

[Robert Blackstone]

Hi David,

Ref.: "What's the role of TeXShop? What process did it carry out? "

TeXShop, by means of its LilyPond Engine, processed the file containing the 
code copied from Frescobaldi. I processed the file with two LilyPond versions, 
2.18.2 and 2.19.58.1, and as far I could see the results were identical. 
I always use TeXShop to edit LilyPond-files because it allows me to use some 
tricks and shortcuts that Frescobaldi does not like, or does not allow. As 
TeXShop always saves files with the extension .tex I rename the copies 
(_ly.tex). So the pdf in the package I uploaded was made with TeXShop. 
Incidentally, It is not really necessary to make a copy of the code generated 
by Frescobaldi from the xml-file. I can open and process the .ly -file with 
TeXShop just as well. But for most of the scores I make I have to do quite a 
lot of editing for which I always use TeXShop. 

Ref.: "The 2.19 files might be of more interest as 2.18.2 doesn't have the 
problem."

There is no separate and/or different 2.19 file. The .ly -file generated from 
the downloaded -xml-file produced the same result with  2.18.2 and 2.19.58.1.

Best regards,

Robert


On 14 May 2017, at 14:24 , David Wright  wrote: 
  

> On Sun 14 May 2017 at 12:42:03 (+0200), Robert Blackstone wrote:
>> Hi Leszek, 
>> 
>> Out of curiosity I downloaded and processed the Kyrie.xml, from the link you 
>> attached to your post of 12-05-17. 
>> I was curious in particular because I mostly use the same procedure for 
>> engraving with LilyPond as you do, starting with Finale, except that I'm on 
>> a Mac (OSX 10.9.5 also known as Mavericks).
>> So I imported your file in Frescobaldi, and then copied and pasted it in 
>> TeXShop, my favourite editor, which processed your file without any problem 
>> (both with LilyPond version 2.18.2 and 2.19.58.1). 
> 
> So with Frescobaldi you import the XML (which uses the musicxml2ly
> program; you posted the .ly) and then produce the PDF (posted).
> What's the role of TeXShop? What process did it carry out?
> 
>> You can find the results here: 
>> 
>> https://dl.dropboxusercontent.com/u/512573/FileChute/LilyPond-test_Kyrie_from_xml-file.zip
> 
> The 2.19 files might be of more interest as 2.18.2 doesn't have the problem.
> 
>> So apparently for a Mac there is nothing wrong, neither with your xml-file 
>> nor with recent musicxml2ly.
>> It may be of litte help to you (as  long as you stay on Windows ;-)) but it 
>> could perhaps help you in narrowing down the search for the source of 
>> trouble in your system.
> 
>> On 12 May 2017, at 13:42 , Leszek Wroński  wrote:
>>> […] Anyway, since one and the same XML file stopped
>>> converting correctly, it indeed seems that in the meantime some
>>> encoding issues have been introduced to musicxml2ly (I'm using 2.19.48
>>> now).
> 
> Cheers,
> David.


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

Re: XML to .ly and Lilypond, again

[David Wright]

On Sun 14 May 2017 at 12:42:03 (+0200), Robert Blackstone wrote:
> Hi Leszek, 
> 
> Out of curiosity I downloaded and processed the Kyrie.xml, from the link you 
> attached to your post of 12-05-17. 
> I was curious in particular because I mostly use the same procedure for 
> engraving with LilyPond as you do, starting with Finale, except that I'm on a 
> Mac (OSX 10.9.5 also known as Mavericks).
> So I imported your file in Frescobaldi, and then copied and pasted it in 
> TeXShop, my favourite editor, which processed your file without any problem 
> (both with LilyPond version 2.18.2 and 2.19.58.1). 

So with Frescobaldi you import the XML (which uses the musicxml2ly
program; you posted the .ly) and then produce the PDF (posted).
What's the role of TeXShop? What process did it carry out?

> You can find the results here: 
> 
> https://dl.dropboxusercontent.com/u/512573/FileChute/LilyPond-test_Kyrie_from_xml-file.zip

The 2.19 files might be of more interest as 2.18.2 doesn't have the problem.

> So apparently for a Mac there is nothing wrong, neither with your xml-file 
> nor with recent musicxml2ly.
> It may be of litte help to you (as  long as you stay on Windows ;-)) but it 
> could perhaps help you in narrowing down the search for the source of trouble 
> in your system.

> On 12 May 2017, at 13:42 , Leszek Wroński  wrote:
> > […] Anyway, since one and the same XML file stopped
> > converting correctly, it indeed seems that in the meantime some
> > encoding issues have been introduced to musicxml2ly (I'm using 2.19.48
> > now).

Cheers,
David.

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

Re: XML to .ly and Lilypond, again

[Robert Blackstone]

Hi Leszek, 

Out of curiosity I downloaded and processed the Kyrie.xml, from the link you 
attached to your post of 12-05-17. 
I was curious in particular because I mostly use the same procedure for 
engraving with LilyPond as you do, starting with Finale, except that I'm on a 
Mac (OSX 10.9.5 also known as Mavericks).
So I imported your file in Frescobaldi, and then copied and pasted it in 
TeXShop, my favourite editor, which processed your file without any problem 
(both with LilyPond version 2.18.2 and 2.19.58.1). 

You can find the results here: 

https://dl.dropboxusercontent.com/u/512573/FileChute/LilyPond-test_Kyrie_from_xml-file.zip

So apparently for a Mac there is nothing wrong, neither with your xml-file nor 
with recent musicxml2ly.
It may be of litte help to you (as  long as you stay on Windows ;-)) but it 
could perhaps help you in narrowing down the search for the source of trouble 
in your system.

Best regards

Robert Blackstone




On 12 May 2017, at 13:42 , Leszek Wroński  wrote:

> Dear Guys,
> 
> first, thank you very much for the replies!
> 
> Second, for a little bit of detective work. I have not updated my
> Finale in years, so if it produced correct XML files in the past, it
> should do the same now (I always write using a similar really basic
> setup, since actual editing is to be done in Lilypond). Anyway, I
> tracked down an XML file which converted correctly in 2.19.5. I wanted
> to check whether I would get the 'lots of null characters' problem
> currently. To my surprise, I didn't even get to that part. Musicxml2ly
> gave me the following:
> 
> --
> musicxml2ly: Reading MusicXML from Kyrie.xml ...
> musicxml2ly: Converting to LilyPond expressions...
> (.)
> musicxml2ly: Output to `Kyrie.ly'
> Traceback (most recent call last):
>  File "/home/leszek/lilypond/usr/bin/musicxml2ly", line 3269, in ?
>main()
>  File "/home/leszek/lilypond/usr/bin/musicxml2ly", line 3263, in main
>voices = convert(filename, options)
>  File "/home/leszek/lilypond/usr/bin/musicxml2ly", line 3175, in convert
>score_information.print_ly(printer)
>  File "/home/leszek/lilypond/usr/share/lilypond/current/python/musicexp.py",
> line 855, in print_ly
>self.format_header_strings(k, v, printer)
>  File "/home/leszek/lilypond/usr/share/lilypond/current/python/musicexp.py",
> line 848, in format_header_strings
>printer.newline()
>  File "/home/leszek/lilypond/usr/share/lilypond/current/python/musicexp.py",
> line 123, in newline
>self._file.write (self._line + '\n')
>  File "/home/leszek/lilypond/usr/lib/python2.4/codecs.py", line 501, in write
>return self.writer.write(data)
>  File "/home/leszek/lilypond/usr/lib/python2.4/codecs.py", line 178, in write
>data, consumed = self.encode(object, self.errors)
> UnicodeDecodeError: 'utf8' codec can't decode byte 0xa9 in position
> 19: unexpected code byte
> 
> 
> (Isn't '0xa9' the copyright character? ;))
> 
> The XML file, if someone wants to take a peek, is here:
> https://www.dropbox.com/s/1dnv1hthyp7ss5h/Kyrie.xml?dl=0
> 
> Unfortunately it seems I do not have an XML file about which I could
> be sure that it converted correctly using a version of Lilypond newer
> than 2.19.5. Anyway, since one and the same XML file stopped
> converting correctly, it indeed seems that in the meantime some
> encoding issues have been introduced to musicxml2ly (I'm using 2.19.48
> now).
> 
> If you think I could be of any additional help (well, not sure this
> was helpful at all, but I'm trying ;)), please tell me what info I
> should provide.
> 
> Cheers and thank you again,
> 
> Leszek.
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

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

Re: XML to .ly and Lilypond, again

[zs.hassia]

>On Fri 12 May 2017 at 12:03:36 (+0200), David Kastrup wrote:
>

>My guess is that the wrong encoding comes from "original" strings
>being passed from the input to the output as opposed to all the
>normal strings that are generated by the conversion program. These
>original strings would carry their encoding with them.
>
>
If you are meaning finale is producing the wrong xml, I can tell you
Sibelius, musescore and capella also have this problem.


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