Opened 13 years ago

Closed 12 years ago

#223 closed Bug Report (invalid)

Individual voice control values are nuked on changing polyphony

Reported by: David Robillard Owned by:
Priority: major Component: Ingen
Keywords: Cc:

Description

Setting a different control value for individual ports (e.g. make a chord with an oscillator by hand in the control dialog) then changing the polyphony count of the patch nukes individual control settings.

Semantically: port 'value' must store p values, not just 1.

Change History (2)

comment:1 Changed 13 years ago by David Robillard

Priority: minormajor

May affect ontology: priority = major

comment:2 Changed 12 years ago by David Robillard

Resolution: invalid
Status: newclosed

Removed ability to set voice specific controls (and if this functionality is needed it should now happen via a special dict value with all voice controls in it which would serialise directly for both file format and protocol)

Note: See TracTickets for help on using tickets.