bugDenemo - Bugs: bug #30191, Polyphony in a chords vs easier...


bug #30191: Polyphony in a chords vs easier access to voices for only small parts and further voice ideas

Submitted by:  -Deleted Account- <steele>
Submitted on:  Mon 21 Jun 2010 08:29:04 PM UTC  
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  None
Open/Closed:  Closed

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Sat 22 Nov 2014 05:38:05 PM UTC, comment #1:

I think this is broadly all history now.

Richard Shann <rshann>
Project Administrator
Mon 21 Jun 2010 08:29:04 PM UTC, original submission:

This is currently just a reminder for future versions:

I think Denemo should stick with the prinpical of "one vertical position, one duration" which is fine for most music except (which is a very important exception!) Piano music and other instruments like guitar...

It should stick with voices, these are (once they are inserted correctly) much better because of the ways lilypond handles them.

In a typical classical piano piece (maybe a Beethoven Sonata) you have a polyphonic chord maybe every 20 measures which leads to a problem:

Voices are much to fragile currently and too hard to handle for only small parts of the music where polyphony is needed.

Here are some ideas about voices:

0) A quick enhancement would be to create a better indicator than the current "voice 1", "voice 2"... Only one area which indicates which voice through a name or number instead of all with a bold/highlight, like it is now.

1) Drop the "Join voices" and "Split voices" command, which does Staff<->Voice, and exchange with a graphical way.
A voice could be an extra staff all the time, but graphically connected. For example we could use very neutral background color for each "logical" staff, alternating between white and light grey, and all voices of one staff still have the same background color. Also voice-staffs cannot be moved away up and down other then changing the voice order. "Move Staff" always moves the whole complex.

2) Voices still should be mergable, visibly, in Denemo itself, but maybe read-only because its too easy to get confused and create strange things that will destroy your lilypond output.
2b) In addition it should be possible to hide all voices except the main "voice-staff"

3) The Piano-case, also called "Rubberband-Voice": It should be VERY easy to create an additional voice just for one measure to enter a few additional notes. You hit a key/menu-option and an extra empty measure "slides" out under the current one and merges back in once you leave this measure with the cursor. This does not need to push other staffs out of the way, just give the extra-measure a small frame and of course it should be non-transparent.

Smaller things:

4) Caution with directives and keysigs etc! Its very easy to accidently insert such an object into a voice and your score gets broken because the measure is not considered empty anymore.

5) A Keysig inserted in another staff (with "All Staffs" activated) will insert the keysig correctly in all staffs on the same position except into another voice where it shows always at the beginning of the measure, which leads to double keysigs and wrong print and logical errors.

6) Review and check: Voices should listen to the same midi infos, only the main-staff (as in 1) should contain midi-information. Inserting a midi directive anywhere in one of the voices should affect all voice-staffs.

7) Don't forget to check any changes with voices with Select/Copy/Cut/Paste (first of all paste!)

-Deleted Account- <steele>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by rshann (Posted a comment)
  • -email is unavailable- added by steele (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-11-22 rshann StatusPostponed => Fixed
        Open/ClosedOpen => Closed

    Back to the top

    Powered by Savane 3.4