Clef change doesn't relocate notes in new score
1. Create score.
2. Input Middle C.
3. Drag bass clef onto first bar.
Result: The note position does not relocate - with the new clef, it appears as E (almost two octaves below Middle C).
Discussion: Only applies to scores created in the nightly build.
Using MuseScore 2.0 Nightly Build (5326) - Mac 10.6.8.
Comments
Please see this discussion in Technology Preview
http://musescore.org/en/node/14938
It looks as though this has been fixed.
Leastways clefs seem to be working properly in the latest version I have tested - R5471
If no-one responds before the end of the week I will mark this as fixed
I don't think it's fixed.
1. Create piano score.
2. Enable 'Note Entry'.
3. Input Middle C.
4. Disable 'Note Entry'.
5. Drag any bass clef onto the first bar of the treble stave.
Result: The note does not relocate.
Using MuseScore 2.0 Nightly Build (5489) - Mac 10.7.3.
If you save the file then reload it MuseScore crashes on reload
But then when you reboot it the note appears in the correct position.
However it is still not behaving as it should.
R5471
#11620: [Trunk] Reload causes crash
What I would love to know is:-
Why it works properly on a loaded score.
But not on a MIDI file import or freshly created score!
For some reason this seems to have shown up again recently? I would swear I had changed initial clefs successfully last week (in fact, elsewhere, I commented on a nice and hopefully intended behavior I saw where you could have different clefs for concert pitch and transposed), but this week, initial clef changes don't work again. The original problem description above still applies in windows nightly build 9-15.
Yes, I think it still applies.
Using MuseScore 2.0 Nightly Build (ec12bc5) - Mac 10.7.4.
should be fixed in latest versions
Automatically closed -- issue fixed for 2 weeks with no activity.