Unrepeatable Crashes
I've been messing around for a while trying to move the beam connecting 2 quavers in a voice as it is running through the head of a crotchet in another voice. I'm having trouble getting it how I want it so I've had several tries. But every time Musescore crashes at some stage in the process.
What happens is that I successfully alter the angle of the beam by using the handles and successfully move it a few times but at some point - and not always at the same point - Musescore crashes. Unfortunately I can't reproduce it reliably, so I can't raise a bug report. All I can say with any accuracy is that if I mess about with the beam ling enough it will eventually crash.
Is there any point in raising issues such as this - I'm new to the software so I'm assuming I'll come across similar situations as I delve deeper?
Comments
A screencast could help :)
In reply to A screencast could help :) by chen lung
Do you mean a screen shot? Of what? Just the bar affected? If so I've attached one (at least I think I have this is the 1st time I've tried this).
Obviously I can't provide a screenshot of the event causing the crash as I never know when it's going to happen
In reply to Do you mean a screen shot? Of by fatwarry
Which version of MuseScore are you using? On which operating system?
Can you share the file you are working on? or the part of it that make it crash ?
Read [[nodetitle:How to report bug or ask for support]]
In reply to Which version of MuseScore by [DELETED] 5
Thanks lasconic. Sorry but I'm a bit confused. You seem to be saying I should raise a bug report but it says in "How To Report A Bug" :
"If you are reporting a bug, please describe the precise steps that lead to the problem (where do you click, what keys do you press, what do you see, etc.). If you are not able to reproduce the problem with the steps, it is probably not worth reporting it as the developers will not be able to reproduce it (and solve) either."
As I can't describe the precise steps etc I wasn't sure whether to report it or not (that's basically the question I was asking in my initial post)
I don't think I can share the file as I'm transcribing a copyrighted arrangement. However, in my previous post I did attach a jpeg of the offending section.
Just for the record I'm using 0.9.6.3 running under Win XP Home SP3
http://www.screencast-o-matic.com
:)
In reply to http://www.screencast-o-matic by chen lung
Wow! what a great service!
Anyway, Sod's law dictated that I couldn't recreate the crash while trying to record it on Screencast. I can only guess that it must have been something I did earlier in the session that created the conditions for the crash. When it happened on subsequent occasions yesterday I was using the option to restore the previous session when I restarted Musescore. Today, I've been opening the score from file.
Incidentally, I've got round my problem by "un-beaming" the notes where the beam is crossing a notehead in another voice. It's a bit laborious having to select the note and then go to "No Beam" in the palette - I couldn't find a way of selecting and processing several at a time. Is there one?