Clicking on already selelcted note removes accidental
I just started using MS and I'm doing it by importing my Sibelius files via MusicXML.
I noticed that clicking on a note with an accidental twice causes the accidental to disappear. As several people here have said this doesn't happen for them, I'm wondering if it's related to importing a file via MusicXML.
I don't think I'm dragging the note. I'm just making a brief click using mouse keys so there's no way it could be dragged. Also it doesn't change lines or spaces. And it's always a matter of the accidental disappearing, whether that's going up or down in pitch.
Furthermore, the accidental symbol in the palette bar remains highlighted, although the note doesn't show the accidental and the playback is without the accidental.
Seems very much like a bug, but I'd be curious if there's an explanation.
Comments
I just imported a mxl from Sibelius 7.5. I found an accidental and clicked on it. no change no matter how many times I clicked it. My suggestion would be to save the file so that it is an mscz file. then open it and see what happens.
"Furthermore, the accidental symbol in the palette bar remains highlighted, although the note doesn't show the accidental and the playback is without the accidental."
After clicking the note, what pitch does the note report in the Status Bar (bottom left)? If it has changed there as well, then your click has changed the pitch. You say you are not dragging the note, but I think that is the most likely cause.
In reply to "Furthermore, the accidental… by DanielR
I would think that an experienced user would know if they are dragging a note or not. Especially if they are, as in this case, watching for it.
Who knows what is going on. Mxl is problematic as it is.
In reply to "Furthermore, the accidental… by DanielR
I'm using mouse keys so no dragging is possible. The key that produces the click is independent of any key that drags. Furthermore clicking on a flat always removes the flat (an upward motion) and clicking on a sharp always removes the sharp (a downward motion) so that's not consistent with a random drag.
In reply to I'm using mouse keys so no… by Michael Mossey
Please post a page or two of the file.
In reply to Please post a page or two of… by bobjp
I found that saving as mscz fixed the problem. It only happens for me on musicxml files. I actually didn't realize that opening a musicxml file didn't immediately convert to mscz. So I'm going to proceed like it's fixed for now.
In reply to I found that saving as mscz… by Michael Mossey
I have many sib. files that i work on in MU4. You might find that you may need to re-enter some dynamics. MU4 doesn't always render them the same as Sibelius did. Hairpin placement might be off sometimes. Also MuseScore does not read slurs. kind of a bummer.
In reply to I have many sib. files that… by bobjp
MuseScore doesn't read Sibelius files in the first place.
And it does import MusicXML, including slurs...
In reply to MuseScore doesn't read… by Jojo-Schmitz
I should have said MU4 doesn't playback slurs.
In reply to I should have said MU4 doesn… by bobjp
It works for a few instruments, e.g. the flute. In instruments.xml there is a section like this for the flute:
<Articulation>
<velocity>100</velocity>
<gateTime>95</gateTime>
</Articulation>
This means that a note without a slur has a nominal duration of 95%, while notes with a slur have a duration of 100%.
Disadvantage: a whole note at a slow tempo has too long an interruption to the next note and with eighth notes the difference is barely audible.
I have added these lines to a copy of instruments.xml for my horn and linked to it in "Preferences/Score/Instrument List 1".
At least in 3.6.2 this worked with the disadvantage mentioned.