• tim167

    hi,
    I know there's probably already a bunch of these out there,
    but here's my take on grains...
    I'm seeding the randoms by sampling the adc~, so the dsp should be on before you load the patch. There must be better ways to seed randoms. Any suggestions ?
    gr,
    Tim

    http://www.pdpatchrepo.info/hurleur/grains.zip

    posted in patch~ read more
  • tim167

    hi arif,
    thanks :)
    the input sits inside the 'loader' subpatch, by default it takes inputs 1 and 2
    (its just [adc~] without any arguments)

    posted in patch~ read more
  • tim167

    new version with some more modifications:
    -random seeding with $0, as suggested by hardoff
    -'grab' and 'autograb' for live input grabbing
    also, the graingen subpatch is now less well hidden ;)

    gr
    Tim

    http://www.pdpatchrepo.info/hurleur/GRAINS2.zip

    posted in patch~ read more
  • tim167

    hello,
    thanks all for your replies and tweaks !
    hardoff, I wonder if that can work. I tried it, but changing [/ 127] to [/ $0] will also affect what comes in from the sliders obviously...
    maybe it can be solved by setting the slider to 0-1 range and adding

    • right before it goes into the random object...something like that?
      also, doesn't $0 always start to count from the same value when pd is loaded ?
      i tested this with [loadbang] -- [f $0] -- [print] and i always get 1002 when loading that right after opening pd..

    posted in patch~ read more
  • tim167

    Hi, jumping in with my first post on this forum :)

    You could use [keyname].
    At its left outlet, it outputs a 1 for key-down and a 0 for key-up.
    repeated keystrokes while holding down a key will all have a 1 in the left outlet, so you can block those (spigot) on these two conditions:
    -has the same key name as the previous
    -no 0 for this key has occured yet (you havent released and repressed the key yet)
    That way you _can_ enter the same key twice, but only if you release it first.
    I haven't made a patch to show this yet, but that's the reasoning I would base it on...

    Tim

    posted in technical issues read more
Internal error.

Oops! Looks like something went wrong!