The behaviour of the software in accidental application is against standard music notation. The treatment of accidentals is a particular instance of some of the behaviour which concerns me and for those who are learning music, it would cause more confusion than is necessary I would like to recommend this software to others as a replacement for other music notation software but I'm still of the opinion, that while massive progress has been made, there are significant issues which prevent it being used more widely, especially for those who are learning music. I've followed the project from around version 0.9, and stuck with it through some extremely quirky and buggy behaviour. I think MuseScore is a fantastic project! I find it extremely capable and useful at ironing out problems in understanding scores and pieces of music. In the meantime, I have bumped the issue quoted above. sharpened or flattened or 'naturalized' the accident is not written as implicit), mostly like MuseScore currently does for accidentals in the key signature.ī) While editing existing notes, the current MuseScore behaviour should be kept: only the note(s) on which the user acts should be changed, without carrying the change on other following notes of the same pitch.Īs this is a rather recurring topic, probably is something to push somewhat higher on the priority scale.
In all occasions, most of the complexities were cleared by distinguishing between "entering new notes" and "editing already entered notes" and a general consensus was reached along this guide lines:Ī) While entering new notes, the current MuseScore behaviour is sub-optimal: it should default to a more immediate adherence to current "spelling conventions" in particular, entering a note which already occurs in the same measure with an accidental should by default produce a note of the same pitch (i.e. This topic reappears periodically there are several threads in the forums and at least one issue
0 kommentar(er)
