@EsGeh: I just finished to multithread my fork ; beta-testers are welcomed!
< https://forum.pdpatchrepo.info/topic/11738/spaghettis-yet-another-fork-of-pure-data >
i/o-errors in pd
@EsGeh: I just finished to multithread my fork ; beta-testers are welcomed!
< https://forum.pdpatchrepo.info/topic/11738/spaghettis-yet-another-fork-of-pure-data >
@Nicolas-Danet Hey Nicolas, that's very cool! I will test my patches with your fork for sure, let's see how it handles my array craziness...
@jancsika said:
Sorry, I'm having trouble making sense of what you've written:
Sndfiler crashes my pure data in every situation I've tried, so I can't use it.
then this:
If I put the array in another patch and I don't open the graphics of it, the
[resize(
message doesn't affect to the dsp performance, so now I can record arrays and resize them at the same time whatever the duration of the recording is.Which is true?
Both are true. If I use sndfiler the patch crashes directly. Then, without using sndfiler, if I put the array in another patch or embedded window outside the main patch, it seems to help with the dsp performance, not perfect but much better. I supose that opening a new pd window helps a little with multithreading.
Oops! Looks like something went wrong!