I'm creating this bug for general ideas and
discussion about ways to make the notation editor
more reliable, predictable and comprehensible.
I'm going to leave it unassigned and unprioritised
for the moment.
This is partly in response to Michael's comment in
another bug report about how the notation editor
has stopped evolving during the last couple of
years. We've reached a point where most of the
obvious bug and feature work available is stuff
that is easy to describe and explain the need for,
but very hard to conceive of even the first steps
towards actually achieving in the GUI and code,
which is why even the most basic features (e.g.
piano staffs, alternative repeats) keep getting
Much of the difficulty arises from Rosegarden's
form as a combined sequencer/notation editor. I
would like to find ways to overcome the difficulties
that arise from this form, rather than boringly
accepting that some things just can't be done or
will have to be excessively complicated to use.
I'll try to start this off shortly (if nobody else nips in
first) with some thoughts about polyphony, part
writing, and rests.