[PD] Patching Circle At CRASH Space Los Angeles Saturday 2013-09-07
We haven't done a patching circle at CRASH Space in a bit, so let's do one! How about Saturday, 2013-09-07 from 2-6 PM? Come and join us - it's free and open to everyone, of course. CRASH Space is located at 10526 Venice Blvd, Culver City CA 90232. -Theron ^ ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[PD] applying perlin value to each iterated geo
Hi, im generating structures iterating geos in gem and was wondering
how can i apply an value from a perlin noise to each iterated
structure.
In processing i can do this in this way:
for(int i = 0 ; i < 20 ; i ++){
float perlin = noise( i * noiseScale, j * noiseScale);
pushMatrix();
translate(0 + (i * 20) , 0);
translate( 0, 0 , perlin * 30 );
rotateX( perlin );
rotateY( perlin );
box(perlin * 20 + 20);
popMatrix();
}
How can i do the same with Gem?
I been trying in the following way but its not working, any idea?
http://www.freeimagehosting.net/newuploads/2rf7o.png
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Re: [PD] MIDIFILE read Tempo
On 2013-09-05 09:29, Martin Peach wrote: On 2013-09-05 07:04, Maciej Sledziecki wrote: Hello, ist there any way to read the tempo information contained in a midi file? Or do I really have to set up a metro for mrpeach/midifile everytime ? It's been a while since I worked on that but I think you can dump the info and use that to set up a metro. I could probably add a message to get it to play automatically. If you bang the [midifile] after opening the file, the right outlet will emit ticks_per_quarternote and microsec_per_quarternote messages. So the millisecond rate for the [metro] would be = (microsec_per_quarternote/ticks_per_quarternote)/1000 See attached patch. Martin #N canvas 421 249 558 483 10; #X declare -lib mrpeach; #X obj 320 12 import mrpeach; #X obj 155 164 midifile; #X obj 200 340 /; #X obj 200 366 / 1000; #X obj 155 135 metro 2; #X obj 200 394 s ms_tempo; #X obj 194 108 r ms_tempo; #X obj 155 109 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0 1; #X floatatom 213 214 7 0 0 0 - - -; #X floatatom 367 214 7 0 0 0 - - -; #X floatatom 204 135 7 0 0 0 - - -; #X msg 64 147 rewind; #X obj 60 54 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1 -1; #X text 122 29 Read the midi file and bang it once to get the tempo into the metro; #X text 14 29 1>; #X text 39 55 2>; #X text 133 106 3>; #X text 157 74 or just start the metro and it will adjust after the first tick; #X obj 39 0 openpanel; #X msg 39 31 read \$1; #X obj 39 -18 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1 -1; #X obj 200 184 route microsec_per_quarternote ticks_per_quarternote ; #X connect 1 2 21 0; #X connect 2 0 3 0; #X connect 3 0 5 0; #X connect 4 0 1 0; #X connect 6 0 4 1; #X connect 6 0 10 0; #X connect 7 0 4 0; #X connect 11 0 1 0; #X connect 12 0 1 0; #X connect 18 0 19 0; #X connect 19 0 1 0; #X connect 20 0 18 0; #X connect 21 0 8 0; #X connect 21 0 2 0; #X connect 21 1 9 0; #X connect 21 1 2 1; ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] MIDIFILE read Tempo
That works great ! Even tempo changes within the file are updated. Thank you very much. Maciej Am 05.09.2013 um 18:36 schrieb Martin Peach: > On 2013-09-05 09:29, Martin Peach wrote: >> On 2013-09-05 07:04, Maciej Sledziecki wrote: >>> Hello, >>> >>> ist there any way to read the tempo information contained in a midi file? >>> Or do I really have to set up a metro for mrpeach/midifile everytime ? >> >> >> It's been a while since I worked on that but I think you can dump the >> info and use that to set up a metro. I could probably add a message to >> get it to play automatically. >> > > If you bang the [midifile] after opening the file, the right outlet will emit > ticks_per_quarternote and microsec_per_quarternote messages. > > So the millisecond rate for the [metro] would be = > (microsec_per_quarternote/ticks_per_quarternote)/1000 > > See attached patch. > > Martin > ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] MIDIFILE read Tempo
On 2013-09-05 07:04, Maciej Sledziecki wrote: Hello, ist there any way to read the tempo information contained in a midi file? Or do I really have to set up a metro for mrpeach/midifile everytime ? It's been a while since I worked on that but I think you can dump the info and use that to set up a metro. I could probably add a message to get it to play automatically. Martin ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Sinesum, cosinesum and cubic interpolation's guard points
OK, that's clear, thanks. Still when using [tabread4~] or [tabosc4~] you still need a copy of the last element in the first index and copies of the first two elements in the last two indices, right? Even if you're not using sinesum or cosinesum but some other mathematical function.. On Thu, Sep 5, 2013 at 1:56 PM, IOhannes m zmoelnig wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 2013-09-05 09:45, Alexandros Drymonitis wrote: > > OK, index 0 is the negative of index 2, > > no not really, they just happen to be the same. > > > which can again make sense as it's a sine (supposing that index 0 > > is a copy of the table's last element), but index 512 doesn't have > > that value, why? And why do indices 1 and 513 have different values > > too? > > do they? > > when it comes to floating point, "equality" becomes a little bit fuzzy. > e.g. "0.1" is really the 'same' as "0.10001490116119384765625" [1]. > > comparing the values, you can see that they are not *very* wrong: > > array[512]-array[0] = -5.30668e-6 = -0.053 > array[513]-array[1] = -5.30718e-6 = -0.053 > array[514]-array[2] = -5.30668e-6 = -0.053 > > so the errors are really rather small, and hopefully don't matter so > much in the interpolation (which is another approximation anyhow). > > the reason why the error is not smaller, is that Pd internally > (src/g_array.c:896) deals with a PI value of 3.14159, which is a > rather rough estimate and is the reason why the cycle is not exactly > 512 points long. > > > fgamsdr > IOhannes > > [1] > > http://en.wikipedia.org/wiki/Floating_point#Representable_numbers.2C_conversion_and_rounding > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.14 (GNU/Linux) > Comment: Using GnuPG with Icedove - http://www.enigmail.net/ > > iEYEARECAAYFAlIoY3UACgkQkX2Xpv6ydvTY1wCcDCyH8kY50snbVOv5AxwspIAB > jwQAoLJOrVoESvzyqrZyvWKky0ec1eUT > =YqkS > -END PGP SIGNATURE- > > ___ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[PD] MIDIFILE read Tempo
Hello, ist there any way to read the tempo information contained in a midi file? Or do I really have to set up a metro for mrpeach/midifile everytime ? Thanks for any advice, Maciej ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Sinesum, cosinesum and cubic interpolation's guard points
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-05 09:45, Alexandros Drymonitis wrote: > OK, index 0 is the negative of index 2, no not really, they just happen to be the same. > which can again make sense as it's a sine (supposing that index 0 > is a copy of the table's last element), but index 512 doesn't have > that value, why? And why do indices 1 and 513 have different values > too? do they? when it comes to floating point, "equality" becomes a little bit fuzzy. e.g. "0.1" is really the 'same' as "0.10001490116119384765625" [1]. comparing the values, you can see that they are not *very* wrong: array[512]-array[0] = -5.30668e-6 = -0.053 array[513]-array[1] = -5.30718e-6 = -0.053 array[514]-array[2] = -5.30668e-6 = -0.053 so the errors are really rather small, and hopefully don't matter so much in the interpolation (which is another approximation anyhow). the reason why the error is not smaller, is that Pd internally (src/g_array.c:896) deals with a PI value of 3.14159, which is a rather rough estimate and is the reason why the cycle is not exactly 512 points long. fgamsdr IOhannes [1] http://en.wikipedia.org/wiki/Floating_point#Representable_numbers.2C_conversion_and_rounding -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlIoY3UACgkQkX2Xpv6ydvTY1wCcDCyH8kY50snbVOv5AxwspIAB jwQAoLJOrVoESvzyqrZyvWKky0ec1eUT =YqkS -END PGP SIGNATURE- ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[PD] Sinesum, cosinesum and cubic interpolation's guard points
When you send this message [sinesum 512 1( to a table Pd will automatically add one index to the beginning of the table and two indices to its end, and you end up with a table of 515 indices. The three additional indices are the guard points for the cubic interpolation, right? So the first index should be a copy of the last element (here, index 0 a copy of index 512), and the last two indices should be copies of the first two elements (here, indices 513 and 514 copies of indices 1 and 2 respectively). Am I getting it right up to here? Well, with the message [cosinesum 512 0 1( this is indeed true; these are the values I get: index 512 = 0.25 index 0 = 0.25 index 1 = 1 index 513 = 1 index 2 = 0.25 index 514 = 0.25 Well, the second and the last elements have the same value anyway (index 2 and 512), which makes sense as it's a cosine. But if I send [sinesum 512 1( I'm getting these results: index 512 = -0.0122768 index 0 = -0.0122715 index 1 = 0 index 513 = -5.30718e-06 index 2 = 0.0122715 index 514 = 0.0122662 OK, index 0 is the negative of index 2, which can again make sense as it's a sine (supposing that index 0 is a copy of the table's last element), but index 512 doesn't have that value, why? And why do indices 1 and 513 have different values too? ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
