03-oversampling.pd

I was writing up a quick demo of oversampling, and found to my surprise that [block~] seems to be ignoring messages. I've got a toggle going into the subpatch, [inlet] --> [* 7] --> [+ 1] --> "64 1 $1" --> [block~], and when I flip the toggle, there's no difference in the sound.

I even tried switching dsp off and on again, but no dice.

Are messages to [block~] supposed to work? Or, should they be sent only when dsp is already off?

Here's another version of the patch that switches DSP off, sends the block~ message, then switches back on. I don't hear it doing anything. OK, worst case I'll just have two oscillators and switch them at the output, but the block~ help patch documents that a message can be used and AFAICS it doesn't work.

03-oversampling-b.pd

TIA,
hjh

use [set 64 1 $1(
no need to switch dsp off

@ddw_music I tested a few of my FFT patches that have adjustable window sizes and they all seem to still work on 0.56.2 without having to cycle dsp off and on. I can confirm that your patch isn't responding though, so maybe there's an issue with the oversampling portion of the message? If I enter your params as arguments in the block~ object, it seems to work fine. Maybe use dynamic patching as a temporary workaround?

@solipp said:

use [set 64 1 $1(
no need to switch dsp off

Thanks -- in the reference, I saw "<list>" but I missed the "set" before it. Good catch.

Yeah, it's working now!

hjh

@solipp said:

use [set 64 1 $1(
no need to switch dsp off

OMG, I was staring at my own code and didn't see that!