No hooks on the arpeggio bracket in this score + other problems
1. Load Attached Score (originated as a demo score)
2. Navigate to bar 10
3. Drag the straight line arpeggio bracket to the chord and adjust length.
Expected behaviour the line should have hooks at each end.
Actual behaviour - the hooks are missing.
I suspect there may be something funny about this score as MuseScore crashes whenever you try to reload it.
Windows XP Pro SP3/MuseScore 2.0 Ra419129
Attachment | Size |
---|---|
bwv565.mscz | 38.78 KB |
Comments
Maybe the crash is not to do with the score - I've just tried to reload another of my 2.0 scores and it crashed again - so perhaps there is another issue here?
For OS etc see original post
#11620: [Trunk] Reload causes crash
Thought I should also mention.
I was having trouble with clef changes "taking" whilst editing this score. Sometimes the clef would appear but the notes wouldn't change, sometimes an un-necessary courtesy clef would be inserted. Usually undo would not solve the problem.
Unfortunately this problems didn't occur with a consistent enough sequence for me to file a specific bug report.
It may be something to do with the score which was originally generated with an early version of 2.0
Sorry not to be more specific :(
OS and MuseScore version as in original post.
There's another separate problem - I can't see any elements of the score.
Using MuseScore 2.0 Nightly Build (cdfaf84) - Mac 10.7.4.
It's blank???
Yes.
It'll play, but there's nothing there.
Weird!
So Chen, does this later version of the score I uploaded yesterday behave in the same way??
http://musescore.org/en/node/16500#comment-62649
The file attached to this report displays OK on the latest Windows Nightly Build - R53f6f8d
That one is fine.
Using MuseScore 2.0 Nightly Build (966e628) - Mac 10.7.4.
Same problem for the same versions under Ubuntu 11.04
http://prereleases.musescore.org/linux/nightly/mscore-2012-07-18-10-46-…
works, the previous didn,t
reinstating title...
The score here is made with an old development version, so it's expected to have funny behavior with it. I close this issue, reopen or open another one if you have more information.