even oversampling just doubles real block size
i want to build a feedback loop imitating in analogue circuits so i need low block sizes. 1 would be best. 64 would have resonant frequencies in the audible range.
should i report this as a bug?
Switch~ can't reduce block size
even oversampling just doubles real block size
i want to build a feedback loop imitating in analogue circuits so i need low block sizes. 1 would be best. 64 would have resonant frequencies in the audible range.
should i report this as a bug?
pd redefining mathematics |expr fact(0)|==0
did you check the 'execution order' help patch? if you don't put your delread~ and delwrite~ in subpatches to force the execution order, then there is a good chance you can't go lower than 1 block of delay.
i already know of g04/05
05 is only useful if you don't have loops
04 tells you what to do if you want to make a loop but block size really is 64 and not 1 in the subpatch
pd redefining mathematics |expr fact(0)|==0
can at least someone confirm this behaviour?
btw 0.41.4-extended/windows here
pd redefining mathematics |expr fact(0)|==0
Mmm...I think that abstraction I gave you might actually be shit. It doesn't seem to work with block sizes below 64. Might be a bug with [bang~].
Take a look again at G.04. Get rid of the random thing going into the right inlet of [pd delay-writer] and replace it with this:
[0\
|
[/ 44.1]
|
Don't connect it to the [metro], of course. This will allow you to change the delay length in samples. You can clearly hear the difference when you change by one sample, even for lengths below 64.
deer sir,
you were right
now i can finally build my overdrive
but i bet it will fry my cpu
pd redefining mathematics |expr fact(0)|==0
iem_blocksize~ >_<
pd redefining mathematics |expr fact(0)|==0
Oops! Looks like something went wrong!