strange behavior


    Apr 22 2006 | 8:42 pm
    Hi all,
    I'm at a total loss. I'm working on a patch, which seems to function
    fine if I trigger an event manually (either by clicking, or using
    [key] to trigger) but if i try to automate it with [trigger] or
    [metro] or even sending a midi event, it behaves completely
    differently. I know i'm doing something really stupid, but I can't
    for the life of me figure out what! I isolated the problem in the
    patch below, it looks like it's doing the same thing if you click or
    hit tab or use the metro, but if the metro sends a bang, it behaves
    complely differently. is anyone able to reproduce this?
    thanks so much!
    best,
    erik
    --
    www.hecanjog.com / www.cedarav.com / www.luvsound.org
    he can jog split ep with jahbitat forthcoming on norsordo:
    Switches and Intricate Maximals comps out now on Audiobulb Records

    • Apr 22 2006 | 10:34 pm
      Hi Erik
      You have two solutions first is simply to put a defer object between the '9' and the 'select 9'
      And the second solution is even more simple - turn overdrive off.
      I struggled with this same thing so i know your pain! The help file for defer helps to explain why this works:
      "When Overdrive mode is enabled, objects such as metro operate in a high-priority scheduler thread. If you want to execute a time-consuming task, such as using an Uzi for repetitive operations or the bang message to a table object, you can defer the output to the lower priority main thread by passing a message through the defer object."
      Hope that helped,
      john.
    • Apr 23 2006 | 1:52 am
      Brilliant! Thanks John! That's really good to know, I felt a little
      crazy for a while.
      Best,
      Erik
      --
      www.hecanjog.com / www.cedarav.com / www.luvsound.org
      he can jog split ep with jahbitat forthcoming on norsordo:
      Switches and Intricate Maximals comps out now on Audiobulb Records
    • Apr 30 2006 | 2:41 pm
      erik schoster wrote:
      > I isolated the problem in the patch below, it looks like it's doing
      > the same thing if you click or hit tab or use the metro, but if the
      > metro sends a bang, it behaves complely differently. is anyone able
      > to reproduce this?
      No, the metro and the bang/tab behave the same. But it seams you want to
      behave it differently, as the comment states "it should clear the buffer."
      Of course it will fill the buffer with the choosen selection and it does
      so, no idea why you would expect it to clear the buffer, as the bangs
      also don't clear it...
      Not quite clear what the metro is aimed for...
      Stefan
      --
      [][] [][][] [][] [][][]
      [][][][][][][][][][][][][][][]
      Stefan Tiedje
      Klanggestalter
      Electronic Composition
      &
      Improvisation
      /~~~~~
      \ /|() ()|
      ))))) )| | |( \
      /// _/)/ )))))
      ___/ ///
      -------------------------x----
      --_____-----------|-----------
      --(_|_ ----|-----|-----()----
      -- _|_)----|-----()-----------
      ----------()------------x-----
      14, Av. Pr. Franklin Roosevelt,
      94320 Thiais, France
      Phone at CCMIX +33-1-57 42 91 09