poly~ help_please


    Feb 21 2006 | 2:10 am
    If anyone has the time could you please check out the following poly~ patch see if there are any glaring problems. I modeled it after the clickless examples and I'm still getting click-like garbage all over the patch. Every 10 seconds or so it sounds like a click or the gets interupted by something. Any help would be much appreciated,
    THanks
    Casey
    max v2;

    • Feb 21 2006 | 4:16 pm
      i've just looked at your patch and it seems fine...i didn't bother getting it inside poly~ and building a testpatch around it.... but i would like to see the 'master patch' in which this poly is used..... the error can be in this patch as well.
      If you want me to test out the hole thing....u can send me the patches by mail : geek74@gmail.com
    • Feb 21 2006 | 7:24 pm
      casey Farina wrote:
      > If anyone has the time could you please check out the following poly~
      > patch see if there are any glaring problems. I modeled it after the
      > clickless examples and I'm still getting click-like garbage all over
      > the patch. Every 10 seconds or so it sounds like a click or the gets
      > interupted by something. Any help would be much appreciated, THanks
      Points to look into: the gate~ 8 which might be switched at the wrong
      time, you could replace it with matrix~.
      In general it looks like there is potential to simplify the whole
      structure. You send all parameters of a note in one single list, but
      some parameters are redundant. For example the buffer size is not
      necessary to send, as if you have a buffer~ you could always get the
      size within the poly~.
      What I do, usually with all this kind of information, I fill a coll and
      refer to that coll within the poly~, then you don't have to carry that
      long list around every time.
      Also attack decay sustain release would only be usefull to carry with
      the note information if it changes with every note. But as you just
      carry adsr, I suspect you think of it in a traditional way as sound
      parameter which not necessarily would change with every note.
      If you want to carry enevlope information, you could send multisegment
      lists to an extra input, which would not restrict you to use adsr type
      envelopes.
      Stefan
      --
      [][] [][][] [][] [][][]
      [][][][][][][][][][][][][][][]
      Stefan Tiedje
      Klanggestalter
      Electronic Composition
      &
      Improvisation
      /~~~~~
      \ /|() ()|
      ))))) )| | |( \
      /// _/)/ )))))
      ___/ ///
      -------------------------x----
      --_____-----------|-----------
      --(_|_ ----|-----|-----()----
      -- _|_)----|-----()-----------
      ----------()------------x-----
      14, Av. Pr. Franklin Roosevelt,
      94320 Thiais, France
      Phone at CCMIX +33-1-49 77 51 72
    • Feb 22 2006 | 11:29 am
      great idea having the coll object inside poly~, haven't thought of it...
    • Feb 22 2006 | 2:08 pm
      Thanks for the tips everyone, I really appreciate it. I'm a little confused to how one would impliment the coll in the poly technique. Any examples?
    • Feb 22 2006 | 11:20 pm
      something like this...