The maxsize for table is not necessary anymore, there is no limit to how big files can be loaded into table now a days. So no need to do that

But yeah, playback can still be an issue.

It could be sooo many things.

I'd suggest including the patch. It's really hard to troubleshoot something you can't see.

@Pi_r

The window is inside clone, so it will process the window on each grain.

But replacing it with a hanning window, yes it should be possible, It would probably require a few steps, but too tired to dive in atm.

Changing number instances on clone dynamically is not possible as far as I know. But you can approach it in a different manner. You can basically just set clone to the maximum number of voices you would like. Lets say you set it for 64 voices. and then you can do this:

This is just an example made with a subpatch, you would of course need to use the actual clone object.

What it does:
If the nr-of-grains parameter is larger than the clone/grain number, then turn on audio for this clone/grain. So if you set the first argument on clone to 64, then you have 64 grains available, but if you only set the nr-of-grains parameter to 48, only the first 48 grains will have audio turned on and only 48 grains will be played and processed. It works fine, I did it in my version, as a workaround, since I was not able to change clone arguments dynamically.

I am pretty sure the need for using maxsize was removed a few versions back. But I might remeber incorrectly.

But since PD is 32 bit there will be some issues with reading back files larger than 190 seconds.

Here is a pretty good explanation why it is like that by Katjaa:

EDIT:
Hmm, for some reason the YT link does not work. Admin, heeeelp!

You can for now go to youtube and search for " Precision matters" and watch the first video, by instantdecomposer.

Hey

I've made a simplified version for VCV's Prototype module that can load PD patches. This is the first version, will probably be updated.

You can get it here:
https://github.com/jaffasplaffa/Pure-data-patches/tree/master/Granular21-VCV-Prototype

@seb-harmonik-ar

I am going to take your word for it, this is a bit beyond my knowledge on the subject

Ahh okay, that makes sense.

I think the jpcex sounds decent for what I tried for now. Haven't used it in a synth yet, only experimented with it.

Actually I used your Shadylib oscs for a Moog clone I was working on at some point and I had some issues with frequency modulation, it kind of "blows up" at times. Especially when feeding the same osc back to itselfs frequency input, like feedback, it blows up. Thought it was something in my patching, but since you mention it here, I think I'll try some other oscs and see if I get a better result. I like the ones form your library, cause it was pretty easy to get the right waveforms I was looking for, like sharktooth Moogish style

Shadylib also has band limited oscs. I think they don't use upsampling, actually.

jpcex external library has band limited PolyBLEP oscs with sync.

Find them via Find Externals.

Using a 2012 Macbook(High Sierra, 10.13.6) with Chrome Version 94.0.4606.71 (Official Build) (x86_64).

There is a small bit of latency when pushing start, audio sounds okay.

Overall pretty cool thing you got there

A record/export audio function would be nice, though

I would also suggest PiSound, combined with the operating system they make specific to use with Pisound and comes with PD preinstalled.

PiSound:
https://blokas.io/pisound/

Patchbox:
https://blokas.io/patchbox-os/

It's very easy to setup. It even comes with simple ways of using it as a stand alone device. You can then use an Ipad or an Android device to change pd patches.

You will have it up and running in a day

Had to give up the first time I tried make a Pi3/pd based synth. But with Patchbox and and PiSound, it took only a few hours

Hey

Just wanted to share an idea I got a while ago for making a preset system using "savestate" and an array.

I wanted to take advantage of "savestate" being able to actually store data to each unique version of an abstraction, without using .txt files. Everything is stored internally in PD.

It uses an array to temporarily hold the parameter data and then use "array get" and "array set" to get and set the data to "savestate", for actual storing and recalling the data when saving and loading a pd patch,

I haven't seen anyone doing something similar, so I thought I'd share it.

It's very simple and it works really well. There is also a copy preset function build in.

It can be found on my Github page:
https://github.com/jaffasplaffa/Pure-data-patches/tree/master/Savestate-Preset-System

There is an description inside the abstraction that shows how to set it up. I think the description should work, if not, then let me know and I will add better description.

Have fun!

Any suggestions for updates are welcome

Best wishes, Jakob Skouborg(Jaffasplaffa)

Looks nice

You asked which GUI elements are missing, I'd suggest a knob

I also started a thread here, asking for help for optimising a Karlsen Ladder filter. I think we ended up with a decent optimised low pass filter. The high pass is not good, it could be a lot better. But I like the sound of the low pass filter.

https://forum.pdpatchrepo.info/topic/13202/looking-for-help-for-optimisation-of-karlsen-24-db-ladder-filter/29

It has oversampling implemented too.

Ahh okay, I don't use Purr, so was not sure.

Don't really know what to say more.

I cleaned it up so it should work with Vanilla and on any OS.

@rubini_t

Hmm, no idea what the problem could be.

I just downloaded it from Github and opened it in PD 0.51.4, on OSX 10.13.6 and it works here.

I do not have a Windows computer, sorry.

Hmmm....... Maybe:
Which version of Pure Data Vanilla are you using? You need the "Clone" object, which I think is only in Vanilla 0.49 and up. If you use the latest version, 0.51.4, you should be good.

I don't think Extended or Purr has "Clone" object, so I am pretty sure it will not work in those two.

@seb-harmonik.ar

Was actually thinking about this yesterday, why it is not enrolled into the Vanilla release.

It has been talked about many times in the Facebook group and also here, I guess

@alexandros

I wish I thought of this when starting out, but have come to this conclusion over time too, learning the hard way.

But now, having literally thousands of patches, using direct references to externals, without the " cyclone/xxx " prefix, it just seems like a humongous task to change it for all patches. But yeah, should probably do it, to make it easier to find which externals packages is actually used. Have already had issues with that when making patches on Osx and using them on Linux systems.

Another example to why it's good to use external prefixes, like " cyclone/xxx ":
If I create a abstraction called " scale " and try to load it, it actually loads a cyclone object called " scale " and not my abstraction.

So using the prefix for externals gives us more freedom for naming abstractions, like " scale " and it won't cross reference to, for example, cyclone external library

Stutter effect can be easily done using a delay. If you have something going into a tabwrite~ and send out of a tabread~ you can simply bypass the input for the tabwrite~ and route the tabread~ back into tabwrite~, like feedback with no gain setting.

Something like this:

I saw you were working on a new version of the delay objects. I think I saw a freeze function in that? That will probably be able to make a nice stutter effect too