hello,
How can I compile a patch into an audio unit independent of puredata?
Le 7 Août 2005 17:54, alexandre matheson a écrit :
How can I compile a patch into an audio unit independent of puredata?
You can't compile a patch, but if you want PD to act as an audio black box, try using it with "jack" for audio i/o and with the "nogui" option to hide the graphic interface. -- Marc
what about j sarlo's pdvst http://crca.ucsd.edu/~jsarlo/pdvst/
never used it but seems like a great idea.
On 8/8/05, Marc Lavallée marc@hacklava.net wrote:
Le 7 Août 2005 17:54, alexandre matheson a écrit:
How can I compile a patch into an audio unit independent of puredata?
You can't compile a patch, but if you want PD to act as an audio black box, try using it with "jack" for audio i/o and with the "nogui" option to hide the graphic interface. -- Marc
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
hello,
On Dimanche, août 7, 2005, at 08:36 pm, we are wrote:
what about j sarlo's pdvst http://crca.ucsd.edu/~jsarlo/pdvst/
I would really like to be using pdvst but its only for windows, how unfortunate for me ;-(
never used it but seems like a great idea.
On 8/8/05, Marc Lavallée marc@hacklava.net wrote:
Le 7 Août 2005 17:54, alexandre matheson a écrit:
How can I compile a patch into an audio unit independent of puredata?
You can't compile a patch, but if you want PD to act as an audio black box, try using it with "jack" for audio i/o and with the "nogui" option to hide the graphic interface.
hmmm... a good workaround, but the reason I would like to turn it into an au is so I can pass some patches to non-pd using friends. Is there not ways to turn a patch into a .app by taking what it needs from pure data so that it can run standalone, I have seen a patch like this called "tree"
Maybe this is to big a project for somebody at my level.
-- Marc
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
alex
alexandre matheson wrote:
I would like to turn it into an au is so I can pass some patches to non-pd using friends. Is there not ways to turn a patch into a .app by taking what it needs from pure data so that it can run standalone,
If PD is free, what is preventing your friends from installing it to run your patch?
There have been a few threads about making a "projector", an "executable" or a "stand alone" PD patch on the list before. Have a search in the archives with these keywords to read all the details. But the essence of the matter is this: projectors, stand-alones and executables are usually tricks that commercial software companies use to allow people to share things in a very limited way without giving away free copies of the program. Since PD is free, this seems very unneccessary. On top of that, making a closed PD patch feels like a violation of the open spirit of the community. But maybe not everyone else feels that way...
Past suggestions have included bundling a PD installation in an OS-specific folder for distribution with the patches, or at the most extreme making a bootable Linux CD set up to run PD with the patch. Both methods remain transparent, however. Then the construction of the patch remains available to anyone who wants to see it.
best, d.
hi,
On Jeudi, août 11, 2005, at 05:38 pm, derek holzer wrote:
alexandre matheson wrote:
I would like to turn it into an au is so I can pass some patches to non-pd using friends. Is there not ways to turn a patch into a .app by taking what it needs from pure data so that it can run standalone,
If PD is free, what is preventing your friends from installing it to run your patch?
There have been a few threads about making a "projector", an "executable" or a "stand alone" PD patch on the list before. Have a search in the archives with these keywords to read all the details. But the essence of the matter is this: projectors, stand-alones and executables are usually tricks that commercial software companies use to allow people to share things in a very limited way without giving away free copies of the program. Since PD is free, this seems very unneccessary. On top of that, making a closed PD patch feels like a violation of the open spirit of the community. But maybe not everyone else feels that way...
Past suggestions have included bundling a PD installation in an OS-specific folder for distribution with the patches, or at the most extreme making a bootable Linux CD set up to run PD with the patch. Both methods remain transparent, however. Then the construction of the patch remains available to anyone who wants to see it.
all good points, Initially I was just looking for a simple way to pass a friend something they could pull up as a pluggin in logic. Making a .app is completely redundant for me. Not to mention that it would be wrong to just grab pieces of pd without permission, no?
alex
best, d.
-- derek holzer ::: http://www.umatic.nl ---Oblique Strategy # 165: "Use an old idea"
alexandre matheson wrote:
Not to mention that it would be wrong to just grab pieces of pd without permission, no?
The license that Pd is released under gives you permission to take all or part of it and use/modify/distribute it (under certain conditions).
See pd/LICENSE.txt for full details.
Claude
-
alexandre matheson -
ClaudiusMaximus -
derek holzer -
Marc Lavallée -
we are