On Feb 7, 5:13pm, William Kleinsasser wrote:
When trying to create a new array using the menu, I get an error:
bad screen distance ".x1008a828.a10095220"
and see no new array. When I try to send messages to it (array2) I am told that it doesn't exist. Also, moving the arrays around the screen is very slow.
Is there a simple way to create and use envelope shapes like Hamming, Hanning, etc.?
Thanks,
Bill
-- End of excerpt from William Kleinsasser
Ouch... I never saw the error you're getting creating tables, the "bad screen distance ".x1008a828.a10095220"
Does this happen if you make a new document and put an array into it or is there more context I should reproduce? Also, I forgot which kind of machine you run on; perhaps there's a bizarre machine dependency lurking.
You can make Hanning/Hamming windows by blasting an oscillator right into tabwrite~, although it's tricky setting the phase. (you do it by taking a snapshot~ of the phasor~ output and subtracting that number from phasor~'s future output. Not that tabread4~'s 4-point interpolation means that its input should be between 1 and size-2.
cheers Miller
Miller and others,
Ouch... I never saw the error you're getting creating tables, the "bad screen distance ".x1008a828.a10095220"
Does this happen if you make a new document and put an array into it or is there more context I should reproduce? Also, I forgot which kind of machine you run on; perhaps there's a bizarre machine dependency lurking.
Sorry to be ambiguous. First: O2, R5000 irix 6.3. I am trying to addarrays to the patch that you sent to us for tabwrite/read. I'll try to recreate the problem from a fresh window and let you know tomorow.
You can make Hanning/Hamming windows by blasting an oscillator right into tabwrite~, although it's tricky setting the phase. (you do it by taking a snapshot~ of the phasor~ output and subtracting that number from phasor~'s future output. Not that tabread4~'s 4-point interpolation means that its input should be between 1 and size-2.
Thanks. I'll give it a shot.
Bill
Ouch... I never saw the error you're getting creating tables, the "bad screen distance ".x1008a828.a10095220"
Does this happen if you make a new document and put an array into it or is there more context I should reproduce? Also, I forgot which kind of machine you run on; perhaps there's a bizarre machine dependency lurking.
Miller and others,
Here is the patch that gave me the problems. It's the patch that Miller sent last week for array work.
Problems:
- I have resized the array (10 sec @ 44100). When I try to
create a second array from the menu I get the "bad screen distance" error described before.
patch #1:
#N canvas 508 31 663 743 10; #X obj 361 501 tabwrite~ array1; #X msg 278 425 bang ; pd dsp 1; #X msg 45 62 bang ; pd dsp 1; #X obj 213 178 * 44.1; #X floatatom 212 154 100; #X obj 213 229 line~; #X floatatom 112 152 100; #X floatatom 42 168 1; #X obj 42 192 sig~; #N canvas 0 0 650 696 Untitled-1 1; #X graph graph1 0 -1 44100 1 141 327 541 27; #X array array1 44100 float; #X pop; #X msg 152 348 ; array1 read foo.tab; #X msg 152 398 ; array1 write foo.tab; #X msg 152 489 ; array1 print; #X msg 150 444 array1 resize 88200; #X restore 437 92 page table; #X obj 84 354 sig~ 0.1; #X obj 44 353 *~; #X obj 318 248 metro; #X msg 319 201 1; #X floatatom 319 224 1; #X obj 414 309 tabwrite~ array1; #X obj 414 228 sig~; #X obj 414 198 random 1000; #X obj 414 253 phasor~; #X obj 414 283 cos~; #X obj 43 382 hip~ 5; #X obj 46 412 dac~; #X obj 44 322 tabread4~ array1; #X obj 41 218 phasor~; #X msg 383 151 bang ; pd dsp 1; #X obj 113 227 line~; #X obj 44 247 *~; #X obj 44 279 +~; #X obj 111 177 * 44.1; #X msg 112 123 100; #X obj 315 279 random 30; #X obj 367 427 adc~; #X obj 115 203 pack 0 1000; #X obj 212 205 pack 0 1000; #X floatatom 150 266 44100; #X obj 149 289 sig~; #X obj 375 470 line~; #X obj 232 33; #X connect 1 0 0 0; #X connect 1 0 36 0; #X connect 2 0 29 0; #X connect 2 0 7 0; #X connect 3 0 33 0; #X connect 4 0 3 0; #X connect 5 0 27 1; #X connect 6 0 28 0; #X connect 7 0 8 0; #X connect 8 0 23 0; #X connect 10 0 11 1; #X connect 11 0 20 0; #X connect 12 0 17 0; #X connect 12 0 30 0; #X connect 13 0 14 0; #X connect 14 0 12 0; #X connect 16 0 18 0; #X connect 17 0 16 0; #X connect 18 0 19 0; #X connect 19 0 15 0; #X connect 20 0 21 0; #X connect 20 0 21 1; #X connect 22 0 11 0; #X connect 23 0 26 0; #X connect 24 0 13 0; #X connect 24 0 15 0; #X connect 26 0 27 0; #X connect 27 0 22 0; #X connect 28 0 32 0; #X connect 29 0 6 0; #X connect 29 0 4 0; #X connect 30 0 12 1; #X connect 31 0 0 0; #X connect 32 0 25 0; #X connect 33 0 5 0; #X connect 34 0 35 0; #X connect 35 0 26 1; #X connect 36 0 0 0;
Perhaps you can recreate the error. Thanks,
Bill
Is there a way to trigger phasor~ to restart at 0-degrees once it has been set in motion?
Bill
-
Miller Puckette -
William Kleinsasser