bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: crash during musicxml2ly


From: Phil Holmes
Subject: Re: crash during musicxml2ly
Date: Sat, 14 Apr 2018 14:32:59 +0100

Please see http://lilypond.org/doc/v2.19/Documentation/contributor/patches

--
Phil Holmes


"Frédéric Gohier" <address@hidden> wrote in message news:address@hidden
hello,

I face a crash when run the command line :
/usr/local/bin/musicxml2ly --nd --nrp --npl --no-beaming -m MusicXMLV2_from_sibelius7.xml

the traceback is :
Traceback (most recent call last):
 File "/usr/local/bin/musicxml2ly", line 3277, in <module>
   main()
 File "/usr/local/bin/musicxml2ly", line 3271, in main
   voices = convert(filename, options)
 File "/usr/local/bin/musicxml2ly", line 3157, in convert
   update_score_setup(score, part_list, voices, parts)
 File "/usr/local/bin/musicxml2ly", line 3027, in update_score_setup
   score_structure.set_part_information(part_id, staves_info)
File "/usr/local/share/lilypond/2.21.0/python/musicexp.py", line 2351, in set_part_information
   self.contents.set_part_information (part_id, staves_info)
File "/usr/local/share/lilypond/2.21.0/python/musicexp.py", line 2135, in set_part_information
   c.set_part_information (part_name, staves_info)
AttributeError: PartGroupInfo instance has no attribute 'set_part_information'

I correct this issue by modifying

 *   in file git/python/musicexp.py :
 *   in class StaffGroup :
 *   in function set_part_information :

   def set_part_information (self, part_name, staves_info):
       if part_name == self.id:
           self.part_information = staves_info
       else:
           for c in self.children:
+                if hasattr(c, 'set_part_information'):
+                    c.set_part_information (part_name, staves_info)
-                c.set_part_information (part_name, staves_info)


I don't know the process to validate and don't remember the process to push a modification on git server.
please can you help me ?



Cordialement,
GOHIER Frédéric




reply via email to

[Prev in Thread] Current Thread [Next in Thread]