On Tue, 2008-03-18 at 01:26 -0700, Spencer Russell wrote:
> On Tue, 2008-03-18 at 17:17 +0900, hard off wrote:
> > oops, sorry for double reply spencer..forgot to send this mail to the
> > list.
>
> no problem. I get the digest, so this sped up the process, anyways! :)
> >
> >
> > the [send~] &
On Tue, 2008-03-18 at 17:17 +0900, hard off wrote:
> oops, sorry for double reply spencer..forgot to send this mail to the
> list.
no problem. I get the digest, so this sped up the process, anyways! :)
>
>
> the [send~] & [receive~] objects only work for default block size.
hmm, the block~ docu
oops, sorry for double reply spencer..forgot to send this mail to the list.
the [send~] & [receive~] objects only work for default block size.
you can create a table the same size as your new blocksize, and use
[tabsend~] / [tabreceive~], although i think that might bring in a one block
delay,
I'm trying to send some signals around a reblocked patch, and I'm
getting the following errors:
error: sigsend 1002-test: unexpected vector size
error: receive~ 1002-test: vector size mismatch
this happens in a simple test patch with a send~/receive~ pair inside of
a subpatch that's reblocked to
