• weightless

    @kevinschlei I don't think there is but Purr Data has those and is arguably nicer.
    https://github.com/agraef/purr-data/releases

    posted in extra~ read more
  • weightless

    @t3zeu5 Here are two abstractions I made some time ago for that purpose (plus other useful abstractions used in the help files). They suited my needs but can be easily adapted to yours I think. Take a look at f2scale-help.pd and subset-help.pd. Hope this helps.
    quantize-abs.zip

    posted in technical issues read more
  • weightless

    @rpgidem check out [bonk~].

    posted in technical issues read more
  • weightless

    @Fauveboy this is my version of the vanilla pipelist using [text]:
    vpipelist.zip

    posted in technical issues read more
  • weightless

    @Fauveboy
    for [prepend], you can use [list prepend] followed by [list trim].
    for [unpackOSC], I think [oscparse] should do the same.
    for [pipelist], this is trickier but I have a feeling it could be done with a combination of [text] objects. You can have a look at [list-fifo] as well (a vanilla abstraction from the list-abs library), but I don't think it does the same thing as [pipelist].

    posted in technical issues read more
  • weightless

    @dom1817 I don't think that is a built-in feature because if you send a bang to a toggle, it changes its state. But if you want to keep your patch tidy, you could turn my patch into an abstraction and use that instead of a toggle.
    toggle2.zip
    look at the help file.

    posted in technical issues read more
  • weightless

    @ouzala Hi and welcome to Pd.
    If those processes are of unknown (or variable) time lengths, I guess you must to derive the end trigger directly from each event in order to set off the next one. This depends on how you are playing those loops. For example, [tabplay~] and [readsf~] already have an outlet which gives a bang whenever you reach the end of the playback. If you use [tabread~] it's different.
    It'd be easier for us to help you more specifically if you could post your patch.

    posted in technical issues read more
  • weightless

    @bocanegra I guess I misunderstood your post then, my bad. I didn't mean to show off my favourites but rather point you to some nice work that has already been done in Pd (especially the Dattoro one) in case you didn't know about it, for you to study and take some inspiration from.

    Reverb design goes a bit over my head to be honest, even though I tried to study a few algorithms, so perhaps somebody else will join in for the discussion.

    Your jVerb sounds very nice to me, thank you very much for sharing it.

    posted in patch~ read more
  • weightless

    @orangepickle Hi, this converts midi notes to delay time for the karplus strong algorithm:
    Screen Shot 2018-09-21 at 08.51.56.png
    for midi notes higher than 76 you need to put the delay write and read in a subpatch with [block~ 1 1 1] because the delay time is too short.

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!