Intermittent poly~ performance

    Feb 07 2013 | 4:34 pm
    Been working on this patch and have posted about it in other posts. I am now encountering a new issue so I thought it deserves a new thread. I am getting inconsistent and intermittent performance with this patch. Not sure why it only works sometimes and not all the time. Also, it seems that when I am on one event (that's my internal cue) it will be o.k., but then it'll stop altogether on the next event (cue). Sometimes it won't work at all but other it will be just fine.
    Top Patch:
    poly~ patch names cycle synth(simpleFM):

    • Feb 12 2013 | 3:17 pm
      Still haven't solved this issue. I thought it might be related to the sel objects located within the synthdata sub-patch but not sure that is it. I still get intermittent performance. Sometimes the synth will stop playing altogether even when it you can see frequencies being sent into it. I am sure there is something I am missing.
    • Feb 12 2013 | 3:21 pm
      Here is the top-level patch if anyone is interested.
    • Feb 13 2013 | 12:44 pm
    • Feb 13 2013 | 5:04 pm
      Someone suggested i be a bit more clear in my problem to see if that will help in getting a response.
      What I am attempting to do is have a collection of frequencies (contained in a coll) sent out in random order to an FM synth. The order and groupings are controlled by the patcher coll counter.
      The data being sent to the synths is in the patcher synth data. This data is for frequencies, modulation index, envelopes, and durations.
      What I want to have happen is that I can trigger frequencies, envelopes, etc. via the metro object contained in the poly-synth patch. The sounds are to be continuous and will progress through with various iterations. The problem is that the audio stops at certain points. This should not be the case but it is. Watching my number~ it can bee seen that there is no signal coming through even if there is still a frequency being trigger and sent to the poly~ through the note$1 message. So there is something going on I assume with my patcher "envelopes" that is causing this confusion.
      Hope that helps n what i am trying to achieve.
    • Feb 13 2013 | 6:36 pm
      The problem lies in your architecture for the poly~ patch, I think. You're having the amplitude envelope generated globally, yet the unmuting and busy state on is happening locally. Your envelopes don't have a sustain state, so they can actually be much simpler in operation.
      The following structure should take care of things. It's find to use send and receive for single values, like harmonicity ratio, but don't use them to trigger envelopes as this will cause all manner of confusion. (in this example, they're stored with the zl reg object for later triggering)
      Also, I recommend providing default values for all your oscillators, line~, sig~ in your poly~ patch. (It makes debugging easier)
    • Feb 13 2013 | 7:58 pm
      Peter, you're brilliant. That did it. Here is how I did it: