Nightly crashes when trying to view newly edited parts
I posted this under support and bug reports, but maybe I should have posted it here in the first place?
I have been using Nightly f794aee on my Windows 8 laptop without problems. (The problem persists with MuseScoreNightly-2014-11-06-2008-fd82ab6.)
After editing the flute and the violin voices and creating the parts for my score (V2), the Nightly always crashes when I try to view the violin or the flute part. All other parts work fine.
I managed to get a working copy by exporting as Music XML, then opening that in an HTML editor and saving it after minimal editing. Opening that score in the Nightly resulted in a copy where I can view all parts without problems. However, in that copy (V2a) there are no pizzicato channels that I can select, whereas pizzicato works fine in the original score.
Can someone please look at those almost identical scores and tell me what is wrong with each of them?
| Attachment | Size |
|---|---|
| Coultergeist_V2_Alle.mscz | 128.98 KB |
| Coultergeist_V2a_Alle.mscz | 94.66 KB |
Comments
I read your initial report but I must say it was confusing to understand. Could you skip that part of MusicXML and just focus on the crash plus the exact steps the reproduce? Make it as simple as possible and discard unneeded info. Thanks.
In reply to Steps by Thomas
Simple, open the 1st attachment in the latest nightly build, click on the flute or violin tab -> crash
In reply to Simple, open the 1st by Jojo-Schmitz
That is nicely simplified. It states what action leads to the crash succintly.
However it doesn't tell how I arrived at the 2nd attachment which doesn't lead to a crash when clicking on the flute or violin tab.
And it doesn't ask for why the second attachment won't play pizzicatos.
Meanwhile I have used file compare to find out that a whole lot of code seems to get lost when saving as MusicXML, including the code that's responsible for pizzicato channels and switching to them. Is that correct?
Meanwhile I have also seen in the code that - due to having created the piano and the bass parts first, then creating all parts at once and deleting the second copies of the piano and bass parts - midi-channel ids for the five parts were not numbered 1 to 5, but 1 to 2, and 5 to 7. I don't know whether that might cause the problem? (Deleting all parts and recreating them all at once did not solve the problem, however. Actually, now (with V2m) the nightly also crashes upon clicking on the bass tab. Does that tell you anything?)
P.S.: The same happens with another score, now that I have added a flute part. Clicking on the newly created flute tab will result in a crash :-(.
And exporting all parts to PDF will create all but the flute part. The flute part is 0 Bytes and the nightly crashes while trying to create its PDF.
In reply to That is nicely simplified by pseller
MusicXML indeed cannot store all information that is in a MSCZ file - it's designed to capture that which can portably transfer between different programs. Which isn't to say it might not be possible to figure out a way, but just to set expectations - it's never going to capture everything, and details like how MuseScore sets up multiple "channels" for certain instruments seems like exactly the sort of thing it might not get.
As for the crash - was this score created entirely within the Beta and/or later builds, or was it by any chance started at some point earlier? If it was ever worked on using a pre-Beta build of 2.0, that could explain the crash right there. There have been incompatible changes made over the course of 2.0 development, and scores created earlier this year do not work correctly, nor should they be expected to. We are making every effort to make sure scores created with Beta or later builds continue to work, though.
If this score was created entirely post-Beta, then anything you can tell us about *how* it was created would be useful. Did you start with new score created from scratch? From template? By importing a score from 1.3, from MusicXML, or some other format?
Sounds like what you described in terms of the order in which you created parts might have something to do with it, so any additional info - ideally, steps to reproduce the problem in a new score created from scratch - would be very helpful!
In reply to MusicXML indeed cannot store by Marc Sabatella
Some remarks that could explain fully or partially (more likely?) these problems.
Watch the Voltas e.g. -> "Line properties" You see a curious font text:
The XML Export fixes this, but then, in each part, several Voltas overlapping (and it misses the point 1. or 2.)
![volta.jpg]( "volta.jpg")
As already said, it would essential to know if this score was a new score created from scratch, from a template, imported from 1.3, from MusicXML, or other format.
In reply to Some remarks that could by cadiz1
Thanks for pointing out the volta issue. However, I don't see how that could explain my crash problem. I can click on some tabs (e.g. Bandoneon) without it crashing, even though the Bandoneon part also contains that volta issue.
I think that the several overlapping voltas were created by me since I initially had problems in creating them. And the font text was there, because I inserted some explanatory text which I later deleted, I believe.
The Bando score doesn't contain any voltas, only D.S. al Coda, etc. Still the crash problem also exists with the Bando score.
In reply to MusicXML indeed cannot store by Marc Sabatella
Thanks, Marc, for taking up my problem.
The Coultergeist score was originally imported into MuseScore beta 1 as Music XML from Sibelius. (Actually, I now remember that I had problems importing the Music XML created by Sibelius into MuseScore beta 1. I solved them by first opening the Music XML file in MuseScore 1.3, saving it as mscx, then opening that in MuseScore beta 1). The recent changes were made using Nightlys from Oct and November. As long as I didn't add another instrument (the flute), MuseScore never crashed.
The Bando score was read by PhotoScore Ultimate 7 from a PDF, then imported as Music XML into a Nightly. I modified the instruments. The crash only occurred this week when I added the flute part. I did so by copying passages from other parts and transposing or manually changing them.
I just tested with the Bando score what happens when I delete all parts, save the score, and then recreate all parts at once. Unfortunately, that results in crashes when I click on any part tab now. The same happens when I just create one part and click on its tab.
I again managed to circumvent the problem by saving the score as Music XML and opening that. However, I first received an error message about an invalid kind element (see attachment). I had to replace all empty {syntaxhighlighter SPEC}{/syntaxhighlighter} tags by {syntaxhighlighter SPEC}minor{/syntaxhighlighter}, before I was able to open the Music XML score without error mesages. Then I was able to create all parts and view them without problems.
With an older version of the Bando score which didn't yet contain the flute part, I just tested that I'm able to view all parts tabs. Once I add a flute, copying the transposed bass voice into the flute staff, then creating the flute part and click on its tab, it crashes again. Again, I was able to circumvent the problem as described above.
Does that help you in spotting the source of the problem?
P.S. One thing that also occurs to me as strange is that after opening the Music XML file - which I create to circumvent the above problem - I need to manually enter all the instrument names for the parts (see attachment). Is that normal?
In reply to Imported as Music XML from Sibelius into MuseScore beta 1 by pseller
Knowing that the problem score was the resultof MusicXML import helps. It suggests that if you post the MusicXML file you started with and give precise steps to get from there to some sort of problem, that will make a nice bug report that someone can hopefully fix.
As for the "kind" tag error, please give the original MusicXML file from the other program and list the specific steps to reproduce that problem from there, too.
In reply to Knowing that the problem by Marc Sabatella
I can post the original Music XML of the Coultergeist score which came from Sibelius.
I can also post the first full version of the Bando score (Piazzolla - Bando.xml) after reading the PDF using PhotoScore Ultimate 7. (I started trying out with just the first page, then decided to do it for the full score.)
I will also post the first mscz version of the Bando score (Piazzolla - Bando.mscz).
The "kind" tag error only occurred when trying to open the Music XML file which I created to circumvent the crash problem when clicking on the newly added flute part tab. I will also post that Music XML file (Bando-Partitur_V2_with_invalid_kind_tags.xml) then, along with the mscz file from which it was saved. Finally, I also post the Music XML file (Bando-Partitur_V2.xml) with valid kind tags, which allows me to click on all part tabs.
In reply to Original files by pseller
I get an error message trying to load Piazzola - Bando.xml, then a crash if I ignore the error. This is the file that came from PhotoScore? How did you get it into MuseScore?
I still can't figure out how to reproduce the "kind" problem. I tried importing Bando-Partitur_V2.xml, then imeddiately exporting that to another XML file, then importing the file I just exported. I got no error. So there must be more to the process?
At this point, it's kind of hard to keep this all straight. I'd recommend you post a separate thread for each problem. Right now, I personally am interested in the "kind" problem, because that is the only one that deals with an area of code I know anything about. So maybe start with that? Post the XML you started with (the one that was not created by MuseScore), then exact step by step instructions on how to get from there to the "kind" error.
In reply to Steps by Thomas
See below
The "kind" problem can be reproduced by
- starting with Bando-Partitur_V2.mscz (the file that leads to the crash upon clicking the flute tab)
- creating a Music Xml file from it and trying to open that in MuseScore Nightly.
The Music Xml file Bando-Partitur_V2.xml which I posted is the file after replacing empty "kind" tags, which doesn't crash any more.
I will have to respond to the other issue tomorrow.
Thanks,
Peter
In reply to The "kind" problem by pseller
I recognize you can get errors starting with the mscz file, but I that file may already be corrupt. I am trying to understand how that happened - how to reproduce the problem starting only from the MusicXML file you got from the other program.
In reply to I recognize you can get by Marc Sabatella
I have tried to reconstruct what I did, starting from the original PhotoScore-generated Music XML Bando score which I posted. You are right, it cannot be opened without errors in MuseScore 2.0. I think I circumvented that problem by opening it in MuseScore 1.3, saving it as .mscz, and then opening it in MuseScore 2.0 beta 1.
In order to allow you to follow that path, I'm attaching the .mscz file (Piazzolla - Bando reconstruction) saved by MuseScore 1.3, which I then edited in MuseScore 2.0 beta 1.
I'm also attaching the first Bando score (Piazzolla - Bando Partitur Neu.mscx) where all instruments are arranged together, which I produced from the former material where the instrument scores were written down consecutively.
Please note that I only got the crash much more recently when adding the flute.
Do you think that the fact that I used MuseScore 1.3 early on, in order to get the original Music XML file opened in MuseScore, may explain the crash problem, occurring only so much later in the process?
In reply to Reconstructing the path by pseller
It could be. I think the real problem is the original input file (from the other program) itself. The fact that 2.0 gives you error messages is a sign the file is in fact *not* a valid MusicXML file - it has some sort of errors in it. 1.3 might have silently ignored those errors but produced a corrupt score. Right now, though, there are still a few too many variables too allow a solid determination.
In reply to It could be. I think the by Marc Sabatella
I don't get any more crashes with the slightly revised version of Bando (Bando-Partitur_V3_mscz).
I'm not sure what made the difference. But maybe you can find out by comparing Bando-Partitur_V2_mscz with it?
Hmm, I just tested creating the parts and clicking on them with Bando_V2_mscz, and I don't get any crashes there either. I don't know why. Maybe it has to do with the fact that I saved it as mscx in between. Maybe it has to do with the fact that I'm now using the Nightly R.bbe146b from Nov 12? What was changed recently that might have made the difference?