i'm talking about pd ext 0.39.3 built windows version from sourceforge. (Pd-0.39.3-extended.exe) included there's vasp.dll (it says version 0.1.4pre but the version at your link has got a different filesize and says the same) in the package at pd\extra; there's all vasp functions explained in pd\doc\5.reference\vasp in separate .pd files; there are some examples at pd\doc\examples\vasp\pd-ex and there are vasp's release notes at pd\doc\manuals\vasp. but as i said, one folder is missing. what do you mean by "there is no vasp binary at all, because it is flext based"? i don't understand. you mean there's just the source code for it? is then there also only the source code for the modules above?
should i do a bug report? regarding doing it on my own: i'm no programmer yet and i don't want to destroy things (that i still need ;-)
thanks fabb (without re :-)
On Thu, May 1, 2008 at 4:27 PM, marius schebella marius.schebella@gmail.com wrote:
hi fabbre, I am not sure which pd-ext version you mean. but for the autobuilds there is no vasp binary at all, because it is flext based. you can get the latest releases at http://grrrr.org/ext/beta/pd (I am not sure why they are not linked on the main vasp page). I think it should be possible to get flext based externals working in autobuilds, too, it is really mainly a problem of someone having the time to do the work. for the next pd-extended release I could help getting all the vasp files together. marius.
Langsam Wieder wrote:
what do you mean by "there is no vasp binary at all, because it is flext based"?
that was only related to the nightly autobuilds http://autobuild.puredata.info that compile always the latest pd version during night from the latest source code. and some things are not included there, because it is not a real release, only a test version (check it out).
should i do a bug report? regarding doing it on my own: i'm no programmer yet and i don't want to destroy things (that i still need ;-)
you don't need to be a programmer for it, I think it only needs copying the folder you mentioned into the correct directory. so if you send a bug report then someone with svn access could add it easily. marius.