help using [live.step] with [poly]
I am having trouble getting the [live.step] to work with a [poly], [pack], [route] combination. The sittuation is that when I input notes on the sequencer, only some trigger the intended oscillator, and some are omitted. These omissions seem to be random. Could somebody advize me on how to resolve this? Sorry if my explanation is a bit vague, but I have clearly outlined what I mean in the attached patch.
Using a fast trigger like [metro 50] may produce overlapping of different notes.
[poly] assigns different voices to them, but you have routed only voice 1.
The problem indeed occurs at the point you indicate [route 1 2 3 4] as the only events getting thru from the [poly 4] are those with voice number 1. The quick fix is to connect the other outputs of [route] to the unpack. Without getting into too much detail, you may want to pack the signal part of the patch into a 4 [poly~ ] to get all notes to reproduce with overlap.
Not quite, but that's (kind of) on the right track. Wherever you need to copy same part of a patch - as you have done with the copy of the sound generating patch in your newer example - encapsulating that part of the patch in a poly~ (not to be confused with [poly]!) is the best bet for voice management . Check out MSP tutorial 21 for a better explanation...
I have another question regarding this topic. Using the picture above as an example, sometimes when I start the live.step notes seem to get stuck down at random. Occasionally when I am playing a note just randomly sticks, and produces a never ending tone. This can then be resolved by closing and re-openning the patch.
Could this be a problem to do with the live.step object or the poly~? Can anyone give me advice on how to resolve this issue?