[PD] Can you close source of Pd patches (for commercial development)?
mviljamaa at kapsi.fi
Sat May 7 19:36:46 CEST 2016
What about using Pd as a C/C++ library and writing the patch that way? Or perhaps LibPd?
Would this allow the patch to be compiled as a stand-alone program? Yes?
The easiest would be if there was a way to open a patch in binary form in Pd.
What I’ve been envisioning would be to create “modules” for Pd similar to Reaktor’s Blocks that would
allow for a more high-level patching and usage of Pd. And it could motivate developers to develop patches
in a more standardized “blocks” form, rather than as unstandardised patches.
Reason, I’ve been wanting to see modular synthesis properly realised in Pd. But I wouldn’t want to
spend effort on developing modules that I cannot profit from, since I could do that using some other platform.
> On 07 May 2016, at 20:29, Miller Puckette <msp at ucsd.edu> wrote:
> You'd have to modify Pd if you want to be able to run patches and
> keep it a secret how the patch works. I don't think people often feel the
> need to do that but it wouldn't be hard to do.
> On Sat, May 07, 2016 at 08:14:05PM +0300, Matti Viljamaa wrote:
>> But how do you close and distribute a Pd patch so it’s not viewable? Can you open a Pd patch distributed as binary?
>> I only found this:
>> How do I compile a Pd-patch to run as a stand-alone application?
>> https://puredata.info/docs/faq/standalone <https://puredata.info/docs/faq/standalone>
More information about the Pd-list