[PD] (netpd)U(Pd-extended), Pd-ext bug-tracker (was Re: elitism, software and academia)

[Enrique Erne]

On Jun 9, 2007, at 4:11 PM, Kyle Klipowicz wrote:

> On that tip, I'm curious if there is a tarball of all the current
> netpd instrument/effects/utility abstractions,

there is no tarball. and if there would be it would be not up to date
within short time.

>  of will I have to go to
> each description page on the netpd site?

i wouldn't do that because there are not all instruments available.
and maybe it's not the newest version. somebody could make an
archive of his current netpd directory and send it to you.

or we check the idea of adding only netpd to the cvs
and so everybody can get it online.

if people start writing patches using pd-extended and all it's
externals we will probably have many new external related and
os specific bugs and patches that wont work on everybody's system.

> The largest challenge with this idea is the extra machinery for
> synchronization between netpd elements.

why do you want a extra machinery .. there is synchronization
from a patch called master.pd (global metro)

>  However, this machinery is
> ideal for implementing a preset system for the instruments, so that
> could be very nice.

there has been a state saving system for a long time and on it
a preset administrator (which i just fixed yesterday)

> ~Kyle

ciao
eni


>
> On 6/9/07, Kyle Klipowicz <kyleklip at gmail.com> wrote:
>> Yes, what I am talking about is not to add 'netpd the whole
>> application' to Pd-extended, but merely the modules, which are
>> functional and quite useful on their own.
>>
>> These seem to be the best developed set of GOP objects that would be
>> immediately understandable to those coming from the
>> Reason/Reaktor/AudioMulch/whatever crowd, and would serve as a nice
>> entry point to Pd even when removed from the context of internet
>> collaborative performance (which is still a WAY cool concept, Roman!).
>>
>> In the next week or so, I will start tinkering with some patches to
>> see how well they integrate in my local Pd-extended distribution. If
>> the go ahead is there from the netpd community, I'll try to write up a
>> quick proposal to include these in the Pd-extended distro. Roman, how
>> would I go about getting permission to distribute the patches in this
>> way?
>>
>> If this were to happen, would that require that the patches be
>> maintained in cvs separate from the netpd application page? I'm pretty
>> green at this sort of thing, but it seems like something that would be
>> a great benefit, and which I might actually be able to help with. So
>> please, feedback anyone?
>>
>> ~Kyle
>>
>> On 6/9/07, Enrique Erne <pd at mild.ch> wrote:
>>>>> I am now wondering something: why haven't these awesomely 
>>>>> functional
>>>>> netpd object been included as abstractions within Pd-extended?!?!
>>>
>>> on one hand i would like to see netpd included in pd-extended, but 
>>> not
>>> on cost of the current package. it is important that netpd and all
>>> patches work on linux, osx and windows.
>>>
>>> if people start to write netpd patches with pd-extended and use many
>>> externals i'm afraid we are going to have instrument that work on
>>> one os and maybe not on the other. netpd would also be a great
>>> system to find os-specific bugs :-)
>>>
>>>> Yes, would be nice - someone would have to integrate them to
>>>> pd-extended
>>>> (using [import] and etc.) ...
>>>
>>> are you talking about basic netpd or netpd & all the instruments...
>>>
>>> basic netpd is written by Roman Haefeli
>>> all the instruments have at least 10 different authors.
>>>
>>>
>>
>>
>> --
>> -----
>> ------------
>>     ----     -----
>> ---- -------- - ------
>> http://perhapsidid.wordpress.com
>>
>
>
> -- 
> -----
> ------------
>     ----     -----
> ---- -------- - ------
> http://perhapsidid.wordpress.com
>
> _______________________________________________
> PD-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> http://lists.puredata.info/listinfo/pd-list
>