On 6/18/07, Roman Haefeli [EMAIL PROTECTED] wrote:
luckily just yesterday, i had a (very simple) idea, for which i waited
for years:
instead of opening the netpd-patches with the (for me) inconvenient
'open'-message, i want to load them as abstractions. this has the BIG
advantage, that i can
On Tue, 2007-06-19 at 11:47 -0500, Kyle Klipowicz wrote:
On 6/18/07, Roman Haefeli [EMAIL PROTECTED] wrote:
luckily just yesterday, i had a (very simple) idea, for which i waited
for years:
instead of opening the netpd-patches with the (for me) inconvenient
'open'-message, i want to load
On Jun 14, 2007, at 1:07 PM, Roman Haefeli wrote:
On Tue, 2007-06-12 at 21:46 -0400, Hans-Christoph Steiner wrote:
It would very nice if it was just plug and play. It would not be
that hard to do it. I think you could spend a day on it and have it
working smoothly. It would be very
On Mon, 2007-06-18 at 19:05 -0400, Hans-Christoph Steiner wrote:
On Jun 14, 2007, at 1:07 PM, Roman Haefeli wrote:
On Tue, 2007-06-12 at 21:46 -0400, Hans-Christoph Steiner wrote:
It would very nice if it was just plug and play. It would not be
that hard to do it. I think you could
On Jun 14, 2007, at 3:08 PM, Patco wrote:
does getdir work without [import]?
Why wouldn't it work without [import]? I've got it working so fine
without the help of any ohter stuff than vanilla.
Pk
ah i am not sure about pd-extended's flatspace. when to use
[ggee/getdir], [import ggee],
Hallo!
ah i am not sure about pd-extended's flatspace. when to use
[ggee/getdir], [import ggee], -lib ggee, or just [getdir]
If getdir is in ggee, then you can use
[ggee/getdir]
or
[import ggee] and [getdir]
or
-lib ggee and [getdir]
LG
Georg
___
On Thu, Jun 14, 2007 at 11:17:57AM +0200, Roman Haefeli wrote:
the question is: how should they be included? should they be included as
they are now, with the gui and their dependency on the netpd-framework?
or would it make more sense to strip everything off to get a working
subset of
Hallo,
Chris McCormick hat gesagt: // Chris McCormick wrote:
One thing that would be cool for us to come up with is some way to
abstract the core, and gui of abstractions separately in such a way that
they could be used in multiple different state saving/communication paradigms.
For
Hello,
Frank Barknecht a écrit :
All that would be necessary are a clean and documented
interfaces for the DSP abstractions.
Yes exactly.
Things like state saving, GUIs or
network control then could easily be built as wrapper abstractions.
It might be necessary to have a bridge
On Fri, 2007-06-08 at 16:07 -0500, Kyle Klipowicz wrote:
You can submit edited patches to the bug tracker on the sourceforge
page [http://sourceforge.net/tracker/?group_id=55736atid=478070
direct link].
I am now wondering something: why haven't these awesomely functional
netpd object been
Hallo Roman!
i'd rather do not include the abstractions/patches myself and i'd rather
do not make the decision on how they should be included. but i'd be
willing to deliver stripped off abstractions with helpfiles from my own
netpd-patches, so someone else could could include/organize them in
On Sat, 2007-06-09 at 08:57 -0500, Kyle Klipowicz 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.
yeah, that is what i think as well.
These seem to be the best
On Sat, 2007-06-09 at 09:11 -0500, Kyle Klipowicz wrote:
On that tip, I'm curious if there is a tarball of all the current
netpd instrument/effects/utility abstractions, of will I have to go to
each description page on the netpd site?
yes, i think so (unfortunately). it would be surely very
Roman Haefeli wrote:
On Sat, 2007-06-09 at 09:11 -0500, Kyle Klipowicz wrote:
On that tip, I'm curious if there is a tarball of all the current
netpd instrument/effects/utility abstractions, of will I have to go to
each description page on the netpd site?
yes, i think so (unfortunately). it
On Sun, 2007-06-10 at 11:45 +0200, Enrique Erne wrote:
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)
On Mon, 2007-06-11 at 00:40 -0500, Kyle Klipowicz wrote:
Rather than reinvent the wheel, why not take the fruits of the netpd
community and make them accessible to users who might just want a
wikkid bassline or GOP mixer abstraction?
yeah, absolutely. as often, it is a question of someone
On Tue, 2007-06-12 at 15:17 +0200, Georg Holzmann wrote:
Hallo!
maybe some chosen patches could be converted to work standalone,
but it would be lots of work ... and introduce new bugs.
some systems like the fx-library system for the mixer were
specially developed that different users
On Tue, 2007-06-12 at 21:42 -0400, Hans-Christoph Steiner wrote:
netpd has been changing a lot over the last years, and things that
change a lot don't work well in Pd-extended. You get version
troubles, etc.
maybe i am blind to see the obvious solution, but the main problem i see
in
On Tue, 2007-06-12 at 21:46 -0400, Hans-Christoph Steiner wrote:
On Jun 9, 2007, at 5:45 AM, Enrique Erne 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
On Tue, 2007-06-12 at 21:46 -0400, Hans-Christoph Steiner wrote:
Alex Quessy and I tried to run the latest version on netpd working
for a network jam last Sunday, we both failed. He got further than
me, he got some sounds out, but neither got it all working. Both of
us know quite a
On Wed, 2007-06-13 at 11:21 -0400, Hans-Christoph Steiner wrote:
I think it should not be too hard to make netpd double-clickable with
no extra setup at all (setting .pdrc, etc.) without embedding it into
it's own Pd install.
but this works smoothly and i think it is the only option, so
The helpfile aspect would be very much appreciated!
I think that modular is better so that people can reuse netpd elements
in their own patches. Of course, being able to use the sequencers and
mixer + fx would be the primary Reason (forgive the semi-pun) for
newbies to adopt the objects.
~Kyle
On Tue, 2007-06-12 at 21:46 -0400, Hans-Christoph Steiner wrote:
It would very nice if it was just plug and play. It would not be
that hard to do it. I think you could spend a day on it and have it
working smoothly. It would be very worthwhile, but I think you have
already spent far
Good idea. There could be a script called by cron to automatically
tarball this dir every week.
~Kyle
On 6/14/07, moritz [EMAIL PROTECTED] wrote:
Roman Haefeli wrote:
On Sat, 2007-06-09 at 09:11 -0500, Kyle Klipowicz wrote:
On that tip, I'm curious if there is a tarball of all the current
Great! This seems easy enough. I think that this is the simplest
solution for now anyway. Eventually being able to separately use
modules and even create alternate GUIs for them would be nice too. Of
course, I think that the GUIs in netpd are one of the most attractive
aspects for new users (and
Hello Eni,
Enrique Erne a écrit :
does getdir work without
[import]?
regards
eni
Why wouldn't it work without [import]? I've got it working so fine
without the help of any ohter stuff than vanilla.
Pk
___
PD-list@iem.at mailing list
i'm glad you like it. was it hard to install?
if i'd maintain it into cvs first thing i would do is add plain/basic
netpd.
then i would add some patches to the 2 directories netpd/patches and
netpd/abs.
btw. if you disconnect the chat from the netpd server everything works
locally.
it opens a
hello hans
On Jun 13, 2007, at 3:46 AM, Hans-Christoph Steiner wrote:
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
On Jun 13, 2007, at 4:10 AM, Enrique Erne wrote:
hello hans
On Jun 13, 2007, at 3:46 AM, Hans-Christoph Steiner wrote:
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
Hallo!
maybe some chosen patches could be converted to work standalone,
but it would be lots of work ... and introduce new bugs.
some systems like the fx-library system for the mixer were
specially developed that different users can develop effects
without touching the mixer itself. somehow
After playing around a little bit with netpd over the past few days, I
think that it would be possible to write a dummy _controller.pd that
would allow a user to have the netpd experience without an internet
connection. Maybe this could be included with a pd-extended netpd
library (as well as the
On Jun 9, 2007, at 5:45 AM, Enrique Erne 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
Hallo!
I am not meaning that people will add to netpd from Pd-extended.
Rather, it would be neat to 'steal' the great functional modules that
are in netpd and use them as standalone modules for rapid building of
non-netpd patches. Say, if a person has been using Reason for a few
years, but
hi Georg
On Jun 11, 2007, at 9:25 AM, Georg Holzmann wrote:
I am not meaning that people will add to netpd from Pd-extended.
Rather, it would be neat to 'steal' the great functional modules that
are in netpd and use them as standalone modules for rapid building of
non-netpd patches. Say, if
good morning Kyle
i would only add the basic netpd to Pd-extended without any
instrument, so that any user can get the newest version of the
instruments through creator without maintaining all the instruments
in cvs.
the netpd-instruments are using some basic netpd-abstractions
for broadcasting,
Hallo,
Enrique Erne hat gesagt: // Enrique Erne wrote:
i'm pretty green about cvs. over the pasat 3 years there have been
at least 10 different people writing instruments for netpd.
how is this done in other projects... like pixeltango or rradical
are they maintained in cvs by one person or
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
Hallo!
Yes, would be nice - someone would have to integrate them to pd-extended
(using [import] and etc.) ...
Everyone could integreate them to her/his own pd-extended using a
simple -path flatspace, as AFAIK everything netpd uses is already
there and people not using pd-extended wouldn't
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
On that tip, I'm curious if there is a tarball of all the current
netpd instrument/effects/utility abstractions, of will I have to go to
each description page on the netpd site?
The largest challenge with this idea is the extra machinery for
synchronization between netpd elements. However, this
You can submit edited patches to the bug tracker on the sourceforge
page [http://sourceforge.net/tracker/?group_id=55736atid=478070
direct link].
I am now wondering something: why haven't these awesomely functional
netpd object been included as abstractions within Pd-extended?!?!
Seriously, they
Hallo!
You can submit edited patches to the bug tracker on the sourceforge
page [http://sourceforge.net/tracker/?group_id=55736atid=478070
direct link].
Yes, or if you have a useful bundle of patches that work out of the box
with pd extended just send them to me or to the list and I will add
42 matches
Mail list logo
