[PD] spread Gem-computation over several dsp-cycles (?) (was: [Gem]: gem-pointer and [list] OR slow [repeat])

Roman Haefeli reduzierer at yahoo.de
Thu Mar 1 03:34:37 CET 2007


as always: i forgot the attachment........

On Wed, 2007-02-28 at 23:24 +0100, Roman Haefeli wrote:
> On Wed, 2007-02-28 at 07:14 -0600, chris clepper wrote:
> > On 2/28/07, Roman Haefeli <reduzierer at yahoo.de> wrote:
> >         
> >         
> >         i might be wrong but in my eyes it doesn't make sense to do
> >         all the work
> >         that could be done in 50ms in only 1.45ms. 
> > 
> > What?  GEM doesn't use the DSP clock.  It will take as much time as
> > needed to render.  
> 
> oops. ok....
>  
> > For example, the current work I have uses three or four 1080i clips, a
> > live feed and records to disk and there is no way that all runs in
> > 1.45ms.  It takes about 12-15ms!
> 
> anyway, i get dropouts when doing gem-rendering, although 'top' tells me
> that pd uses only 20% cpu-time. i don't care much about the audio (as
> IOhannes mentioned, i could run two instances of pd). the problem is
> that the timing is not nice. i'd like to run the patch with 20 frames
> per second. but in praxis each cycle needs 70ms, which gives me a
> framerate of 14. 
> 
> is my gpu too slow? what happens, when the gpu is overloaded? can that
> cause pd to stuck?
> 
> i attached a little gem-benchmark-test. although you say, gem doesn't
> use the dsp-clock, it takes much longer to compute the first block after
> a gem-rendering command. why is that? 
> and: here on my system, the [realtime] measures up to 70ms, when i go
> over [repeat 1400] (under 1400 it's 50ms). the funny thing is, that it
> stays around 70ms, even if i set the [repeat] up to 3000 or more. why is
> that? here on my system, cpu-time used by pd is always 20%.
> 
> sorry to ask you so much...... but i try to understand things a bit
> better.......
> 
> roman
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 	
> 		
> ___________________________________________________________ 
> Der frhe Vogel fngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
> 
> 
> _______________________________________________
> PD-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-------------- next part --------------
#N canvas 394 19 736 552 10;
#X obj 26 123 gemwin;
#X obj 26 42 sel 0 1;
#X msg 26 95 0 \, destroy;
#X obj 26 19 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 1 1
;
#X obj 216 102 gemhead;
#X obj 216 152 translateXYZ 1 1 0;
#X obj 23 152 gemhead;
#X obj 23 210 world_light;
#X msg 48 66 perspec -1 1 -1 1 2 2000 \, lighting 1 \, create \, 1
;
#X obj 23 177 rotateXYZ 30 -54 0;
#N canvas 1115 145 249 311 measure_realtime 0;
#X obj 39 40 t b b;
#X obj 39 256 outlet;
#X obj 39 16 gemhead;
#X obj 39 141 f;
#X obj 39 186 +;
#X obj 39 163 * 9;
#X obj 39 209 * 0.1;
#X obj 39 118 t b f;
#X text 97 155 smooth it a bit;
#X obj 39 62 realtime;
#X connect 0 0 9 0;
#X connect 0 1 9 1;
#X connect 2 0 0 0;
#X connect 3 0 5 0;
#X connect 4 0 6 0;
#X connect 5 0 4 0;
#X connect 6 0 3 1;
#X connect 6 0 1 0;
#X connect 7 0 3 0;
#X connect 7 1 4 1;
#X connect 9 0 7 0;
#X restore 198 339 pd measure_realtime;
#X floatatom 198 368 5 0 0 0 - - -;
#X obj 217 236 rotateXYZ 1 0 0;
#X text 247 370 <- check if it goes higher than 50ms;
#X obj 217 298 cube 0.02;
#X obj 217 211 translateXYZ -0.001 0 0;
#X obj 217 263 translateXYZ 0 0 0.02;
#X obj 31 249 bang~;
#X obj 31 276 t b b;
#X obj 31 300 realtime;
#X obj 31 326 t b f;
#X obj 31 350 f;
#X obj 58 351 + 1;
#X obj 31 379 pack f f;
#X obj 99 245 gemhead;
#X obj 99 270 b;
#X obj 99 293 0;
#X floatatom 31 434 0 0 0 0 - - -;
#X floatatom 85 435 0 0 0 0 - - -;
#X floatatom 127 435 0 0 0 0 - - -;
#X floatatom 171 436 0 0 0 0 - - -;
#X floatatom 214 436 0 0 0 0 - - -;
#X floatatom 255 437 0 0 0 0 - - -;
#X text 37 457 1;
#X text 94 458 2;
#X text 135 458 3;
#X text 180 459 4;
#X text 225 459 5;
#X obj 31 403 route 0 1 2 3 4 5;
#X text 262 459 6;
#X text 28 477 realtime measured lenght of the nth dsp-cycle after
the [gemhead] starts rendering.;
#X obj 216 129 rotateXYZ 0 0 90;
#X obj 216 187 repeat 2000;
#X text 55 17 <- rendering on/off;
#X floatatom 380 146 5 0 0 0 - - -;
#X text 425 143 <- try different 'loads';
#X connect 1 0 2 0;
#X connect 1 1 8 0;
#X connect 2 0 0 0;
#X connect 3 0 1 0;
#X connect 4 0 41 0;
#X connect 5 0 42 0;
#X connect 6 0 9 0;
#X connect 8 0 0 0;
#X connect 9 0 7 0;
#X connect 10 0 11 0;
#X connect 12 0 16 0;
#X connect 15 0 12 0;
#X connect 16 0 14 0;
#X connect 17 0 18 0;
#X connect 18 0 19 0;
#X connect 18 1 19 1;
#X connect 19 0 20 0;
#X connect 20 0 21 0;
#X connect 20 1 23 1;
#X connect 21 0 22 0;
#X connect 21 0 23 0;
#X connect 22 0 21 1;
#X connect 23 0 38 0;
#X connect 24 0 25 0;
#X connect 25 0 26 0;
#X connect 26 0 21 1;
#X connect 38 0 27 0;
#X connect 38 1 28 0;
#X connect 38 2 29 0;
#X connect 38 3 30 0;
#X connect 38 4 31 0;
#X connect 38 5 32 0;
#X connect 41 0 5 0;
#X connect 42 0 15 0;
#X connect 44 0 42 1;


More information about the Pd-list mailing list