I love the functionality where the note list has several notes on one line so that you get a chord whose number of sounding notes varies as the POLYPHONY parameter. We have to manage this due to the costs that polyphony imposes on the CPU.
I also love the functionality where I have similar chords of even more notes, but chord mode is set to RANDOM NOTE so that the note pulsed is always randomly chosen out of a bin. Regardless of the number of notes in the bin, POLYPHONY limits the number of choosable notes even though only one will ever be chosen. In that case, I have to set POLYPHONY high to ensure that the one note will be chosen from a big bin. If I set POLYPHONY to 1, a RANDOM NOTE chord will only ever have its lowest note played. If I set POLYPHONY high, however, I may accidentally lose track of things during live performance and unintentionally create a situation where a chord of many notes whose envelopes have long holds or delays bogs down the CPU even though I meant for only one of its notes to sound at a time. I also wonder if I might really mess up and cause a huge chord to be pulsed directly, which would also impose a huge, sudden cost on the CPU.
In view of this, I think it would be best for the RANDOM NOTE chord mode to override POLYPHONY and impose a hard limit of 1.
I’ve caused CPU-related misbehavior on my PolyPulse and have even crashed it a couple of times, so I’m getting used to managing the CPU while performing. Even so, adding training wheels that don’t impose any actual performance limitation would be useful for many people and possibly a non-interfering convenience for more experienced performers.