[PD] DMX USB
Does someone try to pilot a Enttec DMX USB pro via the comport external Thank's Ivan Chabanaud 06 21 03 76 13 http://www.chabalab.net ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] DMX USB
I tried it once, but had no luck with it. I think it was a driver issue and I think I tried it with a midi 2 dmx bridge, which did not work. (I think I did not use comport). But I would like to see this working! marius. ivan Chabanaud wrote: Does someone try to pilot a Enttec DMX USB pro via the comport external Thank's Ivan Chabanaud 06 21 03 76 13 http://www.chabalab.net ___ 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
Re: [PD] relative pathes: problems with [open(-message to pd
On Sat, 2007-03-24 at 10:14 +0800, Chris McCormick wrote: On Fri, Mar 23, 2007 at 11:20:01PM +0100, Roman Haefeli wrote: On Fri, 2007-03-23 at 10:04 +0100, Steffen wrote: On 22/03/2007, at 23.41, Roman Haefeli wrote: When opening patches by sending messages to pd, the path is relative to pd's startup-location. when loading other files (text-, audio-, data-files etc) the path is set relative to the location of the patch. since the patch doesn't know, where pd was started, you actually cannot use relative pathes when opening patches by messages without: Maybe [declare] can help you? (Pd = 0.40) i'm afraid, it doesn't. as i understand [declare], it lets you add pathes, so that it finds abstractions or libs. but it doesn't help, when opening a patch by message to pd. but it's a good point to point to [declare], since it lets you decide between relative to patch and relative to pd. i'd like to have the same opportunity for the [open(-message. actually there are three different relative paths involved in pd: - relative to pd - relative to patch - relative to start-up location i claim to deprecate the latter. i think, now everyone knows about my opinion about this topic ;-) it would be nice to hear more voices. does anything speak _for_ 'relative to start-up location'? Yep. If I understand your meaning correctly, 'relative to start-up location' is useful in situations where you are building an application that uses Pd at it's core. You want the patches to start up correctly no matter where the user installs the entire package for Puredata+Gem+application patches. This is the case with the Ergates program I announced on this list a while ago. I'm building a windows installer for it (very slowly) and I don't think it would work without relative to start-up paths. hm i think i see, what you mean. whenever a set of patches and/or externals is packed together with a startup-file (bash-script for unix, bat-file for windows), it seems to make sense to specify pathes relative to the start-up location for [open(-message. i say 'it seems', because - afaict - this 'relativity' to start-up in the [open(-message is never really used. when you open the patches directly from the script using the '-open' option, you don't need the [open(-message in pd it-self. and when you afterwards open other patches from the main-patch, you could easily open them with pathes relative to the patch. as far as i can see it, there is still no case, where you really need 'relative to start-up'. if i missed your point here, can you please elaborate a bit more, why Ergate _does_ need 'relative to start-up' for [open(-message? roman ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] [sqosc~]-issues
hm.. it seems that the previous mail wasn't sent here again: hello martin peach i tested your external a bit more deep on the 'good' soundcard, where i can exclude aliasing introduced by the soundcard. it turned out, that a bit of aliasing is audible in the range above 5000Hz. i think this is not tooo bad, maybe for 'pure'ists. but i had serious troubles, when loading some patches, that contain [sqosc~]. it can happen, that after loading the patch, pd is sending constantly a dc to my soundcard. even when i close pd, the dc stays on these channels, where pd was connected before over jack. to get rid of the dc, i must restart jackd again. because of that, i assume it is related to jackd (is it possible to crash jackd from pd?). i attached a test-patch. when loading that patch, jackd (and pd) get unusable for sure. my system: ubuntu dapper i386 pd-0.40.2 jackd 0.100.0 when i create a patch from scratch with [sqosc~], i have no troubles. i get the dc also, when i open the help-patch of [sqosc~]. roman ___ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] gem[new movie might crash... ...survived]
Hello, I am initial in puredata and I have small problem: I make a patch which will have to read several videos at the same time. These videos will be to pick in files/folders in Random. I use it [pix_film] with one [makesymbol]. For the moment I use a HRADIO to select the video one and I read only one of them at the same time but Pd crash landing… I do not understand. Perhaps is necessary it to close my reader before open a new video ??? if you have any suggestion, ideas thanks ! Pd says: OSCroute object version 1.05 by Matt Wright. pd: jdl Win32 raf. OSCroute Copyright ﾩ 1999 Regents of the Univ. of California. All Rights Reserved. pix_film:: avi support pix_film:: quicktime support [makesymbol] part of zexy-2.1 Copyright (l) IOhannes m zmölnig, 1999-2005 forum::für::umläute IEM compiled: Jan 17 2006 GEM: Start rendering new movie might crash... ...survived GEM: pix_film: Loaded file: C:/Program Files/pd/pD/patch/ombre_portee/dossier_1/video_1.avi with 42 frames (720x576) C: symbol dossier_1/video_1.avi new movie might crash... ...survived GEM: pix_film: Loaded file: C:/Program Files/pd/pD/patch/ombre_portee/dossier_1/video_1.avi with 42 frames (720x576) C: symbol dossier_1/video_1.avi myPatch: #N canvas 587 0 1268 722 12; #X obj -3 5 cnv 15 150 600 empty empty empty 20 12 0 14 -260818 -66577 0; #X msg 68 70; #X symbolatom 7 96 10 0 0 0 - - -; #X text 6 216 comment; #X obj 81 259 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 77 284 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1 ; #X text 10 29 object; #X text 8 66 message; #X text 6 120 comment; #X floatatom 84 145 5 0 0 0 - - -; #X obj 85 186 nbx 5 14 -1e+037 1e+037 0 0 empty empty empty 0 -6 0 10 -262144 -1 -1 0 256; #X text 5 147 number 1; #X text 3 183 number 2; #X text 7 252 bang; #X text 6 282 toggle; #N canvas 386 121 882 750 OSC-receive 0; #X obj 57 73 cnv 15 300 600 empty empty empty 20 12 0 14 -257472 -66577 0; #X floatatom 78 158 10 0 0 0 - - -; #X obj 73 195 select 1 2 3 4 5 6; #X obj 72 234 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 94 236 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 142 233 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 118 236 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 168 234 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 191 234 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 67 488 sendOSC; #X floatatom 67 515 5 0 0 0 - - -; #X msg 69 463 disconnect; #X text 60 441 ; #X floatatom 121 517 5 0 0 0 - - -; #X text 181 461 bundleDepth; #X obj 65 343 bng 15 250 50 0 empty empty connect 0 -6 0 8 -262144 -1 -1; #X obj 65 369 t b b; #X obj 155 368 bng 15 250 50 0 empty empty disconnect 0 -6 0 8 -262144 -1 -1; #X floatatom 207 474 5 0 1000 0 - - -; #X msg 152 632 0; #X obj 119 666 f; #X obj 155 666 + 1; #X obj 72 633 metro 40; #X floatatom 121 702 5 0 0 0 - - -; #X obj 67 578 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 222 651 select 400; #X msg 75 398 typetags 0; #X obj 69 116 OSCroute /ombre_portee1; #X msg 208 502 send /ombre_portee1 \$1; #X msg 60 418 connect 192.168.0.186 5000; #X msg 131 588 stop; #X obj 67 80 dumpOSC 5000; #X connect 1 0 2 0; #X connect 2 0 3 0; #X connect 2 1 4 0; #X connect 2 2 6 0; #X connect 2 3 5 0; #X connect 2 4 7 0; #X connect 2 5 8 0; #X connect 9 0 10 0; #X connect 9 1 13 0; #X connect 11 0 9 0; #X connect 15 0 16 0; #X connect 16 0 29 0; #X connect 16 1 26 0; #X connect 17 0 11 0; #X connect 18 0 28 0; #X connect 19 0 20 1; #X connect 19 0 23 0; #X connect 20 0 21 0; #X connect 20 0 23 0; #X connect 21 0 20 1; #X connect 22 0 20 0; #X connect 23 0 25 0; #X connect 23 0 18 0; #X connect 24 0 22 0; #X connect 25 0 19 0; #X connect 26 0 9 0; #X connect 27 0 1 0; #X connect 28 0 9 0; #X connect 29 0 9 0; #X connect 30 0 22 0; #X connect 31 0 27 0; #X restore -1 353 pd OSC-receive; #X obj 159 9 cnv 15 150 150 empty empty DEBUG 20 12 0 14 -258699 -66577 0; #X obj 159 333 cnv 15 120 100 empty empty GEMWIN 20 12 0 14 -261681 -66577 0; #N canvas 488 132 757 408 paramGemWin 0; #X obj 27 32 inlet; #X obj 25 66 select 1; #X obj 25 106 t b b; #X obj 22 261 gemwin; #X msg 143 168 lighting 0; #X msg 25 235 create \, 1; #X text 291 34 explication: Le loadbang envoie un bang au toggle. Il prend donc la valeur 1 ou 0 selon son etat initial. Le select vérifie si la valeur est égale à 1: * si ce n'est pas le cas \, cela signifie qu'une fenetre de visualisation est ouverte. Il bang donc à droite \, et donc passe le rendu en 0 (off) et Destroy la fenetre et tout s'arrête là \; * si c'est le cas \, cela signifie qu'il n'y pas de fenetre ouverte. Il bang donc à gauche. et ça continue: Il va ensuite dans un trigger \, une boite qui a pour effet de banger droite à gauche un a un. Il suffit de rajouter des b et on crée ainsi une chute de bang ! Le premier b va d'abord banger
[PD] gem[new movie might crash... ...survived] .... argh !
hello,Bonjour, I am initial in puredata and I have small problem: I make a patch which will have to read several videos at the same time. These videos will be to pick in files in Random. I use it [pix_film] with one [makesymbol]. For the moment I use a HRADIO to select the video one and I read only one of them at the same time but Pd crash landing before four or five playing… I do not understand. Perhaps is necessary it to close my reader before asking him to open a video news thanks for your suggestion !!! tranquillement, ths ° pd: pix_film:: avi support pix_film:: quicktime support [makesymbol] part of zexy-2.1 Copyright (l) IOhannes m zmölnig, 1999-2005 forum::für::umläute IEM compiled: Jan 17 2006 GEM: Start rendering new movie might crash... ...survived GEM: pix_film: Loaded file: dossier_1/video_1.avi with 42 frames (720x576) C: symbol dossier_1/video_1.avi new movie might crash... ...survived GEM: pix_film: Loaded file: /dossier_1/video_1.avi with 42 frames (720x576) C: symbol dossier_1/video_1.avi °° patch: #N canvas 587 0 1268 722 12; #X obj -3 5 cnv 15 150 600 empty empty empty 20 12 0 14 -260818 -66577 0; #X msg 68 70; #X symbolatom 7 96 10 0 0 0 - - -; #X text 6 216 comment; #X obj 81 259 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 77 284 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1 ; #X text 10 29 object; #X text 8 66 message; #X text 6 120 comment; #X floatatom 84 145 5 0 0 0 - - -; #X obj 85 186 nbx 5 14 -1e+037 1e+037 0 0 empty empty empty 0 -6 0 10 -262144 -1 -1 0 256; #X text 5 147 number 1; #X text 3 183 number 2; #X text 7 252 bang; #X text 6 282 toggle; #N canvas 386 121 882 750 OSC-receive 0; #X obj 57 73 cnv 15 300 600 empty empty empty 20 12 0 14 -257472 -66577 0; #X floatatom 78 158 10 0 0 0 - - -; #X obj 73 195 select 1 2 3 4 5 6; #X obj 72 234 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 94 236 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 142 233 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 118 236 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 168 234 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 191 234 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 67 488 sendOSC; #X floatatom 67 515 5 0 0 0 - - -; #X msg 69 463 disconnect; #X text 60 441 ; #X floatatom 121 517 5 0 0 0 - - -; #X text 181 461 bundleDepth; #X obj 65 343 bng 15 250 50 0 empty empty connect 0 -6 0 8 -262144 -1 -1; #X obj 65 369 t b b; #X obj 155 368 bng 15 250 50 0 empty empty disconnect 0 -6 0 8 -262144 -1 -1; #X floatatom 207 474 5 0 1000 0 - - -; #X msg 152 632 0; #X obj 119 666 f; #X obj 155 666 + 1; #X obj 72 633 metro 40; #X floatatom 121 702 5 0 0 0 - - -; #X obj 67 578 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 222 651 select 400; #X msg 75 398 typetags 0; #X obj 69 116 OSCroute /ombre_portee1; #X msg 208 502 send /ombre_portee1 \$1; #X msg 60 418 connect 192.168.0.186 5000; #X msg 131 588 stop; #X obj 67 80 dumpOSC 5000; #X connect 1 0 2 0; #X connect 2 0 3 0; #X connect 2 1 4 0; #X connect 2 2 6 0; #X connect 2 3 5 0; #X connect 2 4 7 0; #X connect 2 5 8 0; #X connect 9 0 10 0; #X connect 9 1 13 0; #X connect 11 0 9 0; #X connect 15 0 16 0; #X connect 16 0 29 0; #X connect 16 1 26 0; #X connect 17 0 11 0; #X connect 18 0 28 0; #X connect 19 0 20 1; #X connect 19 0 23 0; #X connect 20 0 21 0; #X connect 20 0 23 0; #X connect 21 0 20 1; #X connect 22 0 20 0; #X connect 23 0 25 0; #X connect 23 0 18 0; #X connect 24 0 22 0; #X connect 25 0 19 0; #X connect 26 0 9 0; #X connect 27 0 1 0; #X connect 28 0 9 0; #X connect 29 0 9 0; #X connect 30 0 22 0; #X connect 31 0 27 0; #X restore -1 353 pd OSC-receive; #X obj 159 9 cnv 15 150 150 empty empty DEBUG 20 12 0 14 -258699 -66577 0; #X obj 159 333 cnv 15 120 100 empty empty GEMWIN 20 12 0 14 -261681 -66577 0; #N canvas 488 132 757 408 paramGemWin 0; #X obj 27 32 inlet; #X obj 25 66 select 1; #X obj 25 106 t b b; #X obj 22 261 gemwin; #X msg 143 168 lighting 0; #X msg 25 235 create \, 1; #X text 291 34 explication: Le loadbang envoie un bang au toggle. Il prend donc la valeur 1 ou 0 selon son etat initial. Le select vérifie si la valeur est égale à 1: * si ce n'est pas le cas \, cela signifie qu'une fenetre de visualisation est ouverte. Il bang donc à droite \, et donc passe le rendu en 0 (off) et Destroy la fenetre et tout s'arrête là \; * si c'est le cas \, cela signifie qu'il n'y pas de fenetre ouverte. Il bang donc à gauche. et ça continue: Il va ensuite dans un trigger \, une boite qui a pour effet de banger droite à gauche un a un. Il suffit de rajouter des b et on crée ainsi une chute de bang ! Le premier b va d'abord banger en même temps les messages buffer 1 \, lighting 0 et dimen 320 240 qui
Re: [PD] [sqosc~]-issues
and forgot the attachment this time. no day without that. On Sun, 2007-03-25 at 20:42 +0200, Roman Haefeli wrote: hm.. it seems that the previous mail wasn't sent here again: hello martin peach i tested your external a bit more deep on the 'good' soundcard, where i can exclude aliasing introduced by the soundcard. it turned out, that a bit of aliasing is audible in the range above 5000Hz. i think this is not tooo bad, maybe for 'pure'ists. but i had serious troubles, when loading some patches, that contain [sqosc~]. it can happen, that after loading the patch, pd is sending constantly a dc to my soundcard. even when i close pd, the dc stays on these channels, where pd was connected before over jack. to get rid of the dc, i must restart jackd again. because of that, i assume it is related to jackd (is it possible to crash jackd from pd?). i attached a test-patch. when loading that patch, jackd (and pd) get unusable for sure. my system: ubuntu dapper i386 pd-0.40.2 jackd 0.100.0 when i create a patch from scratch with [sqosc~], i have no troubles. i get the dc also, when i open the help-patch of [sqosc~]. roman ___ Der frhe Vogel fngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list #N canvas 199 183 633 300 10; #X obj 54 134 sqosc~ 300 0.5 15000; #X obj 55 244 dac~; #X obj 54 179 *~; #X obj 146 215 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -262144 -1 -1 6400 1; #X obj 143 235 pow 2; #X obj 56 38 hsl 128 15 20 15000 1 0 empty empty empty -2 -8 0 10 -262144 -1 -1 0 1; #X obj 53 102 line~; #X obj 143 278 line~; #X obj 143 256 pack f 50; #X obj 53 79 pack f 100; #X obj 163 98 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -262144 -1 -1 6700 1; #X obj 226 161 line~; #X obj 226 139 pack f 50; #X obj 350 130 sqosc~ 300 0.5 15000; #X obj 351 240 dac~; #X obj 350 175 *~; #X obj 442 211 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -262144 -1 -1 4900 1; #X obj 439 231 pow 2; #X obj 352 34 hsl 128 15 20 15000 1 0 empty empty empty -2 -8 0 10 -262144 -1 -1 5400 1; #X obj 349 98 line~; #X obj 439 274 line~; #X obj 439 252 pack f 50; #X obj 349 75 pack f 100; #X obj 459 94 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -262144 -1 -1 5200 1; #X obj 522 157 line~; #X obj 522 135 pack f 50; #X connect 0 0 2 0; #X connect 2 0 1 0; #X connect 2 0 1 1; #X connect 3 0 4 0; #X connect 4 0 8 0; #X connect 5 0 9 0; #X connect 6 0 0 0; #X connect 7 0 2 1; #X connect 8 0 7 0; #X connect 9 0 6 0; #X connect 10 0 0 2; #X connect 12 0 11 0; #X connect 13 0 15 0; #X connect 15 0 14 0; #X connect 15 0 14 1; #X connect 16 0 17 0; #X connect 17 0 21 0; #X connect 18 0 22 0; #X connect 19 0 13 0; #X connect 20 0 15 1; #X connect 21 0 20 0; #X connect 22 0 19 0; #X connect 23 0 13 2; #X connect 25 0 24 0; ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] [sqosc~]-issues
hello martin peach i tested your external a bit more deep on the 'good' soundcard, where i can exclude aliasing introduced by the soundcard. it turned out, that a bit of aliasing is audible in the range above 5000Hz. i think this is not tooo bad, maybe for 'pure'ists. but i had serious troubles, when loading some patches, that contain [sqosc~]. it can happen, that after loading the patch, pd is sending constantly a dc to my soundcard. even when i close pd, the dc stays on these channels, where pd was connected before over jack. to get rid of the dc, i must restart jackd again. because of that, i assume it is related to jackd (is it possible to crash jackd from pd?). i attached a test-patch. when loading that patch, jackd (and pd) get unusable for sure. my system: ubuntu dapper i386 pd-0.40.2 jackd 0.100.0 when i create a patch from scratch with [sqosc~], i have no troubles. i get the dc also, when i open the help-patch of [sqosc~]. roman ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] PluggoPd using Jack? (was [ot?] pd and ableton via jack)
I'm on 10.4.9 and have finally gotten a decent result for sending and recieving audio through Jack between Live and Pd. There is an excellent tutorial on this: www.zenpho.co.uk/how-to-use-jack-pd-and-live.pdf. I found that using the Audio Unit version of the Jack Insert is much more stable than the VST one. But, this kind of routing is a bit time-consuming, especially when also synching up with Midi Patchbay as well. I'm hoping that the upcoming Summer of Code will spearhead a PluggoPd that does this in a much more streamlined fashion. I just had an idea this week that a good route (for OSX only, sorry) would be to look under the hood of the Jack Audio Unit (and VST too) and the JackPilot for tips. Maybe an ambitious rewrite of the JackPilot which uses Pd for routing could be created (there is talk about how the Jack routing tables are a bit confusing, and Pd might be the perfect language to express them). If Pd could do routing in Jack, then maybe we could have a piece of the PluggoPd puzzle? ~Kyle On 3/24/07, Derek Holzer [EMAIL PROTECTED] wrote: What's the combined CPU usage of all three together? The RAM usage? Loading lots of samples in Live or PD? I've noticed that running PD with Live has a high graphical overhead on OSX. PD's GUI isn't very optimized on OSX and Ableton is simply bloated. You might try changing the way you view your samples in Live...get rid of the waveform viewer, which uses a lot of graphics resources as well. I recall now that I had this problem early on with my set that used both, and that's how I dealt with it. Last, my OSX has been 10.4 for a while now. Maybe JackOSX is better integrated with 10.4? best, d. Myo wrote: hello list, I apologize if this is too off topic, but I figured there would be many people in this same situation here that could help. I'm trying to route audio from pd and ableton live via jack on mac os x 10.3.9. pd is 0.38.4-extended, ableton is 5.2, and jack is 0.74. interface is presonus firebox. I get everything running ok, but still get pops and clicks. changing the buffer size, number of physical i/o, number of virtual i/o, closing background processes, all have no effect. both live and pd function normally without jack, so I know it has something to do with the interactions of the 3 programs. any suggestions are very welcome. thanks alot cory ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- derek holzer ::: http://www.umatic.nl ---Oblique Strategy # 10: Allow an easement (an easement is the abandonment of a stricture) ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- http://theradioproject.com http://perhapsidid.blogspot.com (()()()(()))()()())( (())(())()((( ))(__ _())(()))___ (((000)))oOO ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] munger1~ GOP [was Re: munger1~ binary for ppc]
Ico (and listy), In the meantime, here's the GOP abstraction as promised. It's for a basic stereo configuration and includes the most important controls, plus some other things I added (dry/wet, etc). Some of the functions are limited (# voices limited to 60, for example), some scaled differently (0-100 instead of 0-1) but again I just wanted to make a useful front end for it that would hopefully suit some people's needs. Feel free to include it with the software if you want to; otherwise I am planning on creating a website this afternoon/evening where I will host it along with some other GOP things I have done. Please let me know if you find any mistakes in the patch - I've been using it for a couple hours and it seems fine to me. Of course, suggestions are welcome as well. One thing - when the position is randomized with the orange toggle (on by default, as per your help patch), the hslider will have no effect (turned off with [spigot]). I don't think there are many other idiosyncrasies. I've been having all kinds of fun this afternoon making some really wild sounds, this is really great to connect in chains of objects and patches. Kevin On 3/24/07, Ivica Ico Bukvic [EMAIL PROTECTED] wrote: I'll look into this asap. Thanks for the update! Ico -Original Message- From: Kevin McCoy [mailto:[EMAIL PROTECTED] Sent: Saturday, March 24, 2007 3:33 PM To: Ivica Ico Bukvic; PD-list@iem.at Subject: Re: munger1~ binary for ppc Ico, This one won't build for me... I get the following output: klangisch:/users/kmccoy/desktop/munger1~/source kmccoy$ sudo bash /volumes/audiowork/pdcvs/pure-data/externals/grill/flext/build.sh pd gcc make -f /volumes/audiowork/pdcvs/pure- data/externals/grill/flext/buildsys/gnumake-sub.mak PLATFORM=mac RTSYS=pd COMPILER=gcc BUILDPATH=/volumes/audiowork/pdcvs/pure- data/externals/grill/flext/buildsys/ PKGINFO=package.txt BUILDCLASS=ext TARGETMODE=release TARGETTYPE=multi THREADED=1 _build_ /volumes/audiowork/pdcvs/pure- data/externals/grill/flext/buildsys/mac/gnumake-gcc-targets.inc:22: warning: overriding commands for target `pd-darwin/release-multi' /volumes/audiowork/pdcvs/pure- data/externals/grill/flext/buildsys/mac/gnumake-gcc-targets.inc:18: warning: ignoring old commands for target `pd-darwin/release-multi' mkdir -p ./ g++ -c -ffast-math -Os -ftree-vectorize -arch ppc -maltivec -faltivec -mtune=G4 -DNDEBUG -DFLEXT_THREADS -DFLEXT_SYS=2 -DPD -I pd-darwin/release-multi -I/usr/local/include/stk -I/usr/local/include/flext -I/Users/kmccoy/Desktop/pd-0.39-2/src -I/usr/local/include -I/usr/local/include/sndobj -I/usr/local/include/flext munger1~.cpp -o pd-darwin/release-multi/munger1~.opp_ppc munger1~.cpp: In member function 'void munger1::munger_alloc()': munger1~.cpp:1397: error: expression in new-declarator must have integral or enumeration type make[1]: *** [pd-darwin/release-multi/munger1~.opp_ppc] Error 1 make: *** [build-release-multi] Error 2 __ Let me know what you think, Kevin On 3/24/07, Ivica Ico Bukvic [EMAIL PROTECTED] wrote: Excellent work Kevin! Actually we have another, more cleaned-up version of the code (see attached), so if you could build that one also and then forward me the binary, then I'll include it in the next release. FWIW, there is no behavioral difference for the object but it has a cleaner implementation of some of the routines and therefore it is theoretically more stable (even though I have yet to experience any instabilities of the previous implementation). Simply replace the old cpp file with this one. Regarding the messy help file, I agree. But that's why I said in the first place that this is the Swiss-Army-knife of granular synthesis ;-) Ico -Original Message- From: Kevin McCoy [mailto:[EMAIL PROTECTED] Sent: Saturday, March 24, 2007 11:55 AM To: PD-list@iem.at; Ivica Ico Bukvic; Thomas Grill Subject: munger1~ binary for ppc Hello all, I finally got compilation of munger~ to work under OS X 10.4 on an iMac G5 against pd 0.39-2. I've attached the binary in another email to Ico, and if I recall correctly he said he would start to include it with the munger source. Of course you can email me for it as well. Thomas and Ico, what I needed to do was copy the libstk.a file to my lib... I did not know about this file because STK's documentation says nothing about what it produces when you compile it, much to the frustration of beginners like myself!! When I read Thomas' new and improved flext documentation (very easy to understand) I knew what needed to be done, and everything went very smoothly! Ico, thanks for all your work in porting this, it sounds *wonderful* and I am going to get started today on making a GOP abstraction to control it. This has been my most-wanted-external for a while now. The help patch, as was mentioned, is... well... dense and
Re: [PD] relative pathes: problems with [open(-message to pd
On Sun, Mar 25, 2007 at 07:05:59PM +0200, Roman Haefeli wrote: On Sat, 2007-03-24 at 10:14 +0800, Chris McCormick wrote: On Fri, Mar 23, 2007 at 11:20:01PM +0100, Roman Haefeli wrote: On Fri, 2007-03-23 at 10:04 +0100, Steffen wrote: On 22/03/2007, at 23.41, Roman Haefeli wrote: When opening patches by sending messages to pd, the path is relative to pd's startup-location. when loading other files (text-, audio-, it would be nice to hear more voices. does anything speak _for_ 'relative to start-up location'? Yep. If I understand your meaning correctly, 'relative to start-up location' is useful in situations where you are building an application that uses Pd at it's core. You want the patches to start hm i think i see, what you mean. whenever a set of patches and/or externals is packed together with a startup-file (bash-script for unix, bat-file for windows), it seems to make sense to specify pathes relative to the start-up location for [open(-message. i say 'it seems', because - afaict - this 'relativity' to start-up in the [open(-message is never really used. when you open the patches directly from the script using the '-open' option, you don't need the [open(-message in pd it-self. and when you afterwards open other patches from the main-patch, you could easily open them with pathes relative to the patch. as far as i can see it, there is still no case, where you really need 'relative to start-up'. if i missed your point here, can you please elaborate a bit more, why Ergate _does_ need 'relative to start-up' for [open(-message? Actually, I think you're correct. I think I can specify the relative paths from the .bat or .py launcher file with the -open flag and never have to have an open message inside Pd. After that, once the program is launched, I want the paths to all be relative to already loaded patches, not the launch location. I will do more testing next week when I have some spare time and let you know. Best, Chris. --- [EMAIL PROTECTED] http://mccormick.cx ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [sqosc~]-issues
On Sun, Mar 25, 2007 at 07:23:13PM +0200, Roman Haefeli wrote: [sqosc~]. it can happen, that after loading the patch, pd is sending constantly a dc to my soundcard. even when i close pd, the dc stays on these channels, where pd was connected before over jack. to get rid of This happens on my laptop and I am pretty sure it occurs on a hardware level (in my case). The DC is present sometimes after just playing half an mp3 file and then hitting ctrl-C, and definately happens when doing stuff in Pd sometimes. Best, Chris. --- [EMAIL PROTECTED] http://mccormick.cx ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [sqosc~]-issues
Roman Haefeli wrote: i tested your external a bit more deep on the 'good' soundcard, where i can exclude aliasing introduced by the soundcard. it turned out, that a bit of aliasing is audible in the range above 5000Hz. i think this is not tooo bad, maybe for 'pure'ists. Do you get the aliasing also with [osc~]? Martin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] python problems
Hi, I am working on a python script to access flickr images from within Pd. I got the basics working, but I also would need some help. Big thanks, if some python mighty persons could have a look at it! just look at the code and you will see what I mean. unfortunately I cannot share the flickr api key because only one application can use a key at the time. anyway, if you don't want to register at flickr and still want to help, I will send you my key off-list. find everything at http://www.parasitaere-kapazitaeten.net/Pd/pd_flickr marius. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [sqosc~]-issues
Chris McCormick wrote: On Sun, Mar 25, 2007 at 07:23:13PM +0200, Roman Haefeli wrote: [sqosc~]. it can happen, that after loading the patch, pd is sending constantly a dc to my soundcard. even when i close pd, the dc stays on these channels, where pd was connected before over jack. to get rid of This happens on my laptop and I am pretty sure it occurs on a hardware level (in my case). The DC is present sometimes after just playing half an mp3 file and then hitting ctrl-C, and definately happens when doing stuff in Pd sometimes. How can you guys tell if there's DC in the signal? I'd love to get a sound card that outputs DC! Martin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
