I was thinking that now would be a good time to start a release cycle
for Pd-extended 0.43. There is a ton of really useful new stuff in the
editor with the new gui, plugins, etc. So I'm thinking I'll delay some
of the library work I've been doing, and revert to the 0.42.5 behavior
of loading a bunch of libraries by default at startup. But I personally
be dropping my support for a number of included libraries, but anyone is
welcome to pick them up if they want to see them stay in Pd-extended.
You can see the state of things here:
http://puredata.info/docs/LibrariesInPdExtended
This can be a trial run of the new process of keeping things in
Pd-extended. Basically, I need to reduce my maintenance load, I just
can't keep up any more. So I am proposing that the new process for
getting things into a Pd-extended release. First, the new release
branch will be a copy of the previous release branch. Each library/doc
has a maintainer, listed on the LibrariesInPdExtended page. It is that
maintainer's job to update their libraries/docs into the pd-extended
release branch, otherwise the version will be the same as the previous
version. Each version of a library included in Pd-extended needs to a
fully released version with a proper version number and a release posted
on its own page in the http://puredata.info/downloads section, and
ultimately uploaded to Debian/testing (I'm happy to sponsor people's
packages for upload to Debian once they are ready). The full process is
documented here:
http://puredata.info/docs/developer/GettingIntoPdextended
Comments, feedback, concerns? I'd like to make this a much more open
and participatory process.
.hc
Bugs item #3410012, was opened at 2011-09-15 11:36
Message generated for change (Tracker Item Submitted) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3410012&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: externals
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: IOhannes m zmölnig (zmoelnig)
Summary: [zexy/pack], [zexy/unpack] don't create when using zexy lib
Initial Comment:
When using zexy as a single file zexy.pd_linux library, zexy/pack and zexy/unpack do not create, even tho each object seems to register that classname. I tested on Ubuntu/Maverick using the official pd-zexy package.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3410012&group_…
Google caches a lot of web pages, and you can view them. Here's a way
to search for pages on puredata.info, put this into google:
site:puredata.info librarytemplate
Then click on the "Cached" link next to the result that you want.
.hc
On Wed, 2011-09-14 at 15:51 +0100, Joe White wrote:
> I forgot to mention that http://puredata.info is down for me at the
> moment so I couldn't checkout the library information held there.
>
> On 14 September 2011 15:44, Hans-Christoph Steiner <hans(a)at.or.at>
> wrote:
>
> I think that at this point, Jonathan Wilkes is the expert on
> the meta
> data. If you wanted to take on trying to do automatic updates
> using the
> existing library format [1], that would be awesome. That
> should be
> possible on any platform. The new downloads section should
> make it a
> lot easier to automatically find and download updates:
> http://puredata.info/downloads
>
> .hc
>
> [1] http://puredata.info/docs/developer/LibraryTemplate
>
> On Wed, 2011-09-14 at 14:22 +0100, Joe White wrote:
> > Sounds promising Hans,
> >
> >
> > Is there any more info about this meta structure you were
> referring
> > to. How far has this progressed? What are the implications
> for
> > existing libraries and for programs trying to interface with
> it?
> >
> >
> > I'm on OSX and have no knowledge of Debian so I'm not sure
> how helpful
> > I could be. If there is anything I could do let me know. I'm
> > interested in seeing how this would work from a user
> perspective, e.g.
> > being able to seeing available libraries, downloading and
> updating
> > them. I'm looking into adding git support in the app I'm
> writing.
> >
> > Cheers,
> > Joe
> >
> > On 13 September 2011 19:43, Hans-Christoph Steiner
> <hans(a)at.or.at>
> > wrote:
> >
> > Hey Joe,
> >
> > This is a great idea that has been talked about in
> the past
> > every now
> > and then. The big missing piece has always been
> someone who
> > wants to do
> > the work to implement it. Personally, I've been
> moving my own
> > Pd
> > packaging work to be based out of Debian. And I've
> been
> > trying to make
> > a similar process for Pd-extended (see
> GettingIntoPdextended
> > from the
> > original email) You can see the libraries I maintain
> because
> > they are
> > (almost) all in Debian:
> >
> >
> http://qa.debian.org/developer.php?login=hans@eds.org
> >
> > We know have a lot of the pieces in place to make
> this task a
> > lot
> > easier. For example, the libraries all have
> *-meta.pd files
> > which
> > contain meta information about the library.
> Jonathan Wilkes
> > has been
> > doing some great work around the meta data, but the
> more
> > people working
> > on this stuff, the more that gets done :)
> >
> > .hc
> >
> >
> > On Tue, 2011-09-13 at 17:36 +0100, Joe White wrote:
> > > Hey,
> > >
> > >
> > > Forgive me if this is not totally on topic but I
> had an idea
> > a while
> > > ago a wondered what the feasibility of it was.
> > >
> > >
> > > I don't really have a great knowledge of the Pd
> extended
> > package but
> > > how possible would it be to have each library
> versioned (say
> > on
> > > github) as individual repositories that then get
> pulled in
> > the build.
> > > Maybe you could see when certain libraries have
> been changed
> > and
> > > update them on your own machine. Along the idea of
> how
> > macports
> > > works.
> > >
> > > Again, apologies if this is a really stupid
> question.
> > >
> > >
> > > Cheers,
> > > Joe
> > >
> > > On 13 September 2011 17:06, Hans-Christoph Steiner
> > <hans(a)at.or.at>
> > > wrote:
> > >
> > > I was thinking that now would be a good
> time to
> > start a
> > > release cycle
> > > for Pd-extended 0.43. There is a ton of
> really
> > useful new
> > > stuff in the
> > > editor with the new gui, plugins, etc. So
> I'm
> > thinking I'll
> > > delay some
> > > of the library work I've been doing, and
> revert to
> > the 0.42.5
> > > behavior
> > > of loading a bunch of libraries by default
> at
> > startup. But I
> > > personally
> > > be dropping my support for a number of
> included
> > libraries, but
> > > anyone is
> > > welcome to pick them up if they want to
> see them
> > stay in
> > > Pd-extended.
> > > You can see the state of things here:
> > >
> > >
> http://puredata.info/docs/LibrariesInPdExtended
> > >
> > > This can be a trial run of the new process
> of
> > keeping things
> > > in
> > > Pd-extended. Basically, I need to reduce
> my
> > maintenance load,
> > > I just
> > > can't keep up any more. So I am proposing
> that the
> > new
> > > process for
> > > getting things into a Pd-extended
> release. First,
> > the new
> > > release
> > > branch will be a copy of the previous
> release
> > branch. Each
> > > library/doc
> > > has a maintainer, listed on the
> > LibrariesInPdExtended page.
> > > It is that
> > > maintainer's job to update their
> libraries/docs into
> > the
> > > pd-extended
> > > release branch, otherwise the version will
> be the
> > same as the
> > > previous
> > > version. Each version of a library
> included in
> > Pd-extended
> > > needs to a
> > > fully released version with a proper
> version number
> > and a
> > > release posted
> > > on its own page in the
> > http://puredata.info/downloads section,
> > > and
> > > ultimately uploaded to Debian/testing (I'm
> happy to
> > sponsor
> > > people's
> > > packages for upload to Debian once they
> are ready).
> > The full
> > > process is
> > > documented here:
> > >
> > >
> >
> http://puredata.info/docs/developer/GettingIntoPdextended
> > >
> > > Comments, feedback, concerns? I'd like to
> make this
> > a much
> > > more open
> > > and participatory process.
> > >
> > > .hc
> > >
> > >
> _______________________________________________
> > > Pd-dev mailing list
> > > Pd-dev(a)iem.at
> > > http://lists.puredata.info/listinfo/pd-dev
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
The nightly builds are on a separate server:
http://autobuild.puredata.info/auto-build/
.hc
On Tue, 2011-09-13 at 16:54 +0000, Marc D. Demers wrote:
> Hi Hans,
>
> I will be glad to tried out the new PD-extended version but I've been
> unable to connect to the PD site for the past three days... The link
> seems broken...
>
> Regards,
>
> Marc
>
>
>
>
>
> > From: hans(a)at.or.at
> > To: pd-dev(a)iem.at
> > Date: Tue, 13 Sep 2011 12:06:45 -0400
> > Subject: [PD-dev] pd-extended 0.43 release push
> >
> >
> > I was thinking that now would be a good time to start a release
> cycle
> > for Pd-extended 0.43. There is a ton of really useful new stuff in
> the
> > editor with the new gui, plugins, etc. So I'm thinking I'll delay
> some
> > of the library work I've been doing, and revert to the 0.42.5
> behavior
> > of loading a bunch of libraries by default at startup. But I
> personally
> > be dropping my support for a number of included libraries, but
> anyone is
> > welcome to pick them up if they want to see them stay in
> Pd-extended.
> > You can see the state of things here:
> >
> > http://puredata.info/docs/LibrariesInPdExtended
> >
> > This can be a trial run of the new process of keeping things in
> > Pd-extended. Basically, I need to reduce my maintenance load, I just
> > can't keep up any more. So I am proposing that the new process for
> > getting things into a Pd-extended release. First, the new release
> > branch will be a copy of the previous release branch. Each
> library/doc
> > has a maintainer, listed on the LibrariesInPdExtended page. It is
> that
> > maintainer's job to update their libraries/docs into the pd-extended
> > release branch, otherwise the version will be the same as the
> previous
> > version. Each version of a library included in Pd-extended needs to
> a
> > fully released version with a proper version number and a release
> posted
> > on its own page in the http://puredata.info/downloads section, and
> > ultimately uploaded to Debian/testing (I'm happy to sponsor people's
> > packages for upload to Debian once they are ready). The full process
> is
> > documented here:
> >
> > http://puredata.info/docs/developer/GettingIntoPdextended
> >
> > Comments, feedback, concerns? I'd like to make this a much more open
> > and participatory process.
> >
> > .hc
> >
> > _______________________________________________
> > Pd-dev mailing list
> > Pd-dev(a)iem.at
> > http://lists.puredata.info/listinfo/pd-dev
>
Bugs item #3408113, was opened at 2011-09-12 15:07
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3408113&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Block-Sync-Bug!!
Initial Comment:
Hello, I just wanted to inform you guys about this thread in the Pd-Forum ( http://puredata.hurleur.com/sujet-6171-block-bug-sync-differently-sized-blo… ) !!
There is a patch attached (login to see it) (...I have upoloaded it here, too..) that describes the buggy situation.
Summary:Main-patch(block~ 64 1 1; syncable phasor~) + "Sub-sub-patch"(block~ 64 1 1; syncable phasor~) is in a subpatch(block~ 32 1 1) . Sometimes sync works, sometimes not (maybe depending on the blocksize-quotient), and by sometimes I don't mean individual sync-attempts but rather after adding even just a text to the patch, by changing a connection or by switching the dsp off and on!!
Please let us know if there is a workaround or what you think in general.
Im on windows and I used pd-0.42.5-ext & pd-0.43.
Thx
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3408113&group_…
I have 2 large equations that I would like to create an external for. One
of the 2 equations http://dl.dropbox.com/u/6576402/questions/eq1.txt
Basically it's a 1 second periodic signal with sample rate at 44100 which
the equation gives me control over the frequency,amplitude,phase and
vertical offset
So my logic is to have 4 inlets for the frequency,amplitude,phase and
vertical offset and an output for the signal.
If you want to know what type of PD I'm creating and it's options.
1) The first option will import a text file into a table/array that will
control the variables of the equations that will vary
frequency,amplitude,phase and vertical offset over time.
2) The second option will allow the variables to be controllable/variable
using a midi controller and it's audio signal played
I've been able to find instructions on how to create a hello world
C-external but not one that creates a simple sine wave from a sinewave
equation like A*sin(w*t+p)
(https://secure.wikimedia.org/wikipedia/en/wiki/Sine_wave) Does anyone have
one or know where to find one.
It makes sense to make a C external and create inputs for the values of
frequency,amplitude,phase and vertical offset.
That way I can cleanly feed/control those values with a midi controller or a
table/array in PureData.
Thanks
--
--
Bugs item #3406973, was opened at 2011-09-09 18:04
Message generated for change (Tracker Item Submitted) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3406973&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: externals
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: IOhannes m zmölnig (zmoelnig)
Summary: zexy/unpack doesn't handle multi-symbol messages like unpack
Initial Comment:
If you send a message like [one two three four( to [zexy/unpack], you get "zexy/unpack: no method for 'one'", but Pd's [unpack] outputs it fine. Attached is a patch that illustrates the bug.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3406973&group_…
Bugs item #3402940, was opened at 2011-09-01 23:25
Message generated for change (Tracker Item Submitted) made by vilsonvieira
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3402940&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pd-extended
Group: v0.42
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Vilson Vieira (vilsonvieira)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: Missing iemmatrix on Ubuntu 11.04
Initial Comment:
I'm using Ubuntu GNU/Linux 11.04 with Pd installed from a latest build .deb (it is confirmed on other machine running Ubuntu 11.04 too).
The iemmatrix is missing from /usr/lib/pd-extended/iemmatrix.
I've compiled and installed iemmatrix from the Pd SVN [1] and added /usr/lib/pd-extended/iemmatrix on Pd's File -> Path... and it worked.
[1] svn co https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals/iem…
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3402940&group_…