On 26/02/16 03:21, Alexandre Torres Porres wrote:
howdy, is there any particularly good reason why [s~]/[r~] must run at only
64 block sizes?
if the issue is that they may have conflicting/different sizes between
them, why not give the same error as you get now for blocks other than 64?
"receive~ x: vector size mismatch
sigsend x: unexpected vector size"
It'd be really convenient for feedback loops
if you want something that works right now, tabsend~ and tabreceive~
don't have any restriction about table size must be equal to block size
must be equal to 64
see attached example of a single self-modulating fm oscillator with
single sample feedback (block~ 1)
Claude
--
http://mathr.co.uk
#N canvas 1 51 450 300 10;
#X obj 98 171 dac~;
#N canvas 1 51 450 300 single-sample-feedback 0;
#X obj 186 41 block~ 1;
#X obj 52 214 osc~;
#X obj 51 259 outlet~;
#X obj 129 250 tabsend~ \$0-feedback;
#X obj 114 104 tabreceive~ \$0-feedback;
#X obj 49 187 mtof~;
#X obj 50 137 *~;
#X obj 69 65 inlet~;
#X obj 50 159 +~ 60;
#X obj 119 178 table \$0-feedback 1;
#X connect 1 0 2 0;
#X connect 1 0 3 0;
#X connect 4 0 6 0;
#X connect 5 0 1 0;
#X connect 6 0 8 0;
#X connect 7 0 6 1;
#X connect 8 0 5 0;
#X restore 107 85 pd single-sample-feedback;
#X obj 110 138 *~ 0.5;
#X obj 107 35 osc~ 0.1;
#X obj 205 179 table \$0-scope 1024;
#X obj 206 155 tabwrite~ \$0-scope;
#X obj 208 133 metro 300;
#X obj 211 112 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 1
1;
#X obj 107 57 *~ 48;
#X connect 1 0 2 0;
#X connect 1 0 5 0;
#X connect 2 0 0 0;
#X connect 2 0 0 1;
#X connect 3 0 8 0;
#X connect 6 0 5 0;
#X connect 7 0 6 0;
#X connect 8 0 1 0;
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
