Fill With Slashes ... Crashes
Select a staff fm beginning to end and "fill with slashes" … crash
Please, check these logs
| Attachment | Size |
|---|---|
| FillWithSlashes.zip | 123.92 KB |
Do you still have an unanswered question? Please log in first to post your question.
Comments
In order to investigate, we'd need you to attach the actual score and precise steps to reproduce - crash logs aren't very helpful.
In general, Fill with Slashes works just fine; I use it very often with no problems. I could imagibne a crash happening if your score is corrupt.
In reply to In order to investigate, we'd by Marc Sabatella
1- Add a staff (pad synth), delete the bass clef and place it over piano
2- change its property from PAD to Chords
3- select that staff fm beginning to end and Fill with slashes
. . . . . . . crash
In reply to 1- Add a staff (pad synth), by danworks
Can you attach the "original" import XML file please?
Because:
Minimal crash: DanzaMacabra.mscz
1) Ctrl + A -> Fill with slashes
Result: crash
or,
2) Selection of the first four measures of top staff (Horn), see the selection: 2 Horn selection.mscz
-> Select three measures or four measures (two measures works) -> Fill with slashes
Result: crash
Now, cut the staff text (the culprit), and do again: select -> Fill with slashes
Result: no crash (result as expected)
By now, cannot reproduce from scratch (xml issue?)
EDIT: maybe there is another related aspect?
Ie, by deleting staff text (all similar elements) in the entire score, I get also a crash after Ctrl + A/ Fill with slashes.
But if, in addition, I delete Tempo text (all similar elements), now, it works.
EDIT (next thinking): tempo text is invisible in the score (and entirely hidden or rather deleted? ) in the selection of four first measures.
In reply to 1- Add a staff (pad synth), by danworks
Yeah, this score definitely seems messed up, although I'm not sure what exactly is wrong. I can say the slash fill command is crashing because it tries to insert a note and that operation is failing and the code isn't prepared for the operation to fail - there is no legitimate reason for it to fail. So I could easily enough avoid the crash by checking for that case and aborting the operation, but that doesn't really solve the root problem. More investigation needed for sure.
In reply to Yeah, this score definitely by Marc Sabatella
I've been exporting several xml fm DP, then open and edit within MuseScore, and this one is he only one that sports this bug. The main differences I can think at, compared to other scores are:
1- many tempo changes at the beginning and at the end, coming directly fm DP's conductor track, which I'd love to get rid of it "with one click" (delete tempo changes), but I just found a way to delete one a time, so I've just set it as invisible items cos I obviously don't want to see it on the score.
2- several meter changes
Text on the score are imported fm DP's conductor track
In reply to I've been exporting several by danworks
Please share this particular xml file. We need this, for further investigation.
In reply to Please share this particular by cadiz1
I don't know if I have it anymore, I can export it again though … this afternoon first thing.
In reply to I don't know if I have it by danworks
Here there is the xml fm DP …
In reply to Here there is the xml fm DP … by danworks
Thanks.
![error.jpg]( "error.jpg")
Ah, fatal error here. I leave the explanation of this to the experts :)
In reply to Thanks. Ah, fatal error here. by cadiz1
Known issue with DP Export, it has "beam start" rather "beam begin". Just ignore that.
In reply to Known issue with DP Export, by Jojo-Schmitz
Ignore, of course (it's what I do).
In reply to Known issue with DP Export, by Jojo-Schmitz
Considering that at the end we can open xml created by DP, maybe the programmers could write a little bit more reassuring warning, rather than:
"fatal error on line xxxx column xx […] your machine is going to explode in ten, nine …" ;-)
In reply to Considering that at the end by danworks
This message doesn't come from MuseScore but the XML validator
In reply to I've been exporting several by danworks
Right-click one → Select → All Similar Elements Del
In reply to many tempo changes at the by jeetee
Great, thanks :)
And let me guess, should it work with anything, like system text for example?
In reply to Great, thanks :) And let me by danworks
Yes, it should work on any type of element. Also check out the Select→More… option which lets you do some very fancy handy stuff
In reply to many tempo changes at the by jeetee
It works beautifully