Hi , im making a patch in gem that performs infinite zooming, using iterative processing zexys "repeat" object. im trying to do this by using a feedback algorithm that increase the number of the "repeat" parameter, but i have 2 problems: the first one is that after some time the continuity of the repeating element get broken. and the second one is that the patch begins to eat my cpu progresively. CAn u help me to fix this? or Maybe you know another way to make the same.

many thanks for your help

siggmus

#N canvas 350 44 1011 687 10; #X obj 20 57 gemwin; #X msg 20 22 create , 1; #X msg 90 22 color 0.2 0 0.5; #X msg 106 47 lighting 1; #X obj 83 658 sphere; #X obj 83 372 gemhead; #X obj 83 485 scaleXYZ; #X obj 83 402 translateXYZ; #X floatatom 178 300 5 0 0 0 - - -; #X obj 251 79 world_light; #X obj 243 5 gemhead 1; #X msg 328 54 1 1 0; #X obj 83 458 rotateXYZ 0 0 0; #X floatatom 127 354 5 0 0 0 - - -; #X obj 83 630 translateXYZ 0 0 -0.9; #X msg 226 462 40; #X obj 83 604 repeat 40; #X obj 319 423 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X msg 242 325 $1; #X obj 342 480 int; #X obj 527 206 int; #X obj 538 245 + 1; #X obj 526 112 bng 30 250 50 0 empty empty empty 0 -6 0 8 -258699 -1 -1; #X floatatom 528 286 5 0 0 0 - - -; #X floatatom 311 540 5 0 0 0 - - -; #X obj 243 359 select 10; #X obj 225 433 loadbang; #X msg 419 365 40; #X obj 414 323 loadbang; #X obj 197 564 + 40; #X floatatom 132 581 5 0 0 0 - - -; #X obj 529 173 metro 100; #X obj 404 460 * 2; #X msg 127 312 -3; #X obj 108 270 loadbang; #X connect 1 0 0 0; #X connect 2 0 0 0; #X connect 3 0 0 0; #X connect 5 0 7 0; #X connect 6 0 16 0; #X connect 7 0 12 0; #X connect 8 0 7 3; #X connect 8 0 18 0; #X connect 10 0 9 0; #X connect 11 0 9 1; #X connect 12 0 6 0; #X connect 13 0 7 2; #X connect 14 0 4 0; #X connect 15 0 19 1; #X connect 16 0 14 0; #X connect 17 0 19 0; #X connect 18 0 25 0; #X connect 19 0 24 0; #X connect 19 0 32 0; #X connect 20 0 21 0; #X connect 21 0 20 1; #X connect 21 0 23 0; #X connect 22 0 31 0; #X connect 23 0 8 0; #X connect 24 0 25 1; #X connect 24 0 29 0; #X connect 25 0 17 0; #X connect 26 0 15 0; #X connect 27 0 19 1; #X connect 27 0 17 0; #X connect 28 0 27 0; #X connect 29 0 30 0; #X connect 30 0 16 1; #X connect 31 0 20 0; #X connect 32 0 19 1; #X connect 33 0 13 0; #X connect 34 0 33 0; #X connect 34 0 2 0; #X connect 34 0 11 0; #X connect 34 0 3 0;

On Fri, Oct 15, 2004 at 07:47:27PM -0600, thewade wrote:

I just got 2.6.9-rc3-mm3-VP-T3 running on my AMD64 laptop. I was told some people are opperating their machines with jack running at 64 frames of buffer. My jackd statement looks like this: sudo jackd -R -d alsa -d hw:1 -r 48000 -p 256 anything less than 256 causes xruns just when I move the mouse around...

When I run medium sized patches I get errors like A/D/A Sync: What causes these errors? When I run large patches jackd says something like delay of xxxx usec spare time yyyy restarting... What configure options should I have built jack with? (./configure --with-default-tmpdir=/dev/shm)

My .pdrc file looks like this: -jack -rt -path /usr/local/lib/pd/externs -path /usr/local/lib/pd/extra -path /home/wade/pd/general -path /home/wade/pd -lib sphere~ -lib fftbin~ -lib zexy -lib Gem -mididev 1,2,3 -r 48000 -channels 18

If I dont specify an audiobuf or blocksize, what are the defaults?

64-sample jack buffer works here. 2.6.9-final CONFIG_PREEMPT=y (no psycho patches..) echoaudio nforce3 939-3000+

with that kinda rice in your kernel string, you might want to try devel_0_37 and paste this into configure.in:

   if test "$optimize" == "k8"; then
      ARCH_CFLAGS="-march=k8 -mmmx -msse -msse2 -mfpmath=sse"
   fi

and configure with:

./configure --enable-jack --enable-alsa --enable-optimize=k8 --enable-simd --enable-threadedsf

but i'm only tasting with 'warbly sine wave thing.' because soundfiles arent loading. have you gotten that to work?

default blocksize is 64, but i tried 48 and 96 and it made no difference. first thing you want to do is get jack working without the xrun messages...

Im using a hammerfall multiface, and it seems like a brand new machine with a super-duper kernel and a nice piece of hardware like the hammerfall should allow me to run pd at 5.333 msec latency without xruns or delay of xxxx usec spare time yyyy restarting... errors. Can someone help me to get pd, jack and my machine tuned?

I dont have preemptable latency tracing because Ingo M. told me that it causes badness on x64 architectures, so I cant use that.

Thanks for the help! -thewade

---

PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list