you need four buffers and you need to record audio into it. that's not tricky. the tricky thing here would be overdubbing the same buffer, which may imply some form of summing of your output audio with your input audio, for each of the buffers. even though i would like to point you to a couple things in here: one would be, and is effecively to use a tape delay with 8 and 40 seconds. the other is using a granular delay line. and finally to use granular synthesis with less voices, very large buffers, very large grains, and so.
cheers

@nicnut This might be useful...... it's the old help file from Pd extended and includes at least reversing an array...... all_about_arrays.pd
But an array is indexed...... so can be played backwards anyway by counting down instead of up.
You need the total size of the array (so as to preserve the pitch) and then you can use [phasor~] if you want repeats, or [line~] if you don't, to play parts or all of the array in both directions.
You just need to calculate the range according to the total size of the array.
Here is an old attempt using [phasor~]....... Microsound-granular.pd
It is all just maths...
David.

The use case is a granular synth similar to these ones:

Respectively, there is only one sample, but played simultaneously at different positions and with different speed etc. At the moment I'm using multiple sampler instances each with its own array and read by its own tabread4~ object. The granular synth abstraction is used in several patches and I'd like to declare a subfolder for the sample used in the cloned sampler instances in order keep everything structured and clean. But yes, a great idea to use only one array and pass it to all sampler instances! I'll definitively try it out. Thank you!

Hallo everybody,
I'm a newbie with PD and I need some help.

I downloaded a live granulator patch. I'd like to add some "gate" on the input in order to make the patch work only after a certain mic threshold - because it will be a sort of installation.

I used "moses" and it makes what it should, but don't change the volume of the input (to 0).
I think it's related to the hot/cold inlets, but I didn't find any solution.

Could you please help me?
Thank you

3-7-2-1-granular-live.pd

@nicnut said:

@ddw_music
In the else library or Automatism theres some really good ones, but I haven't found any in Vanilla.

I wish I had found ELSE early on -- if I had, I might have gotten a much better impression. (It even has a copy of my favorite SC resonator, Ringz.ar <--> [resonant~].)

For fun, here's a 1-minute clip from my last show, a duo techno improvisation with my friend Neil on Digitakt (all drums are his) and myself live-coding SC (with the help of a custom dialect for patterns). I'm especially happy with the granular piano washes (the source notes come from VSTPlugin, which you also have in Pd as vstplugin~; granular processing + delays + reverb are all SC). 23-0324-hoodoo-jam-shorter-clip.mp3

@60hz

Don't forget to try https://ceammc.github.io/pd-help/,

Oh, I see, a complete alternate distribution. I had gotten discouraged when I tried to add the CEAMMC externals and found that (at that time) they didn't release them for Linux... but the alternate Pd does have a Linux version.

However, I guess I would have to build it myself, because I've adjusted some things so that the UI drives me slightly less batty. In particular, I loathe the way that dragging an object to reposition it enters edit mode -- but MSP feels that it's more important to be able to duplicate-move-type. Fine, whatever, he's wrong about that(+) but at least when I build from source I can fix it so that it works properly.

(+) Should be a user preference, but it isn't... if that weird UI decision is going to be imposed on everyone by force, then I reserve the right to be grumpy about it.

Anyway, the issue is not entirely about feature availability. It's also about workflow.

hjh

@KMETE I throw this at you until something better is posted....... Microsound-granular.pd .... which will happen.
The "smooth" anti-click part would be better done with a Hann window than the "duck" that is implemented and I am sure it can be improved/simplified.
It should be easy to understand and tailor to your requirements.
If you actually want granular synthesis there are good links here..... http://gerard.paresys.free.fr/Theme/Theme5.html
David.

@raynovich said:

And yeah, I kind of want to know more how it works. . .

Hm, well, let me propose an analogy. Analog synthesis is fairly standard: bandlimited waveforms, there are x number of ways to generate those, y number of filter implementations etc. But many of the oscillators and filters in, say, VCV Rack have a distinctive sound, because of the specific analog-emulation techniques and nonlinearities used per module. You can understand analog synthesis but that isn't enough to emulate a specific Rack module in Pd.

Re: Shuffling, I finally found this one sentence description: "Shuffling takes random sample fragments of variable dimensions from the last three seconds of the incoming sound and modulates its playback density and pitch" -- that's a granular delay.

A granular delay is fairly straightforward to implement in Pd: [delwrite~] is the grain source. Each grain is generated from [delread4~] where you can randomly choose the delay time, or sweep the delay time linearly to change the pitch. That will take care of "random sample fragments," "last three seconds," and "modulates... pitch" (you modulates playback density by controlling the rate at which grains are produced vs the duration of each grain -- normally I set an overlap parameter and grains-per-second, so that grain dur = overlap / grain_freq).

"... of variable dimensions" doesn't provide any useful technical detail.

But what isn't covered in the overview description of a granular delay is the precise connection between the Shuffling plug-in parameters and the audio processing. Since GRM Tools are closed-source, you would have to get hold of the plug-in and do a lot of tests (but if you have the plug-in, then just [vstplugin~] and done), or guess and you would end up with an effect that's somewhat like Shuffling, but maybe not exactly what the composer specified.

I'll send a grain-delay template a bit later, hang on.

hjh

Here's a fairly standard granular patch system made in "vanilla" Pd. Enjoy!
https://github.com/yannseznec/ys.granular

and here's a video tutorial that explains the patch:

@granular deken can be searched.

Edit: just remembered that searching for objects got added too deken in pd itself, just menu over to Help->Find Externals and type in the name of the object you are looking for and it will return a list of libraries which contain an object with that name for you to easily install.

@granular Try this vanilla replacement....... delta.zip
The external was, and probably still is in the maxlib library.
David.