Signature
-
seb-harmonik.ar
like this? I don't think you'll be able to do variable # of outlets without dynamic patching (if you know of any abstractions that do so I would be interested)
round-robin.zip -
seb-harmonik.ar
yes but I think you have to use an antialiasing/interpolation filter of some kind afterwards
sampling causes a (positive and negative) spectrum to repeat at multiples of the sample rate, so whenever you sample you have to put a lowpass on it both before (to eliminate the errors in the actual capture, which is irrelevant here because it's a sinewave lower than nyquist) and after (to eliminate the repeated images created by the sampling).
normally this second filter would be the job of your soundcard/dac, but in your case you are outputting at the higher sample rate
so here I think you need an antialiasing lowpass for the nyquist of your downsampled rate (1/8th of your output rate) after the outlet
edit: you could also try just using[outlet~ lin]
instead if you want something easy but imperfect (or[outlet~ pad]
if you want it to be even more aliased). sample-and-hold and linear interpolation are actually types of crude lowpass (convolving w/ a rectangular or triangular window) -
seb-harmonik.ar
expected, use
[max~ 0]
in the signal (or the writer) to clip it out.
(or alternatively make the table 1/2 as long/only write 1/2) -
seb-harmonik.ar
cosine and sinesum correspond to the 'real' and 'imaginary' parts of the 'real' fourier series respectively. since there is no imaginary part for frequency 0 (dc) I guess it's skipped for sinesum. see the help file of
[rfft~]
for some more info. (beyond that you'd have to start learning about dsp) -
seb-harmonik.ar
@atux send the note messages directly to a
[pipe f f 1000]
instead of a[delay]
and[timer]
-
seb-harmonik.ar
I think in this case you might not even need multiple instances (for instance you could use an array to look up the values for
[expr]
using the index from @oid)
or at least split it into multiple instances later down the processing -
seb-harmonik.ar
you could try to go through the pd source code and see how it does the drawing (and only draw those corresponding points)
-
seb-harmonik.ar
@raynovich are you using gui externals? maybe iemgui or moonlib objects? there were some incompatibilities introduced in 0.53 that caused some of those to crash
at any rate I would try updating your externals -
seb-harmonik.ar
@raynovich yeah on MacOs there should be a crash log in ~/Library/Logs iirc. Easiest might be to open your Console app (in /Applications/Utilities) and find the log from there
-
seb-harmonik.ar
@raynovich is there a stack trace/crash log? what system is it? what is the minimum patch possible that produces the crash?
these are all good infos to get whenever you look for the culprit of a crash