Pd-list March 2007

pd-list@lists.iem.at

139 participants
278 discussions

re:Lindenmayer system in pd / GEM
by Luigi Rensinghoff 01 Mar '07

01 Mar '07

Hi List.. I came across these patches by Cyrille Henry, the postings are from august 2006. when i try to open the patches i am missing "rule" and "rule2". Strange that nobody mentioned it back then. Well i was just curious to see how its done in GEM. Best Regards Luigi See below, for an example ------------------------------------------------------------------------ ---------------------------------------------- #N canvas 561 190 503 642 10; #X obj 37 108 gemhead; #N canvas 0 0 558 408 + 0; #X obj 29 20 inlet; #X obj 28 69 translateXYZ 0 0 0; #X obj 29 46 rotateXYZ 0 0 30; #X obj 105 19 inlet; #X connect 0 0 2 0; #X connect 2 0 1 0; #X connect 3 0 2 3; #X restore 68 472 pd +; #N canvas 0 0 554 404 - 0; #X obj 29 20 inlet; #X obj 28 69 translateXYZ 0 0 0; #X obj 29 46 rotateXYZ 0 0 -30; #X obj 132 18 inlet; #X connect 0 0 2 0; #X connect 2 0 1 0; #X connect 3 0 2 3; #X restore 92 494 pd -; #X obj 37 351 any; #X obj 68 351 any; #X obj 92 351 any; #X obj 118 518 GEMglPushMatrix; #X obj 146 545 GEMglPopMatrix; #X obj 118 352 any; #X obj 146 352 any; #X floatatom 214 282 5 0 0 0 - - -; #X obj 37 156 rotateXYZ 0 0 90; #X floatatom 260 431 5 0 0 0 - - -; #X obj 231 363 line; #X floatatom 231 320 5 0 0 0 - - -; #X msg 231 340 \$1 100; #X floatatom 241 387 5 0 0 0 - - -; #X msg 231 300 0.2; #X obj 37 232 rule; #N canvas 189 124 601 813 F 0; #X obj 28 20 inlet; #X obj 284 140 inlet; #X obj 28 261 translateXYZ 0.05 0 0; #X obj 28 288 rotateXYZ; #X obj 337 143 inlet; #X obj 385 146 inlet; #X obj 28 189 rotateXYZ 0 90 0; #X obj 28 238 rotateXYZ 0 -90 0; #X obj 34 562 rotateXYZ; #X obj 28 93 t a b; #X obj 170 386 random 1000; #X obj 170 465 *; #X obj 248 387 random 1000; #X msg 170 361 seed \$1; #X obj 248 338 + 1; #X msg 248 362 seed \$1; #X obj 248 468 *; #X obj 78 385 random 1000; #X obj 78 331 r rand_seed; #X obj 117 430 r rand; #X obj 78 461 *; #X msg 78 357 seed \$1; #X obj 170 335 + 1; #X obj 78 410 - 500; #X obj 170 412 - 500; #X obj 248 412 - 500; #X obj 106 19 inlet; #X obj 106 48 unpack f f; #X text 175 46 size \, order; #X obj 116 73 - 1; #X obj 74 78 / 300; #X obj 114 128 / 300; #X obj 74 502 *; #X obj 165 505 *; #X obj 243 504 *; #X obj 317 440 + 1; #X obj 34 588 spigot; #X msg 190 572 1; #X msg 217 576 0; #X obj 34 612 color 0 1 0; #X obj 28 161 color 0.6 0.6 0.6; #X obj 34 635 scaleXYZ 1 0.33 0.1; #X obj 34 683 scaleXYZ 1 3 10; #X obj 34 659 sphere 0.05; #X obj 197 542 sel 1; #X obj 111 99 max 1; #X obj 28 214 tube 0.02 0.02 1 10; #X connect 0 0 9 0; #X connect 1 0 2 1; #X connect 1 0 46 3; #X connect 2 0 3 0; #X connect 3 0 8 0; #X connect 4 0 3 3; #X connect 5 0 3 1; #X connect 6 0 46 0; #X connect 7 0 2 0; #X connect 8 0 36 0; #X connect 9 0 40 0; #X connect 9 1 10 0; #X connect 9 1 17 0; #X connect 9 1 12 0; #X connect 10 0 24 0; #X connect 11 0 33 0; #X connect 12 0 25 0; #X connect 13 0 10 0; #X connect 14 0 15 0; #X connect 15 0 12 0; #X connect 16 0 34 0; #X connect 17 0 23 0; #X connect 18 0 21 0; #X connect 18 0 22 0; #X connect 19 0 20 1; #X connect 19 0 11 1; #X connect 19 0 16 1; #X connect 20 0 32 0; #X connect 21 0 17 0; #X connect 22 0 13 0; #X connect 22 0 14 0; #X connect 23 0 20 0; #X connect 24 0 11 0; #X connect 25 0 16 0; #X connect 26 0 27 0; #X connect 27 0 29 0; #X connect 27 0 30 0; #X connect 27 1 35 0; #X connect 27 1 44 0; #X connect 29 0 45 0; #X connect 30 0 46 1; #X connect 31 0 46 2; #X connect 32 0 8 1; #X connect 33 0 8 2; #X connect 34 0 8 3; #X connect 35 0 34 1; #X connect 35 0 33 1; #X connect 35 0 32 1; #X connect 36 0 39 0; #X connect 37 0 36 1; #X connect 38 0 36 1; #X connect 39 0 41 0; #X connect 40 0 6 0; #X connect 41 0 43 0; #X connect 43 0 42 0; #X connect 44 0 37 0; #X connect 44 1 38 0; #X connect 45 0 31 0; #X connect 46 0 7 0; #X restore 37 446 pd F ---------; #X obj 37 182 t b a b; #X obj 111 226 s rand_seed; #X obj 223 170 s rand; #X obj 223 148 / 1000; #X floatatom 223 130 5 0 0 0 - - -; #X floatatom 309 457 5 0 0 0 - - -; #X obj 37 298 route F + - [ ]; #X obj 68 323 t b; #X obj 92 323 t b; #X obj 118 323 t b; #X obj 146 324 t b; #X obj 37 323 t b l; #X msg 37 207 F 1 0; #X msg 260 409 30; #X msg 309 434 -30; #X obj 37 275 rule; #X obj 37 254 rule; #X msg 214 259 0.24; #X obj 37 133 translateXYZ 1 -3 0; #X msg 111 205 15; #X obj 38 11 gemhead; #X obj 38 33 world_light; #X msg 223 107 -34; #X obj 214 231 loadbang; #X obj 223 84 loadbang; #X obj 38 82 gemwin; #X msg 38 57 create \, 1 \, lighting 1; #X text 43 594 same exemple as the previus one \, but with some random.; #X text 42 616 you nead a good graphyc card to load that patch.; #X connect 0 0 38 0; #X connect 3 0 19 0; #X connect 4 0 1 0; #X connect 5 0 2 0; #X connect 8 0 6 0; #X connect 9 0 7 0; #X connect 10 0 19 2; #X connect 11 0 20 0; #X connect 12 0 1 1; #X connect 13 0 19 3; #X connect 14 0 15 0; #X connect 15 0 13 0; #X connect 16 0 19 4; #X connect 17 0 14 0; #X connect 18 0 36 0; #X connect 20 0 32 0; #X connect 20 1 3 1; #X connect 20 1 4 1; #X connect 20 1 5 1; #X connect 20 1 8 1; #X connect 20 1 9 1; #X connect 20 2 39 0; #X connect 23 0 22 0; #X connect 24 0 23 0; #X connect 25 0 2 1; #X connect 26 0 31 0; #X connect 26 1 27 0; #X connect 26 2 28 0; #X connect 26 3 29 0; #X connect 26 4 30 0; #X connect 27 0 4 0; #X connect 28 0 5 0; #X connect 29 0 8 0; #X connect 30 0 9 0; #X connect 31 0 3 0; #X connect 31 1 19 1; #X connect 32 0 18 0; #X connect 33 0 12 0; #X connect 34 0 25 0; #X connect 35 0 26 0; #X connect 36 0 35 0; #X connect 37 0 10 0; #X connect 38 0 11 0; #X connect 39 0 21 0; #X connect 40 0 41 0; #X connect 42 0 24 0; #X connect 43 0 37 0; #X connect 43 0 17 0; #X connect 44 0 42 0; #X connect 46 0 45 0;

3 2

pd39.2 test 7 - text objects ++
by timon 01 Mar '07

01 Mar '07

Hi HC Im using your installer yet again. Thank you for the great work. Just trying to find out why: All text objects in GEM wont work at all Zexy objects - aliases - are all broken Alternate - broken line3 - broken remote - broken randomF - broken ascseq - broken invert - broken They have all been fully working objects in the past. Is there a reason for them to be disabled or have they migrated to a different library? If so what library? And finally, is there a way of keeping track of such changes? Thanks, timon

5 9

small set of vector transforming abstractions
by Roman Haefeli 01 Mar '07

01 Mar '07

hi all during my trials with gem i made a little set of abstractions, that hopefully could be usefull when dealing with vectors. at least they have been for me. the set contains: [v_+] : adds two vectors [v_-] : subtracts a vector from another [v_scale] : scales a vector [v_mag] : outputs the magnitude of a vector [v_normalize] : normalizes a vector (so that its magnitude becomes 1) [v_x] : computes the cross product of two vectors [v_rotate] : rotates a vector around another let me know if you miss something or if you find it not useable at all. it can be downloaded from here: http://romanhaefeli.net/pd/v_abstractions.tar.gz roman ___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

4 6

Re: [PD] spread Gem-computation over several dsp-cycles (?) (was: [Gem]: gem-pointer and [list] OR slow [repeat])
by Roman Haefeli 01 Mar '07

01 Mar '07

On Wed, 2007-02-28 at 07:14 -0600, chris clepper wrote: > On 2/28/07, Roman Haefeli <reduzierer(a)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 frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

2 4

[PD-announce] KnobsAndSlidersDS
by Chris McCormick 01 Mar '07

01 Mar '07

Hi All, KnobsAndSlidersDS allows you to use your Nintendo DS touchscreen to control your Pure Data patches using the FUDI protocol over wifi. You can build interfaces dynamically on the DS touchscreen from inside Pure Data running on your PC/laptop. <http://mccormick.cx/projects/KnobsAndSlidersDS/> I wrote it because I am travelling next year, and I can't take my Midi hardware with me, and need something compact and portable with which to interact with my patches (and I don't like playing the 808 with a long stick). Have fun! Chris. ------------------- chris(a)mccormick.cx http://mccormick.cx _______________________________________________ PD-announce mailing list PD-announce(a)iem.at http://lists.puredata.info/listinfo/pd-announce

2 6

[Gem] angles -> vector translation
by Roman Haefeli 01 Mar '07

01 Mar '07

hello everyone i am working on a gem-patch. i want to make the user feel like flying freely through the 3d-space (what an ugly old-schooled sentence, i know ;-). the problem i have is, that when i rotate the world, i would like the user to fly in the same direction, so that when moving the vanishing point stays in the middle of the gemwin to create the feeling of always looking forward. in other words, i need to 'translate' the rotation done with [rotateXYZ] by the three axes X, Y and Z to a vector {x,y,z}, so that the user flies in the same direction as he is looking to. i was told that what i want to achieve is done with a matrix, but unfortunately my mathematical knowledge is far from being able to set it up myself. examples: the user is looking to: vector to translate ('move'): angle X = 0° Vx = 0 angle Y = 0° Vy = 0 angle Z = 0° Vz = 1 angle X = 0° Vx = -1 angle Y = 90° Vy = 0 angle Z = 0° Vz = 0 angle X = 90° Vx = 0 angle Y = 0° Vy = 1 angle Z = 0° Vz = 0 how can i compute the correct vector for any set of angles? sorry for any inconvenience because of terms that might be used in the wrong way. i am not a mathematician and i hope, it is still clear, what i want to achieve. many thanks in advance for any help. roman ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

6 12

[Gem]: gem-pointer and [list] OR slow [repeat]
by Roman Haefeli 01 Mar '07

01 Mar '07

hi all it's a known trick to use [repeat] from zexy in a gem render chain to produce funny effects and to multiply the rendering of the attached objects. the problem i have here, is that i use a [repeat] with a very high iteration number (>1000). after the [repeat 1000] some stuff is calculated and read from tables and then sent to gem-objects on each iteration. this works well, but on each render-cycle i get a short dropout. i use the default framerate of 20, that should make 50ms per frame, but with [realtime] i measure around 70ms. i could live with that, but i thought that this could be optimized. it's the concept of pd, that when a message is triggered, it gets completely processed in the same dsp-cycle. but when working with gem, this makes absolutely no sense, since the time between each render cycle is much higher (50ms in my case). that's why i wanted to build a slow repeat with [until] and [list], so that i can spread the 1000 iterations over the whole 50ms. unfortunately it is not possible to store a gem pointer with [list]. when i connect a [gemhead] to the right inlet of a [list] and turn rendering on, pd immediately crashes (at least here, i didn't test on other computers). i tried also to bang 'manually' the [gemhead] instead, but then the iterations don't have any effect (no objects are multiplied). is there any way to store a gem pointer? or is there another way of producing slow repeats of a gem pointer? any help appreciated! roman ___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

7 13

fn delete
by marius schebella 01 Mar '07

01 Mar '07

Hi, speaking about annoying things so much leads me to post another problem, that fn + delete, which usually deletes the character right of the cursor on osx, does not work in pd. there appears a funny rectangle character. maybe this one is easier to solve? I also had that problem on some linux machines, btw. whereas on windows it was not possible at all to delete what is right of the cursor, if I remember correctly. marius.

5 5

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list March 2007