Re: [PD] wierd feedback popping with pd/freebob/jack/rt
Quoting Rich E [EMAIL PROTECTED]: After more testing... With pd compiled with JACK_NUM_PORTS 256, audio runs fine at first, but if the cpu gets a big hit, like when I open a soundfont in [fluid~], the audio falls behind and I get the pops/clicks again. If I compile pd with JACK_NUM_PORTS 32, this doesn't appear to happen; [fluid~] does its thing, the gui freezes for a couple seconds, but the audio is fine afterwards. Hopefully this hints at what the problem really is. no, unfortunately this does not make sense at all. NUM_JACK_PORTS is only used for sizing arrays properly and setting the maximum possible numbers of channels Pd can use. as the default number of channels is still 2, jack should actually not notice anything about this parameter. nevertheless, i will re-think (but i really need at least 64 channels, most likely more; this was the main motivation to start writing the entire patch...) fgmads IOhannes This message was sent using IMP, the Internet Messaging Program. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
Quoting Rich E [EMAIL PROTECTED]:
Which brought me to another question; is there any way currently to do a
'cd' or 'pwd' in pd? I tried:
[pwd (
|
[shell]
but this has the same problem of openpanel and savepaned; it gives you the
path that pd was opened from.
seems to be what i would have expected...if [openpanel] thinks that
the pwd is X, why should $(pwd) think it differently.
[cd /home/full/path/to/patch (
|
[shell]
doesn't seem to do anything, and would be a workaround if it did.
it does and it has been discussed multiple times on this list:
sending a command to the [shell] will start a new process (shell), run
the command and quit. like it should be, child processes do not modify
parent processes and siblings.
you could as well do: start a new xterm; notice that you are in
${HOME}; run cd /tmp; close the xterm; start another xterm, notice
that you are still in ${HOME}
i am not sure what you would like to achieve with [pwd] or [cd]
that is: if you could manage with [pwd] and [cd], why can't you do so
with the current absolute/relative path in [openpanel]?
fmgads.
IOhannes
This message was sent using IMP, the Internet Messaging Program.
___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management -
http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
On 29/05/2008, at 4.09, Rich E wrote: Which brought me to another question; is there any way currently to do a 'cd' or 'pwd' in pd? Since your already on the external path you could use [getdir] from ggee. I tried: [pwd ( | [shell] but this has the same problem of openpanel and savepaned; it gives you the path that pd was opened from. [cd /home/full/path/to/patch ( | [shell] doesn't seem to do anything, and would be a workaround if it did. When using a [shell] object you'd really wanna run a script. Since it's a new shell that's opened each time you query it. So when you do [cd /to/som/dir(/[shell] and then after wards to [pwd(/ [shell] then you'r no longer cd'ed to /to/some/dir but get the root dir. You can make a simple shell-script that both cd and pwd and then run that script. That is if you want to use a [shell] object. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
it does and it has been discussed multiple times on this list: sending a command to the [shell] will start a new process (shell), run the command and quit. like it should be, child processes do not modify parent processes and siblings. Ah. This makes sense. i am not sure what you would like to achieve with [pwd] or [cd] that is: if you could manage with [pwd] and [cd], why can't you do so with the current absolute/relative path in [openpanel]? I was just looking for a quick hack to get my patches working that try to open up a specific directory using [openpanel]. But I guess the real solution is making [openpanel]/[savepanel] relative to the patch it they live in. I don't really know how this would work for an [openpanel]/[savepanel] within an abstraction. -rich ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] [maxmsp] Max retreat
Hi everybody, As my studio is moving to La Tourette in France which is the famous monastery designed by Le Corbussier and Xenakis, I'd like to know how much interest would be for participation to set up a Max retreat there... I'd plan it for around the last two weeks of july, but have to propose it to the organisers there and nothing is fixed, could be also in a completely different time slot/duration... These two weeks would give space for working on a personal project, in a beautiful landscape, an inspiring place and with colleagues which could help to break the creative knots. I will be giving an introduction into Max for beginners and will show my tricks to advanced Max users alike. The only requirement would be that the manual had been read, and the tutorials had been gone through once. (elsewise it would be a little waist of time...;-) It would be open to users of Pd, SC, Csound and similar tools as well, but my personal experience with these tools is not as profound as with Max... (There must be an area where I keep my spirit of being a newbie alive...) At the end we would be able to present our results to the public... If you are interested in such a retreat (at any time), please answer me off list... Stefan -- Stefan Tiedjex--- --_---|-- --(_|_ |\-|-()--- -- _|_)|-()-- --()www.ccmix.com ___ maxmsp mailing list [EMAIL PROTECTED] http://www.cycling74.com/mailman/listinfo/maxmsp ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
On Wed, 2008-05-28 at 23:57 -0700, Rich E wrote: it does and it has been discussed multiple times on this list: sending a command to the [shell] will start a new process (shell), run the command and quit. like it should be, child processes do not modify parent processes and siblings. Ah. This makes sense. i am not sure what you would like to achieve with [pwd] or [cd] that is: if you could manage with [pwd] and [cd], why can't you do so with the current absolute/relative path in [openpanel]? I was just looking for a quick hack to get my patches working that try to open up a specific directory using [openpanel]. But I guess the real solution is making [openpanel]/[savepanel] relative to the patch it they live in. I don't really know how this would work for an [openpanel]/[savepanel] within an abstraction. i agree with you, that this new feature of [openpanel] and [savepanel] is kind of bogus the way it is implemented now. in so many cases you rather would want to set a path relative to the patch instead of relative to pd start location. i personally think, that [[open][save]panel]s within abstractions should behave accordingly: path should be relative to the file location (the path that is written in the window title, when you open the window). the same goes for the 'open' message to pd: i can't think of a good reason for the actual behaviour. relative to the patch would make much more sense, IMO. i stop saying this over and over again, as soon as someone comes up with a really good explanation for the current implementation(sorry for being so strongheaded). 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
Re: [PD] [openpanel]/[savepanel] directory, [cd]
i agree with roman, but as was mentioned before, the [getdir] external is good if you need to find the directory of the current patch. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] netpd broken?
On Thu, 2008-05-29 at 19:27 +1000, Max Neupert wrote: servus roman, list, i wanted to demonstrate netpd today here in melbourne and failed. on a intel mac os x 10.5: with a fresh pd-extended 0.4xx and downloaded netpd.zip i can open _chat.pd. then when i click on creator additionally a blank patch pops up called pd cr.singletons the console spills out: netclient ... couldn't create error: inlet: expected '' but got 'connect' ... you might be able to track this down from the Find menu. error: pd-cr.singletons: no such object i can reproduce the same on my own machine os x 10.4 ppc. [netclient] is part of maxlib. afaik, it should be found in extra/maxlib. netpd/_chat.pd has a [declare] in order to add the path of the maxlib folder. if it doesn't load, either [declare] on those versions of pd-extended are broken or netclient was moved. i'll have a look at that soon. probably it is just a matter of using an appropriate [declare]. also there is a small documentation bug: it reads: START netpd - start pd and open _chat.pd - click the 'settings'-bang - set your name - click the 'save and close'-bang - talk to other netpd-people and start a session there is no 'settings-bang, it's called 'pref' and doesn't look like a bang. inside is a 'saveclose' button. suggestion: - hit the 'pref'-button to set your preferences - set your name - hit 'saveclose' yeah, thanks for the report. i am sorry, that you weren't able to use netpd. i am currently quite busy with finishing my studies. i plan to spend more time on netpd (and development) afterwards. then i would like also to fix the netpd.org site, which was sadly spammed. 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
Re: [PD] netpd broken?
Max Neupert wrote: servus roman, list, i wanted to demonstrate netpd today here in melbourne and failed. on a intel mac os x 10.5: with a fresh pd-extended 0.4xx and downloaded netpd.zip i can open _chat.pd. then when i click on creator additionally a blank patch pops up called pd cr.singletons the console spills out: netclient ... couldn't create error: inlet: expected '' but got 'connect' ... you might be able to track this down from the Find menu. error: pd-cr.singletons: no such object hi max which exact version have u tried? have u removed the ~Library/Preferences/org.puredata.pd.plist before you run the newest pd-extended? this versions have been working more or less: on intel osx 10.5 Pd-0.40.3-extended-20080222 Pd-0.40.3-extended-20080504 Pd-0.40.3-extended-20080516 Pd-extended (20080523) some problem with ~ and a new one with matrix (only working as iemmatrix/matrix). now i tried pd-netpd-osx.tar.gz from http://netpd.org/download and it worked surprisingly well. ~, matrix, t3_del all creates fine.. i suggest to try this one too. cheers eni ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] netpd broken?
servus roman, list, i wanted to demonstrate netpd today here in melbourne and failed. on a intel mac os x 10.5: with a fresh pd-extended 0.4xx and downloaded netpd.zip i can open _chat.pd. then when i click on creator additionally a blank patch pops up called pd cr.singletons the console spills out: netclient ... couldn't create error: inlet: expected '' but got 'connect' ... you might be able to track this down from the Find menu. error: pd-cr.singletons: no such object i can reproduce the same on my own machine os x 10.4 ppc. also there is a small documentation bug: it reads: START netpd - start pd and open _chat.pd - click the 'settings'-bang - set your name - click the 'save and close'-bang - talk to other netpd-people and start a session there is no 'settings-bang, it's called 'pref' and doesn't look like a bang. inside is a 'saveclose' button. suggestion: - hit the 'pref'-button to set your preferences - set your name - hit 'saveclose' ciao, max PGP.sig Description: Signierter Teil der Nachricht ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] pulse measurement using touch sensors
Hi all, does anyone have experience with measuring pulse using just hand touch sensors? Which kind of sensors are feasible, is there any special signal conditioning necessary? many thanks, gr~~~ -- Thomas Grill http://g.org smime.p7s Description: S/MIME cryptographic signature ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] netpd broken?
On Thu, 2008-05-29 at 20:42 +1000, Max Neupert wrote: Am 2008-05-29 um 19:54 schrieb Roman Haefeli: On Thu, 2008-05-29 at 19:27 +1000, Max Neupert wrote: servus roman, list, i wanted to demonstrate netpd today here in melbourne and failed. on a intel mac os x 10.5: with a fresh pd-extended 0.4xx and downloaded netpd.zip i can open _chat.pd. then when i click on creator additionally a blank patch pops up called pd cr.singletons the console spills out: netclient ... couldn't create error: inlet: expected '' but got 'connect' ... you might be able to track this down from the Find menu. error: pd-cr.singletons: no such object i can reproduce the same on my own machine os x 10.4 ppc. [netclient] is part of maxlib. afaik, it should be found in extra/maxlib. netpd/_chat.pd has a [declare] in order to add the path of the maxlib folder. if it doesn't load, either [declare] on those versions of pd-extended are broken or netclient was moved. i'll have a look at that soon. probably it is just a matter of using an appropriate [declare]. ok, with [import maxlib] i could make the netclient object. but the rest of the problem is still there: when i open the creator an empty patch pops up called pd cr.singletons and creator doesn't work properly. i think it is probably that i need to declare the include direcory.. exactly.. actually it should be [declare]d already (i checked and it is in _chat.pd). probably you could check, if it is working, by creating a subpatch somewhere in the _chat.pd patch and then trying to create [netpd-r] (or any other abstractions from netpd/includes). if it fails, then for some reason [declare -path] doesn't work on your version of pd-extended. a recent build most likely already has fixed the issue. i haven't kept track of what works in which version, but i think, with the coming release of 0.40-extended many things should be solved. 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
Re: [PD] netpd broken?
Am 2008-05-29 um 19:54 schrieb Roman Haefeli: On Thu, 2008-05-29 at 19:27 +1000, Max Neupert wrote: servus roman, list, i wanted to demonstrate netpd today here in melbourne and failed. on a intel mac os x 10.5: with a fresh pd-extended 0.4xx and downloaded netpd.zip i can open _chat.pd. then when i click on creator additionally a blank patch pops up called pd cr.singletons the console spills out: netclient ... couldn't create error: inlet: expected '' but got 'connect' ... you might be able to track this down from the Find menu. error: pd-cr.singletons: no such object i can reproduce the same on my own machine os x 10.4 ppc. [netclient] is part of maxlib. afaik, it should be found in extra/maxlib. netpd/_chat.pd has a [declare] in order to add the path of the maxlib folder. if it doesn't load, either [declare] on those versions of pd-extended are broken or netclient was moved. i'll have a look at that soon. probably it is just a matter of using an appropriate [declare]. ok, with [import maxlib] i could make the netclient object. but the rest of the problem is still there: when i open the creator an empty patch pops up called pd cr.singletons and creator doesn't work properly. i think it is probably that i need to declare the include direcory.. i'll give it a try and report my findings. roman, i don't wanna distract you --- good luck with your presentation! it's not so urgent. winterly greetings from australia max PGP.sig Description: Signierter Teil der Nachricht ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] netpd broken?
Hi Max, Coincidently i tried this last night (or night before) and got the exact same error - pd cr.singletons. Actually i think there was a hyphen in the error so it was pd-cr.singletons The error occurred using the latest autobuild 2008-05-28 for mac intel. I then got an older build i was using prior to this (2008-05-24) and everything worked fine - no error. did something change in the autobuild maybe between 05-24 and 05-28 maybe that would give an error like this? Also all patches loaded into 'creator' were broken and gave a simalar error for me... mark --- Max Neupert [EMAIL PROTECTED] wrote: Am 2008-05-29 um 19:54 schrieb Roman Haefeli: On Thu, 2008-05-29 at 19:27 +1000, Max Neupert wrote: servus roman, list, i wanted to demonstrate netpd today here in melbourne and failed. on a intel mac os x 10.5: with a fresh pd-extended 0.4xx and downloaded netpd.zip i can open _chat.pd. then when i click on creator additionally a blank patch pops up called pd cr.singletons the console spills out: netclient ... couldn't create error: inlet: expected '' but got 'connect' ... you might be able to track this down from the Find menu. error: pd-cr.singletons: no such object i can reproduce the same on my own machine os x 10.4 ppc. [netclient] is part of maxlib. afaik, it should be found in extra/maxlib. netpd/_chat.pd has a [declare] in order to add the path of the maxlib folder. if it doesn't load, either [declare] on those versions of pd-extended are broken or netclient was moved. i'll have a look at that soon. probably it is just a matter of using an appropriate [declare]. ok, with [import maxlib] i could make the netclient object. but the rest of the problem is still there: when i open the creator an empty patch pops up called pd cr.singletons and creator doesn't work properly. i think it is probably that i need to declare the include direcory.. i'll give it a try and report my findings. roman, i don't wanna distract you --- good luck with your presentation! it's not so urgent. winterly greetings from australia max ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list mark edward grimm | m.f.a | ed.m syracuse u. | vpa foundations | timearts adjunct | new media consultant megrimm.net | socialmediagroup.org .com [EMAIL PROTECTED] | 315.378.2136 ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
On May 29, 2008, at 10:04 AM, Roman Haefeli wrote: On Wed, 2008-05-28 at 23:57 -0700, Rich E wrote: it does and it has been discussed multiple times on this list: sending a command to the [shell] will start a new process (shell), run the command and quit. like it should be, child processes do not modify parent processes and siblings. Ah. This makes sense. i am not sure what you would like to achieve with [pwd] or [cd] that is: if you could manage with [pwd] and [cd], why can't you do so with the current absolute/relative path in [openpanel]? I was just looking for a quick hack to get my patches working that try to open up a specific directory using [openpanel]. But I guess the real solution is making [openpanel]/[savepanel] relative to the patch it they live in. I don't really know how this would work for an [openpanel]/[savepanel] within an abstraction. i agree with you, that this new feature of [openpanel] and [savepanel] is kind of bogus the way it is implemented now. in so many cases you rather would want to set a path relative to the patch instead of relative to pd start location. i personally think, that [[open][save]panel]s within abstractions should behave accordingly: path should be relative to the file location (the path that is written in the window title, when you open the window). the same goes for the 'open' message to pd: i can't think of a good reason for the actual behaviour. relative to the patch would make much more sense, IMO. i stop saying this over and over again, as soon as someone comes up with a really good explanation for the current implementation(sorry for being so strongheaded). I also think the default should be relative to the patch. I am not quite sure now to handle abstractions, that's worth discussing more. I don't have time to work on it now, but if someone posts a bug in the tracker (or feature request, if you think that's better), I'll try my hand at it later. It's always useful to include a link to web archive to related discussions like this in the bug tracker. On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? .hc 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 http://at.or.at/hans/ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
Hans-Christoph Steiner wrote: On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? i would prefer it to be the directory where the original patch lives in. i hardly ever put any patches into my home directory (apart from ominous delme.pd's that keep popping up...:-)) fgmasdr IOhannes ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? sounds good to me. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] default Save As location (was: [openpanel]/[savepanel] directory, [cd])
On Thu, 2008-05-29 at 13:29 +0200, Hans-Christoph Steiner wrote: On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? personally, i sometimes used the fact, that pd writes patches per default to the start location by cd-ing to the directory first, before starting pd, when i knew, i am going to write a new patch. at same time i wouldn't mind, if the default directory would be ~/. this makes sense for me. 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
Re: [PD] pulse measurement using touch sensors
Thomas Grill a écrit : Hi all, does anyone have experience with measuring pulse using just hand touch sensors? Which kind of sensors are feasible, is there any special signal conditioning necessary? i have no experience, but the 1st thing i would try is to use some medical device like this : http://www.medinov.fr/images/products/pdf/Oxym%E8tre.pdf http://www.contactsecurite.fr/fr/shop-40.html (sorry link are in french) open them and make some electronic in order to get data out of the sensors. cyrille many thanks, gr~~~ -- Thomas Grill http://g.org ___ 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] pidip and nightly-builds problems
Thanks for pointing that out, I just fixed it and am re-running the build. It should be done in about 2 hours. Please test and reply back to this thread. .hc On May 29, 2008, at 3:17 AM, Ricardo Dueñas Parada wrote: Hello all, I am trying to use the library pidip in ccrma's pd-extended, but the externals are not in place, i tried to reinstall from planetccrma, and it does, but no single external is placed, in fact, nor even the pidip folder is created. It just puts the file pidip.pd_linux in the folder extra. It's weird because the help patches for pidip are in the reference path, but the objects can't be loaded. I tried to download pd-extended from nightly-builds, but the package for planetccrma6 has just 46bytes. I tracked it down and it is broken since [1]. Somebody know how can I or somebody fix this? Last questions, why the autobuild package is related to planetccrma6 when the latest from planet ccrma is for Fedora 8? and what is the difference between those packages? [1] http://autobuild.puredata.info/auto-build/2008-05-11/ Thanks, _Ricardo ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list All information should be free. - the hacker ethic ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
IOhannes m zmoelnig a écrit : Hans-Christoph Steiner wrote: On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? i would prefer it to be the directory where the original patch lives in. i hardly ever put any patches into my home directory (apart from ominous delme.pd's that keep popping up...:-)) same here. vincent fgmasdr IOhannes ___ 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] pulse measurement using touch sensors
Try this link to medical sensors. http://www.meas-spec.com/myMeas/industry/medical.asp Nick. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Lua: request for 'require'...
Frank Barknecht wrote: Do you think it would make sense to push the directory of a *.pd_lua file to the front of package.path automatically? I guess I think it would. Yes, I guess I think I might be inclined to agree. Now implemented in SVN head, tested very briefly. Untested with .pd_luax, probably needs a different mechanism there. See examples/complex* Claude -- http://claudiusmaximus.goto10.org ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] netpd broken?
On Thu, 2008-05-29 at 23:14 +1000, Max Neupert wrote: ok here my findings: after another [declare -path /Users/max/Desktop/netpd/includes] i could not make an object like [netpd-f] strange thing is: that even after adding the path to the paths- preferences of pd, then restarting pd + netpd there was still no chance to make a netpd object. and yes, the path was right. i tested it without netpd and it works there (made a folder somewhere with a patchname testerx.pd included the path to that in the paths and used it in a new file) that works. i thought the ui-work may heve broken the paths all in all but that's not the case. maybe i have some time tomorrow to give it another try. this is todays autobuild on ppc osx 10.4 m. just a little remark (you might know it already): [declare -*path] works locally in the sense, that pathes are added only for the patch, that holds the [declare]. for testing the netpd stuff, it really only works, if you try it within the _chat.pd patch. remark2 (probably even better known): when adding a [declare], save the patch, close and reopen it in order to test whether the [declare] really works. instantiating a [declare] does _not_ immediately add pathes. check, whether all the netpd stuff is really there. is there a netpd/includes/netpd-f.pd and netpd/includes/creator.pd ? if so, it is very strange, that you weren't able to create those even after adding the path to netpd/includes to your settings. i don't have any explanation for that. 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
Re: [PD] pulse measurement using touch sensors
Thomas Grill wrote: Hi all, does anyone have experience with measuring pulse using just hand touch sensors? Which kind of sensors are feasible, is there any special signal conditioning necessary? The basis of commercial pulse sensors is a just red LED and a light dependent resistor or a phototransistor. The variation in the blood flow changes the amount of red light that passes through the finger. You probably need to amplify the signal, then do further signal processing (filtering and thresholding) in pd. Martin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel] directory, [cd])
On May 29, 2008, at 1:42 PM, Roman Haefeli wrote: On Thu, 2008-05-29 at 13:29 +0200, Hans-Christoph Steiner wrote: On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? personally, i sometimes used the fact, that pd writes patches per default to the start location by cd-ing to the directory first, before starting pd, when i knew, i am going to write a new patch. at same time i wouldn't mind, if the default directory would be ~/. this makes sense for me. Sorry, I should have been clearer. The Save As location for New/ Untitled patches is set to $HOME. Save As for existing patches remains the current folder. .hc roman ___ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de Access to computers should be unlimited and total. - the hacker ethic ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pulse measurement using touch sensors
hi thomas, polar has an oem product line http://www.polarusa.com/manufacturers/products/products.asp the contact heart rate system is also for use with hand sensors. the europe devision is in switzerland and you can get quotes from [EMAIL PROTECTED] . i did not use this one specific but i heard it takes a couple of seconds to give you an output (i only used the belt and receiver system from polar, which works really well). another hand touch system i used which is really responsive and reliable is from another finnish company which is called tunturi http://www.tunturi.com/, they produce hometrainers in which they use hand touch hate rate monitors. they dont have a oem product line, so you would need to contact them to obtain some boards. all of this modules have an output which gives you the pulsrate as an TTL pulse, so you can easiliy read with a microcontroller and send it further to your machine. i collected quite some experience over the years on this topic, so if you want to know more just write me. best erich - http://randomseed.org On Thu, 29 May 2008, cyrille henry wrote: Thomas Grill a ?crit : Hi all, does anyone have experience with measuring pulse using just hand touch sensors? Which kind of sensors are feasible, is there any special signal conditioning necessary? i have no experience, but the 1st thing i would try is to use some medical device like this : http://www.medinov.fr/images/products/pdf/Oxym%E8tre.pdf http://www.contactsecurite.fr/fr/shop-40.html (sorry link are in french) open them and make some electronic in order to get data out of the sensors. cyrille many thanks, gr~~~ -- Thomas Grill http://g.org ___ 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-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] pulse measurement using touch sensors
Hello Thomas, We are using Nexus 10 (http://www.mindmedia.nl/english/nexus10.php) and Nexus 4 (http://www.mindmedia.nl/english/nexus4.php) for bio- signal acquisition in our project, currently we are implementing the PD [audio-visual engine] part of the system, we trace the signals by integrating a Python script to Mindmedia's Biotrace+ (http:// www.mindmedia.nl/english/biotrace.php) and we stream data through OSC. Skin conductance sensor with the above combination, is like a hand touch sensor available for measuring pulse. On the other hand piezo contact mic can be used as a sensor to receive pulse, but I guess it should be tested to see how much reliable output can be received though a contact mic. Koray - M.Koray Tahiroglu Media Lab,UIAH http://mlab.taik.fi/~korayt tel: +358 468956602 ( in Finland only) tel: +90 533 712 8245 On May 29, 2008, at 2:42 PM, [EMAIL PROTECTED] wrote: Message: 1 Date: Thu, 29 May 2008 12:30:38 +0200 From: Thomas Grill [EMAIL PROTECTED] Subject: [PD] pulse measurement using touch sensors To: PD List send pd-list@iem.at Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Hi all, does anyone have experience with measuring pulse using just hand touch sensors? Which kind of sensors are feasible, is there any special signal conditioning necessary? many thanks, gr~~~ -- Thomas Grill http://g.org ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
On May 29, 2008, at 4:48 PM, Martin Peach wrote: Hans-Christoph Steiner wrote: Sorry, I should have been clearer. The Save As location for New/ Untitled patches is set to $HOME. Save As for existing patches remains the current folder. I can't think of any time this would be useful. Apps that do that force me to waste my time drilling back down to the folder I'm working in. Having loose patches floating around the home directory is messy as well. What folder were you working in when you create a new patch? What if there are no other patches open? What if there are many patches open in many different folders? Before, on Mac OS X at least, it defaulted to /. I've changed that to ~, which I think is a lot more useful. Perhaps it could be like this: - if no other patches open, then ~. - if other patches are open, then use the folder of the current top window .hc Martin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
Hans-Christoph Steiner wrote: What folder were you working in when you create a new patch? What if there are no other patches open? What if there are many patches open in many different folders? I usually open pd from inside ~/pd_patches and have subdirectories in there. If I make a new patch it's often interacting with another patch already in the same folder. Before, on Mac OS X at least, it defaulted to /. I've changed that to ~, which I think is a lot more useful. Perhaps it could be like this: - if no other patches open, then ~. - if other patches are open, then use the folder of the current top window Yes, that's better, using ~ as default. And any new patch is most likely to be saved in the folder of the topmost already-open patch. And the default directory should also be a specifiable option in the preferences somewhere, not hard-coded, in the interest of total control. Martin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
Hallo, Martin Peach hat gesagt: // Martin Peach wrote: Hans-Christoph Steiner wrote: What folder were you working in when you create a new patch? What if there are no other patches open? What if there are many patches open in many different folders? I usually open pd from inside ~/pd_patches and have subdirectories in there. If I make a new patch it's often interacting with another patch already in the same folder. I do this as well and I think it would be *very irritating* if Pd would default to some directory different from the one I started Pd from. Btw: If I start Pd from the window manager, new patches automatically get saved to $HOME (because $HOME is the current working directory of the window manager and everything else after logging in), so there's no need to change anything on Linux. Before, on Mac OS X at least, it defaulted to /. I've changed that to ~, which I think is a lot more useful. Perhaps it could be like this: - if no other patches open, then ~. - if other patches are open, then use the folder of the current top window Yes, that's better, using ~ as default. And any new patch is most likely to be saved in the folder of the topmost already-open patch. And the default directory should also be a specifiable option in the preferences somewhere, not hard-coded, in the interest of total control. How is it decided what's the topmost patch? Ciao -- Frank Barknecht _ __footils.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
Hans-Christoph Steiner wrote: What folder were you working in when you create a new patch? What if there are no other patches open? What if there are many patches open in many different folders? Before, on Mac OS X at least, it defaulted to /. I've changed that to ~, which I think is a lot more useful. Perhaps it could be like this: - if no other patches open, then ~. - if other patches are open, then use the folder of the current top window why not do what a lot of other apps do and persistently store the last-used-directory somewhere in the config, so that next time I open Pd, Open is pointing to the same place as the last time I closed it? -- while we're talking about open and save, is it possible to have different default directories for [openpanel] vs for File-Open? (and for [savepanel] vs File-Save, come to think of it -- damian stewart | +31 659 025 782 | [EMAIL PROTECTED] frey | live art with machines | http://www.frey.co.nz ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
Damian Stewart wrote: -- while we're talking about open and save, is it possible to have different default directories for [openpanel] vs for File-Open? (and for [savepanel] vs File-Save, come to think of it In x_gui.c the functions openpanel_symbol() and savepanel_symbol() appear to use an empty path by default. These could be changed to use some other path. Martin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
On May 29, 2008, at 7:28 PM, Frank Barknecht wrote: Hallo, Martin Peach hat gesagt: // Martin Peach wrote: Hans-Christoph Steiner wrote: What folder were you working in when you create a new patch? What if there are no other patches open? What if there are many patches open in many different folders? I usually open pd from inside ~/pd_patches and have subdirectories in there. If I make a new patch it's often interacting with another patch already in the same folder. I do this as well and I think it would be *very irritating* if Pd would default to some directory different from the one I started Pd from. Btw: If I start Pd from the window manager, new patches automatically get saved to $HOME (because $HOME is the current working directory of the window manager and everything else after logging in), so there's no need to change anything on Linux. The problem here is that most people do not start Pd from the command line. With Pd-extended, it is now included in the standard free desktop menus (only tested on GNOME, should work on KDE), so I'll bet most people use that rather than the command line (I do on Ubuntu). On Window and Mac OS X, it is quite rare to start Pd from the command line. All that is a long way of saying that I don't think using the directory that Pd was launched from is a very reliable way of getting the directory that the user will most likely want. I think the combo of $HOME for new patches with no others and the directory of the topmost patch would make the most people happy. One thing to also consider is the last directory used. So maybe something like this: - $HOME when no other patch is open, and it's a new patch - directory of topmost patch when no open/save operation has been done before. - last_open_path/last_save_path once the openpanel/savepanel has been used Before, on Mac OS X at least, it defaulted to /. I've changed that to ~, which I think is a lot more useful. Perhaps it could be like this: - if no other patches open, then ~. - if other patches are open, then use the folder of the current top window Yes, that's better, using ~ as default. And any new patch is most likely to be saved in the folder of the topmost already-open patch. And the default directory should also be a specifiable option in the preferences somewhere, not hard-coded, in the interest of total control. How is it decided what's the topmost patch? By which window has focus. .hc Ciao -- Frank Barknecht _ __footils.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list Computer science is no more related to the computer than astronomy is related to the telescope. -Edsger Dykstra ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote: The problem here is that most people do not start Pd from the command line. With Pd-extended, it is now included in the standard free desktop menus (only tested on GNOME, should work on KDE), so I'll bet most people use that rather than the command line (I do on Ubuntu). The HOME directory already is the default directory on Linux with Gnome/KDE/Blackbox or whatever, as it's the working directory when starting Pd from the manager. No need for any changes AFAIK. I'm the wrong person to comment on MS-Windows or Mac, as I don't use these and don't care even the teeny-tiniest bit about what happens to Pd on these systems, but please leave it on Linux as it is the standard here. All other apps like Vim, Emacs, Gimp, Firefox use the `pwd` as default and I can't see why Pd should behave differently. If you want to confirm this yourself, try the following with the gimp: $ cd /tmp $ gimp Then make a new file, select Save and it will give you /tmp as first directory choice. Ciao -- Frank Barknecht _ __footils.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote: How is it decided what's the topmost patch? By which window has focus. Missed this: But the focus is the window about to be saved, isn't it? Ciao -- Frank Barknecht _ __footils.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] ever want to disable Ctrl-W?
Or perhaps any other key, I was just messing around, and make a quick patch, in case anyone is interested: no-close.pd Description: Binary data .hc Free software means you control what your computer does. Non-free software means someone else controls that, and to some extent controls you. - Richard M. Stallman ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
When I first posted about this, it was about the recently new ability to do this: [symbol somedir( | [openpanel] But this only works if somedir is at $HOME/somedir on linux and /usr/blahblah/pdir/somedir on mac. So if my directly layout is something like ~/patches/somedir, I have to explicitly write in the message to [openpanel] /home/myname/patches/somedir. This will only work on my directly layout, so if it is a patch I'm going to share, I cannot use this new feature (might I add I really like the feature). I was only suggesting that [openpanel]/[savepanel]'s symbol argument has the patch's current directory appended to it, unless the ~ sign is used for home, or a full path is given. I think, as Martin suggested, this is all handled internally with canvas_getdir() and open_via_path(). Regarding the normal operation of [openpanel]/[savepanel], i.e. sending it a bang, I think it would be nice if the last directory navigated to is remembered, else the $HOME. -rich On Thu, May 29, 2008 at 2:26 PM, Frank Barknecht [EMAIL PROTECTED] wrote: Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote: The problem here is that most people do not start Pd from the command line. With Pd-extended, it is now included in the standard free desktop menus (only tested on GNOME, should work on KDE), so I'll bet most people use that rather than the command line (I do on Ubuntu). The HOME directory already is the default directory on Linux with Gnome/KDE/Blackbox or whatever, as it's the working directory when starting Pd from the manager. No need for any changes AFAIK. I'm the wrong person to comment on MS-Windows or Mac, as I don't use these and don't care even the teeny-tiniest bit about what happens to Pd on these systems, but please leave it on Linux as it is the standard here. All other apps like Vim, Emacs, Gimp, Firefox use the `pwd` as default and I can't see why Pd should behave differently. If you want to confirm this yourself, try the following with the gimp: $ cd /tmp $ gimp Then make a new file, select Save and it will give you /tmp as first directory choice. Ciao -- Frank Barknecht _ __footils.org__ ___ 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] default Save As location (was: [openpanel]/[savepanel]directory, [cd])
Rich E wrote: When I first posted about this, it was about the recently new ability to do this: [symbol somedir( | [openpanel] I did not know this yet, cool! But this only works if somedir is at $HOME/somedir on linux and /usr/blahblah/pdir/somedir on mac. So if my directly layout is something like ~/patches/somedir, I have to explicitly write in the message to [openpanel] /home/myname/patches/somedir. This will only work on my directly layout, so if it is a patch I'm going to share, I cannot use this new feature (might I add I really like the feature). I was only suggesting that [openpanel]/[savepanel]'s symbol argument has the patch's current directory appended to it, unless the ~ sign is used for home, or a full path is given. I think, as Martin suggested, this is all handled internally with canvas_getdir() and open_via_path(). Regarding the normal operation of [openpanel]/[savepanel], i.e. sending it a bang, I think it would be nice if the last directory navigated to is remembered, else the $HOME. I think it is quite easy to distinguish between what is a local path and what is an absolute path. these features that you are talking about would make life much easier! I hope they get added. marius. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
