How to get the groove~ loop argument to generate a bang

    Dec 02 2010 | 10:02 pm
    Hey everyone I want the loop argument for groove to output a bang when it has finished its first cycle to trigger an amplitude envelope using function. Is this possible? or will I have to use a metro to a counter object to out put the bang message?

    • Dec 02 2010 | 10:25 pm
      Are you trying to create a grain window that relies on loop size? If so, I don't think [function] is the way to go...
      (Stupid question but, you know about the loop sync output from [groove~]?)
    • Dec 02 2010 | 10:38 pm
      noob thats exactly what im trying to create ha. I totally forgot about using loop sync ive been trying to drive a bang using a counter object which got its maximum count from the info~ object.
    • Dec 02 2010 | 10:40 pm
      I realize [function] will let you draw your own grain-window:
      [trapezoid], driven with the sync signal from [groove~] gives you minimal control over grain-window shape,
      but look at
      and you can draw grains all day!
      hih Brendan
    • Dec 02 2010 | 10:55 pm
      awesome thank you so much for that I really need to understand trapezoid I've looked into it but haven't used it before with those arguments you are using at the moment what type of waveform are they producing? (Sorry for sounding daft)
    • Dec 02 2010 | 11:05 pm
      Just have a quick glance at the helpfile for [trapezoid~]: it's a trapezoidal wavetable, and the 2 arguments (usually between 0. and 1.) dictate the phase position of the up and down ramps, effectively allowing you to slope those two ramps; you can also set the amplitude using the message [hi $1].
      Look at [curve~] too
      Check out youtube (ronnie9253) for my groove-grain tutorials; a bit out-dated but might be useful
    • Dec 03 2010 | 4:48 am
      stay in the signal domain if you can, so no bangs or counters. should be able to do that no problem with trapezoid~, as well as the
      delta~ >~ 0.5 edge~
      kind of analysis on the sync outlet of groove~.
      It would be nice to have a built-in way to grab this all-important information without these three chained-together objects, but hey, they work great.
    • Dec 03 2010 | 7:21 am
      ya, seejayjames is right, better to stay in signal domain if you can(also relieves scheduler...)
      in case it helps, for this: "....without these three chained-together objects, but hey, they work great."
      while this is a time-proven technique for reading start/end of any kind of phasor-like signal, unlike phasor~, groove~'s sync outlet does actually go to 1., so you can whittle those three down to just 2, [==~ 1.] and [edge~] in case it helps:
      for the original question, Brendan's answers are also great! yay trapezoid!