swieser1

When using a kslider set to polyphonic mode, I would expect a bang in the left inlet would report all of the currently held down notes. However, it only reports the most recently changed note (even if it is a noteoff). Successive bangs will continue to report only the most recently changed note.

The reference file for kslider says that a bang to the left inlet should send out "the pitch and velocity values currently stored in kslider". To me, that means all of them.

Is this the expected behavior of kslider? If so, I think the documentation should be amended to say that a bang to the left inlet of a kslider in polyphonic mode will output the most recently changed value.

When using a kslider set to polyphonic mode, I would expect a bang in the left inlet would report all of the currently held down notes.  However, it only reports the most recently changed note (even if it is a noteoff).  Successive bangs will continue to report only the most recently changed note. 

The reference file for kslider says that a bang to the left inlet should send out "the pitch and velocity values currently stored in kslider".  To me, that means all of them.

Is this the expected behavior of kslider?  If so, I think the documentation should be amended to say that a bang to the left inlet of a kslider in polyphonic mode will output the most recently changed value.


polyphonic-kslider-bug

Technically the [kslider] object doesn't store anything, it just displays graphically the data that passes through it and a bang makes it output the last piece of information it remembers, which will be a single event. If you want an object that follows note-ons and note-offs have a look at [borax] or maybe write a small patch to store which notes are currently being played using [coll].

> Is this the expected behavior of kslider?

Scott schrieb:
> Is this the expected behavior of kslider?

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


A workaround is not a problem, the [bag] object was practically made for this exact situation. I'm just pointing out that the help file and reference file are misleading in this case.

A workaround is not a problem, the [bag] object was practically made for this exact situation.  I'm just pointing out that the help file and reference file are misleading in this case.


polyphonic kslider bug?