mpuckett at man104-1.UCSD.Edu
Fri Nov 12 05:27:25 CET 1999
(to answer Richar's earlier query, I'm running the spectral patches
on my Dell PII 300. But memory bandwidth (function of motherboard) is
also important and laptops generally underperform "desktop" machines.
As to the path business, you can invoke "pd -path \my\favorites" or
whatnot. In practice for Windows I put this in a shortcut. It would
be appropriate to have a "PDPATH" environment variable feature too although
I haven't treated this as a high priority. The best thing would
be to have a Pd installation somehow contain information about paths to
installed "dlls" and abstractions, but I haven't thought of a good, OS-
independent way to specify this... ideas?
On Fri, Nov 12, 1999 at 12:11:43AM +0000, Richard Dobson wrote:
> Following my introductory post, I am making some progress, and have got
> as far as building pd.dll under VC++ v.5, and the externs leftshift,
> rightshift and pique. I hope to have access to an ftp server at Bath
> university soon, so that I can make these available (with VC++ project
> files) for anyone interested.
> I have already encountered the problem that external dlls such as those
> mentioned are required to be in the 'current directory', which is hardly
> ideal as there can be many of these, for different projects, as
> demonstrated by the examples supplied. Such as dll is effectively a
> 'plugin', and should really be kept in a single folder for the purpose
> (could even be /pd/bin). This can be accessed via the ineluctable
> environment variable, or under Windows, idiomatically, via the registry.
> Would it be a 'big issue' to change this system to support such a single
> (after all, if an environment var is not detected, the program can still
> default to searching the working directory).
> Richard Dobson
> Test your DAW with my Soundcard Attrition Page!
> http://wkweb5.cableinet.co.uk/rwd (LU: 17th September 1999)
> CDP: http://www.bath.ac.uk/~masjpf/CDP/CDP.htm (LU: 4th November 1999)
More information about the Pd-list