constant delay of 500ms between two bangs ?!


    Jun 19 2006 | 3:10 pm
    Look at the patch below. There's a constant 500ms between the first bang
    and the one out of the counter... How is it possible to have such delay,
    and how does it remain absolutely constant ?
    f.e
    --
    f.e chanfrault | aka | personal computer music
    > >>>>>> http://www.personal-computer-music.com
    > >>>>>> |sublime music for a desperate people|

    • Jun 19 2006 | 3:32 pm
      it seems to me that you have put the quarter note at 120 metronome
      speed,
      that means 2 quarter notes every 1 second. so each of the quarter
      notes comes every 500 mls.
      the timer object measures how much time, after one bang, the
      successive bang will come.
      That's not a delay between the 2 bangs, but the exact timing of the
      tempo object.
      :-)
    • Jun 19 2006 | 3:37 pm
      ups,
      i've realized now that you were sending a bang to the left inlet also.
      well it seems that the problem is much more complicated than what i
      thought... sorry for the wrong answer.
      right now, im near to think that maybe the problem is about "the
      refreshing feature" of the timer object, more than a specific delay
      problem..
      cheers
    • Jun 19 2006 | 3:41 pm
      Am 19.06.2006 um 17:10 schrieb f.e:
      > Look at the patch below. There's a constant 500ms between the first
      > bang and the one out of the counter... How is it possible to have such
      > delay,
      through the power of right-to-left order!
      > and how does it remain absolutely constant ?
      it's tempo's notorious timing accuracy ;)
      (you are confusing timers inputs I think)
      cheers, g.
    • Jun 19 2006 | 3:43 pm
      for example...
      i 've been using a lot timer object in this manner:
      and the timer is always giving the difference in time between two
      successive events, that, in this case, they are the events triggered
      by the tempo object.
      a low explanation is for me that, when the bangs are simoultaneous,
      "timer" consider them as a single bang on the right inlet, always
      refreshing.
      The high explaination is due to other more expert people...
      :-)
    • Jun 19 2006 | 3:45 pm
      hi,
      it's not a delay, it's the interval of the tempo object
      if you want consecutive bangs, use a uzi object.
      in the help file, they say tempo is a "Metronome controllable in beats per minute".
      it also includes a counter starting at 0.
      if you only want your count to go from 1 to 8 instead of 0 to 7, and that's what I beleive
      considering your patch, only add a [+ 1] after the [tempo 120 2 8].
      peace.
      //yac
    • Jun 19 2006 | 4:01 pm
      about the timer object problem,
      this object is one those few for which the right-to-left order rule is not valid.
      its left inlet is cold: it causes no output but starts or restarts the timer.
      and its right is hot: it causes the output of the elapsed time.
      that's all...
      //yac
    • Jun 19 2006 | 4:09 pm
      On 19-Jun-2006, at 17:10, f.e wrote:
      > Look at the patch below. There's a constant 500ms between the first
      > bang and the one out of the counter... How is it possible to have
      > such delay, and how does it remain absolutely constant ?
      That's how timer works. It's not as strictly right-to-left as you may
      have thought. You might want to trace through the following modified
      version of your example.
      -- P.
      -------------- http://www.bek.no/~pcastine/Litter/ -------------
      Peter Castine +--> Litter Power & Litter Bundle for Jitter
      iCE: Sequencing, Recording & |home | chez nous|
      Interface Building for |bei uns | i nostri|
      Max/MSP Extremely cool http://www.castine.de