metro issue when when main transport is looping

    Mar 20 2013 | 11:23 pm
    When I set the Live main transport to a 4 bar loop, and use metro as follows:
    metro 1n @quantize 1920 @autostart 1 @autostarttime 0
    it sends out a double bang every time the transport loops.
    Is this by design? Is there a way to avoid it? Alternatively, is there a more reliable way than metro to quantize m4l events, like having them respect Live's global quantize setting somehow?
    Sorry for the noob questions. I really am trying to sort these things out for myself, but if this is a bug, then I need to know.

    • Mar 21 2013 | 10:23 am
      It seems that autostart/autostarttime is not designed for working with loops. But you can replace it with the 'active' attribute like this
      [metro 1n @quantize 1n @active 1]
    • Mar 21 2013 | 3:52 pm
      Thanks, broc. That does the trick. I would not have found that on my own. I did read thorough the entire metro reference, which has this to say about the active attribute:
      "Turns the metro on and off"
      Nor does it mention anywhere that autostart is not intended for use when the main transport is looping... If one is using Live for, say, "Live" instrumental recording/looping, is it that unusual to loop the main transport at a phrase length in session mode? I would have thought this was a common practice & this would have come up before. No other mention of this issue that I could find, and I looked...
      Hope this thread saves someone else some frustration.
      Thanks again for your quick response/help. I really appreciate it.