Happy new year, all!
I can't seem to find [pool] in my latest download of PD-extended (0.40.3-extended-20071204, Intel Mac). I see help files and some docs for it, but no PD object -- is there an OS X i86 version of it in any of the builds, or am I looking in the wrong place?
Phil Stone pkstonemusic.com
I can't seem to find [pool] in my latest download of PD-extended (0.40.3-extended-20071204, Intel Mac). I see help files and some docs for it, but no PD object -- is there an OS X i86 version of it in
any of the builds, or am I looking in the wrong place?
Hi, up-to-date versions of all my externals for Windows and OSX (UB)
can be found at
http://grrrr.org/ext/beta
gr~~~
On Jan 1, 2008, at 2:33 AM, Thomas Grill wrote:
I can't seem to find [pool] in my latest download of PD-extended (0.40.3-extended-20071204, Intel Mac). I see help files and some
docs for it, but no PD object -- is there an OS X i86 version of it in
any of the builds, or am I looking in the wrong place?Hi, up-to-date versions of all my externals for Windows and OSX
(UB) can be found at http://grrrr.org/ext/beta
You could also just copy the binaries out of the Pd-extended release,
if you want that specific version.
.hc
'You people have such restrictive dress for women,’ she said,
hobbling away in three inch heels and panty hose to finish out
another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
Hi Hans,
I may be misunderstanding, but are you saying it's in the officially released version of PD-extended, and not the nightly builds? (If so, why?)
I plopped the darwin [pool] binary Thomas pointed at into my "flatspace" dirctory (is there a better place?), and so far, so good. Now to figure out Memento and rradical!
Phil
Hans-Christoph Steiner wrote:
On Jan 1, 2008, at 2:33 AM, Thomas Grill wrote:
I can't seem to find [pool] in my latest download of PD-extended (0.40.3-extended-20071204, Intel Mac). I see help files and some docs for it, but no PD object -- is there an OS X i86 version of it in any of the builds, or am I looking in the wrong place?
Hi, up-to-date versions of all my externals for Windows and OSX (UB) can be found at http://grrrr.org/ext/beta
You could also just copy the binaries out of the Pd-extended release, if you want that specific version.
.hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
flext-based things are not built from source as part of Pd-extended.
Binaries are only included in the releases. Check the archives about
this, there is lots of discussion.
.hc
On Jan 1, 2008, at 1:24 PM, Phil Stone wrote:
Hi Hans,
I may be misunderstanding, but are you saying it's in the
officially released version of PD-extended, and not the nightly
builds? (If so, why?)I plopped the darwin [pool] binary Thomas pointed at into my
"flatspace" dirctory (is there a better place?), and so far, so
good. Now to figure out Memento and rradical!Phil
Hans-Christoph Steiner wrote:
On Jan 1, 2008, at 2:33 AM, Thomas Grill wrote:
I can't seem to find [pool] in my latest download of PD-extended (0.40.3-extended-20071204, Intel Mac). I see help files and
some docs for it, but no PD object -- is there an OS X i86 version of it
in any of the builds, or am I looking in the wrong place?Hi, up-to-date versions of all my externals for Windows and OSX
(UB) can be found at http://grrrr.org/ext/betaYou could also just copy the binaries out of the Pd-extended
release, if you want that specific version..hc
'You people have such restrictive dress for women,’ she said,
hobbling away in three inch heels and panty hose to finish out
another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
I have the audacity to believe that peoples everywhere can have three
meals a day for their bodies, education and culture for their minds,
and dignity, equality and freedom for their spirits. - Martin
Luther King, Jr.
It's not as obvious as you might think from the archive. I searched
quite a while before I posted my question. One would have to know to
search on "flext + pd-extended" to find the threads you're indicating.
Someone looking to use Memento (which requires [pool]), might not know
this whole history about incompatible build systems for flext-based
objects, and its implications for using [pool].
I'm in no way complaining about PD-extended and all the work that has gone into it, neither am I dissing the wonderful [pool] (or other flext objects) -- I realize there's no simple solution here, either. It's just another obstacle to building objects that non-PD/SVN experts can use, however. For instance, I'd like to upgrade my [polywavesynth]'s state-saving from sssad to Memento (since I'm already OSC-enabled) -- but this will complicate distribution greatly.
Thanks again for the pointer to the binaries, Thomas. Getting some of the "everybody already knows this" knowledge about flext-based objects into PDPedia would be very helpful.
Phil
Hans-Christoph Steiner wrote:
flext-based things are not built from source as part of Pd-extended.
Binaries are only included in the releases. Check the archives about this, there is lots of discussion..hc
On Jan 1, 2008, at 1:24 PM, Phil Stone wrote:
Hi Hans,
I may be misunderstanding, but are you saying it's in the officially released version of PD-extended, and not the nightly builds? (If so, why?)
I plopped the darwin [pool] binary Thomas pointed at into my "flatspace" dirctory (is there a better place?), and so far, so good. Now to figure out Memento and rradical!
Phil
Hans-Christoph Steiner wrote:
On Jan 1, 2008, at 2:33 AM, Thomas Grill wrote:
I can't seem to find [pool] in my latest download of PD-extended (0.40.3-extended-20071204, Intel Mac). I see help files and some docs for it, but no PD object -- is there an OS X i86 version of it in any of the builds, or am I looking in the wrong place?
Hi, up-to-date versions of all my externals for Windows and OSX (UB) can be found at http://grrrr.org/ext/beta
You could also just copy the binaries out of the Pd-extended release, if you want that specific version.
.hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
This stuff definitely should be in pdpedia. I encourage everyone to
contribute to pdpedia, you don't even have to log in to edit the
pages. Plus it would really help if we heard from people outside of
the usual suspects in things like the pdpedia. ;) More perspectives
means a richer community. :)
.hc
On Jan 1, 2008, at 5:53 PM, Phil Stone wrote:
It's not as obvious as you might think from the archive. I
searched quite a while before I posted my question. One would have
to know to search on "flext + pd-extended" to find the threads
you're indicating. Someone looking to use Memento (which requires
[pool]), might not know this whole history about incompatible build
systems for flext-based objects, and its implications for using
[pool].I'm in no way complaining about PD-extended and all the work that
has gone into it, neither am I dissing the wonderful [pool] (or
other flext objects) -- I realize there's no simple solution here,
either. It's just another obstacle to building objects that non-PD/ SVN experts can use, however. For instance, I'd like to upgrade my
[polywavesynth]'s state-saving from sssad to Memento (since I'm
already OSC-enabled) -- but this will complicate distribution greatly.Thanks again for the pointer to the binaries, Thomas. Getting some
of the "everybody already knows this" knowledge about flext-based
objects into PDPedia would be very helpful.Phil
Hans-Christoph Steiner wrote:
flext-based things are not built from source as part of Pd- extended. Binaries are only included in the releases. Check the
archives about this, there is lots of discussion..hc
On Jan 1, 2008, at 1:24 PM, Phil Stone wrote:
Hi Hans,
I may be misunderstanding, but are you saying it's in the
officially released version of PD-extended, and not the nightly
builds? (If so, why?)I plopped the darwin [pool] binary Thomas pointed at into my
"flatspace" dirctory (is there a better place?), and so far, so
good. Now to figure out Memento and rradical!Phil
Hans-Christoph Steiner wrote:
On Jan 1, 2008, at 2:33 AM, Thomas Grill wrote:
I can't seem to find [pool] in my latest download of PD-extended (0.40.3-extended-20071204, Intel Mac). I see help files and
some docs for it, but no PD object -- is there an OS X i86 version of it
in any of the builds, or am I looking in the wrong place?Hi, up-to-date versions of all my externals for Windows and OSX
(UB) can be found at http://grrrr.org/ext/betaYou could also just copy the binaries out of the Pd-extended
release, if you want that specific version..hc
'You people have such restrictive dress for women,’ she said,
hobbling away in three inch heels and panty hose to finish out
another pink-collar temp pool day. - “Hijab Scene #2", by Mohja
Kahf
I have the audacity to believe that peoples everywhere can have
three meals a day for their bodies, education and culture for
their minds, and dignity, equality and freedom for their
spirits. - Martin Luther King, Jr.
If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an
idea, which an individual may exclusively possess as long as he keeps
it to himself; but the moment it is divulged, it forces itself into
the possession of everyone, and the receiver cannot dispossess
himself of it. - Thomas Jefferson
OK, I updated the [pool] entry in pdpedia a little, to reflect that it's a flext-based object, distributed w/ PD-extended (releases only), and pointed to Thomas' website.
Phil
Hans-Christoph Steiner wrote:
This stuff definitely should be in pdpedia. I encourage everyone to contribute to pdpedia, you don't even have to log in to edit the pages. Plus it would really help if we heard from people outside of the usual suspects in things like the pdpedia. ;) More perspectives means a richer community. :)
.hc
On Jan 1, 2008, at 5:53 PM, Phil Stone wrote:
It's not as obvious as you might think from the archive. I searched quite a while before I posted my question. One would have to know to search on "flext + pd-extended" to find the threads you're indicating. Someone looking to use Memento (which requires [pool]), might not know this whole history about incompatible build systems for flext-based objects, and its implications for using [pool].
I'm in no way complaining about PD-extended and all the work that has gone into it, neither am I dissing the wonderful [pool] (or other flext objects) -- I realize there's no simple solution here, either.
It's just another obstacle to building objects that non-PD/SVN experts can use, however. For instance, I'd like to upgrade my [polywavesynth]'s state-saving from sssad to Memento (since I'm already OSC-enabled) -- but this will complicate distribution greatly.Thanks again for the pointer to the binaries, Thomas. Getting some of the "everybody already knows this" knowledge about flext-based objects into PDPedia would be very helpful.
Phil
Hans-Christoph Steiner wrote:
flext-based things are not built from source as part of Pd-extended. Binaries are only included in the releases. Check the archives about this, there is lots of discussion.
.hc
On Jan 1, 2008, at 1:24 PM, Phil Stone wrote:
Hi Hans,
I may be misunderstanding, but are you saying it's in the officially released version of PD-extended, and not the nightly builds? (If so, why?)
I plopped the darwin [pool] binary Thomas pointed at into my "flatspace" dirctory (is there a better place?), and so far, so good. Now to figure out Memento and rradical!
Phil
Hans-Christoph Steiner wrote:
On Jan 1, 2008, at 2:33 AM, Thomas Grill wrote:
> I can't seem to find [pool] in my latest download of PD-extended > (0.40.3-extended-20071204, Intel Mac). I see help files and > some docs > for it, but no PD object -- is there an OS X i86 version of it > in any of > the builds, or am I looking in the wrong place? >
Hi, up-to-date versions of all my externals for Windows and OSX (UB) can be found at http://grrrr.org/ext/beta
You could also just copy the binaries out of the Pd-extended release, if you want that specific version.
.hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it. - Thomas Jefferson
I don't mean to slight [sssad] in any way; it's worked wonderfully for [polywavesynth]. Memento looks to integrate much better with OSC (which I'm already using in [polywavesynth], and more importantly, will make hierarchical saving more manageable. So, I call it "up" because of some increased functionality.
Phil
Frank Barknecht wrote:
Hallo, Phil Stone hat gesagt: // Phil Stone wrote:
For instance, I'd like to upgrade my [polywavesynth]'s state-saving from sssad to Memento
That's not an upgrade, it's a sidegrade.
Ciao
This seems like a good time to ask... Thomas, did you ever get a chance to check out the buffer overrun bug in [pool] discussed here: http://sourceforge.net/tracker/index.php?func=detail&aid=1818163&gro... ?
I had a look at the source, and perhaps with a little more headbanging (I've never touched C++) I can fix it myself but I'd imagine you can do it much faster : )
I don't mean to nag, but I have a really cool update to Memento that adds [commun]-exposed parameter listing for midi-controller assignment to any Memento-enabled abstraction. The overrun means it kills Pd though (with any nominal level of parameters), so I had to stop development : (.
For [polywavesynth], for example, you could, in two clicks, assign knob 7 of your UC-88 or what-have-you to /polywavesynth1/filter-cutoff, with correct scaling from 0-127 to 20-20000.
And if Novation ever manages to release the SDK for the RemoteSL, I'll be adding automatic display of parameter names on the RemoteSL's LCD screens upon assignment...
Cheers Luke
On Jan 2, 2008 7:28 AM, Phil Stone pkstone@ucdavis.edu wrote:
I don't mean to slight [sssad] in any way; it's worked wonderfully for [polywavesynth]. Memento looks to integrate much better with OSC (which I'm already using in [polywavesynth], and more importantly, will make hierarchical saving more manageable. So, I call it "up" because of some increased functionality.
Phil
Frank Barknecht wrote:
Hallo, Phil Stone hat gesagt: // Phil Stone wrote:
For instance, I'd like to upgrade my [polywavesynth]'s state-saving from sssad to Memento
That's not an upgrade, it's a sidegrade.
Ciao
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Luke Iannini (pd) wrote:
I had a look at the source, and perhaps with a little more headbanging (I've never touched C++) I can fix it myself but I'd imagine you can do it much faster : )
i know C++. perhaps i'll have a look at it while i'm in Bremen next week...
I don't mean to nag, but I have a really cool update to Memento that adds [commun]-exposed parameter listing for midi-controller assignment to any Memento-enabled abstraction. The overrun means it kills Pd though (with any nominal level of parameters), so I had to stop development : (.
... because even though i don't understand this completely, it sounds *really* *really* nice.
one thing i did notice playing around with Memento last night - if you switch substates it only seems to add whatever values you change between switching to the pool. this means that if i have one patch substate (call it substate 0) that sets all the parameters, then make a new substate (substate 1) and change only one value, only that one value will be stored
- which means that to recall the state of the system completely come next
time, i would have to load first substate 0 then substate 1, to completely set all the parameters.
And if Novation ever manages to release the SDK for the RemoteSL, I'll be adding automatic display of parameter names on the RemoteSL's LCD screens upon assignment...
it might be easier to reverse-engineer the Automap protocol. it's just transmitted over sysex AFAIK. and if it's not apparently it's very easy to sniff USB devices. i might give this a go next week..
It's fun, I try to replace memento by sssad, some others tries to replace sssad by memento after coll has been replaced by SSSAD, and maybe they will try later to replace as well memento by sssad (mostly if it has an OSCx bridge, and the grouping of SSSAD_ADMIN messages in a single abstraction only, instead of adressing all patchers, with the use of $0).
Is there a message size limit in sssad, and if there is one, how could we repel this limit?
Patrice Colet a écrit :
It's fun, I try to replace memento by sssad, some others tries to replace sssad by memento after coll has been replaced by SSSAD, and maybe they will try later to replace as well memento by sssad (mostly if it has an OSCx bridge, and the grouping of SSSAD_ADMIN messages in a single abstraction only, instead of adressing all patchers, with the use of $0).
Is there a message size limit in sssad, and if there is one, how could we repel this limit?
By 'message' I tried to mean 'number of stored values in one instance' or something like this...
Hallo, Patrice Colet hat gesagt: // Patrice Colet wrote:
It's fun, I try to replace memento by sssad, some others tries to replace sssad by memento after coll has been replaced by SSSAD, and maybe they will try later to replace as well memento by sssad (mostly if it has an OSCx bridge, and the grouping of SSSAD_ADMIN messages in a single abstraction only, instead of adressing all patchers, with the use of $0).
I actually plan since quite a while to do just that. The idea is, that [sssad] could optionally be created as [sssad /TAG $0] and internally, if the value of $2 ($0 of parent) is greater than 0, an additional send/receive bus will be created that is local to that abstraction. (Those who know Memento will recognize the parallels to [commun /TAG $0] and [originator /SUPERTAG $0].)
There will be no direct support for OSC in [sssad] unless Miller decides to include some OSCroute-variant in plain Pd, as sssad will never require externals. However one could probably build some simple wrappers around sssad to enable OSC pattern matching which is one feature Memento has, but sssad hasn't. The third missing feature of sssad is substates, but I believe, even these are better built as wrappers, and anyway substates would need to be addressed, when local parameter passing is done.
In the end, Memento and sssad will marry and live happily thereafter.
Ciao
Frank Barknecht _ ______footils.org__
On Thu, Jan 03, 2008 at 04:26:56PM +0100, Frank Barknecht wrote:
There will be no direct support for OSC in [sssad] unless Miller decides to include some OSCroute-variant in plain Pd, as sssad will never require externals.
Has anyone lobbied Miller for this feature?
I would love to hear what Miller thinks about OSC in Pd canonical. I queried this in 2005 http://lists.puredata.info/pipermail/pd-list/2005-11/033012.html but he never replied to that thread.
Seems to me that OSC is as valuable to users as MIDI is these days. As many bits of software use OSC now as bits of hardware use MIDI, and even competing commercial products use OSC. Also, the code is there, ready to go into Pd cannonical quite easily.
Best,
Chris.
Wait, isn't OSC GNU? Deja vu for some reason...
~Kyle
On Jan 4, 2008 10:23 PM, Chris McCormick chris@mccormick.cx wrote:
On Thu, Jan 03, 2008 at 04:26:56PM +0100, Frank Barknecht wrote:
There will be no direct support for OSC in [sssad] unless Miller decides to include some OSCroute-variant in plain Pd, as sssad will never require externals.
Has anyone lobbied Miller for this feature?
I would love to hear what Miller thinks about OSC in Pd canonical. I queried this in 2005 http://lists.puredata.info/pipermail/pd-list/2005-11/033012.html but he never replied to that thread.
Seems to me that OSC is as valuable to users as MIDI is these days. As many bits of software use OSC now as bits of hardware use MIDI, and even competing commercial products use OSC. Also, the code is there, ready to go into Pd cannonical quite easily.
Best,
Chris.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Jan 4, 2008 10:23 PM, Chris McCormick chris@mccormick.cx wrote:
On Thu, Jan 03, 2008 at 04:26:56PM +0100, Frank Barknecht wrote:
There will be no direct support for OSC in [sssad] unless Miller decides to include some OSCroute-variant in plain Pd, as sssad will never require externals.
Has anyone lobbied Miller for this feature? http://lists.puredata.info/pipermail/pd-list/2005-11/033012.html but
On Sat, Jan 05, 2008 at 01:08:24AM -0600, Kyle Klipowicz wrote:
Wait, isn't OSC GNU? Deja vu for some reason...
Read the thread.
Best,
Chris.
Ahaha I KNEW it!
Well, did Miller ever weigh in on this?
~Kyle
On Jan 5, 2008 9:30 AM, Chris McCormick chris@mccormick.cx wrote:
On Jan 4, 2008 10:23 PM, Chris McCormick chris@mccormick.cx wrote:
On Thu, Jan 03, 2008 at 04:26:56PM +0100, Frank Barknecht wrote:
There will be no direct support for OSC in [sssad] unless Miller decides to include some OSCroute-variant in plain Pd, as sssad will never require externals.
Has anyone lobbied Miller for this feature? http://lists.puredata.info/pipermail/pd-list/2005-11/033012.html but
On Sat, Jan 05, 2008 at 01:08:24AM -0600, Kyle Klipowicz wrote:
Wait, isn't OSC GNU? Deja vu for some reason...
Read the thread.
Best,
Chris.
I'm still thinking about it. On the plus side, it would make Pd users' lives easier; on the minus, it would introduce a new library dependence and thus reduce Pd's portability.
The OSC design is not much better than that of MIDI, in my opinion... it's a pity it's so widely adopted.
cheers Miller
On Sat, Jan 05, 2008 at 12:20:43PM -0600, Kyle Klipowicz wrote:
Ahaha I KNEW it!
Well, did Miller ever weigh in on this?
~Kyle
On Jan 5, 2008 9:30 AM, Chris McCormick chris@mccormick.cx wrote:
On Jan 4, 2008 10:23 PM, Chris McCormick chris@mccormick.cx wrote:
On Thu, Jan 03, 2008 at 04:26:56PM +0100, Frank Barknecht wrote:
There will be no direct support for OSC in [sssad] unless Miller decides to include some OSCroute-variant in plain Pd, as sssad will never require externals.
Has anyone lobbied Miller for this feature? http://lists.puredata.info/pipermail/pd-list/2005-11/033012.html but
On Sat, Jan 05, 2008 at 01:08:24AM -0600, Kyle Klipowicz wrote:
Wait, isn't OSC GNU? Deja vu for some reason...
Read the thread.
Best,
Chris.
--
---- -----
http://perhapsidid.wordpress.com http://myspace.com/kyleklipowicz
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sat, 5 Jan 2008, Miller Puckette wrote:
I'm still thinking about it. On the plus side, it would make Pd users' lives easier; on the minus, it would introduce a new library dependence and thus reduce Pd's portability.
Oh yeah. And what do you think you're doing with PortAudio? I don't see Pd depending on an external PortAudio library. Where's the portability problem?
The OSC design is not much better than that of MIDI, in my opinion... it's a pity it's so widely adopted.
Do you mean that FUDI is so much better? How so?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
Well, portaudio was unavoidable (it's the only patch to coreaudio on Mac and ASIO on Windows.) But that doesnt' make a good reason to add yet others.
And yes, I think FUDI is much better than OSC, thank you :)
On Sat, Jan 05, 2008 at 01:48:29PM -0500, Mathieu Bouchard wrote:
On Sat, 5 Jan 2008, Miller Puckette wrote:
I'm still thinking about it. On the plus side, it would make Pd users' lives easier; on the minus, it would introduce a new library dependence and thus reduce Pd's portability.
Oh yeah. And what do you think you're doing with PortAudio? I don't see Pd depending on an external PortAudio library. Where's the portability problem?
The OSC design is not much better than that of MIDI, in my opinion... it's a pity it's so widely adopted.
Do you mean that FUDI is so much better? How so?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - t?l:+1.514.383.3801, Montr?al QC Canada
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sat, 5 Jan 2008, Miller Puckette wrote:
On Sat, Jan 05, 2008 at 01:48:29PM -0500, Mathieu Bouchard wrote:
Do you mean that FUDI is so much better? How so?
yes, I think FUDI is much better than OSC, thank you :)
Well, the actual question was "How so?". I don't really care which way you believe as long as I get to know why.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
Miller Puckette wrote:
I'm still thinking about it. On the plus side, it would make Pd users' lives easier; on the minus, it would introduce a new library dependence and thus reduce Pd's portability.
Which library is that? If it was integrated into pd the library would be pd.
Martin
I'd still have to track changes in the OSC code and periodically "import" them to the Pd sources, which is very error-prone.
... and to answer Mathieu's question as to why I prefer FUDI, it's just simpler.
cheers Miller
On Sat, Jan 05, 2008 at 02:17:55PM -0500, Martin Peach wrote:
Miller Puckette wrote:
I'm still thinking about it. On the plus side, it would make Pd users' lives easier; on the minus, it would introduce a new library dependence and thus reduce Pd's portability.
Which library is that? If it was integrated into pd the library would be pd.
Martin
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, Miller Puckette hat gesagt: // Miller Puckette wrote:
I'd still have to track changes in the OSC code and periodically "import" them to the Pd sources, which is very error-prone.
I believ it wouldn't be that bad: OSC has a specification just like MIDI, and this spec doesn't change that often. So once the basic OSC support is included, there won't be a need to do many imports. One thing that already would be useful is a OSCroute or routeOSC object with wildcard support. Wildcards can be very handy. (They even are a bit too limited in OSC for my taste, but it's a least common denominator.)
Ciao
Frank Barknecht _ ______footils.org__
On Sat, 5 Jan 2008, Miller Puckette wrote:
... and to answer Mathieu's question as to why I prefer FUDI, it's just simpler.
I should stop asking questions, it's just simpler.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
Frank Barknecht a écrit :
if the value of $2 ($0 of parent) is greater than 0, an additional send/receive bus will be created that is local to that abstraction.
Genious! I've an idea how to add this and couldn't wait to get this feature, it's attached.
There will be no direct support for OSC in [sssad] unless Miller decides to include some OSCroute-variant in plain Pd, as sssad will never require externals. However one could probably build some simple wrappers around sssad to enable OSC pattern matching which is one feature Memento has, but sssad hasn't. The third missing feature of sssad is substates, but I believe, even these are better built as wrappers, and anyway substates would need to be addressed, when local parameter passing is done.
In the end, Memento and sssad will marry and live happily thereafter.
Ciao
Hallo, Patrice Colet hat gesagt: // Patrice Colet wrote:
Frank Barknecht a écrit :
if the value of $2 ($0 of parent) is greater than 0, an additional send/receive bus will be created that is local to that abstraction.
Genious! I've an idea how to add this and couldn't wait to get this feature, it's attached.
Though it's not quite what I meant. Even with a $0 attached, the global sends should still be active to allow state saving of a complete patch from one central location. The $0 part would activate an *additional* bus, which could be accessed though special messages like "setlocal", "savelocal" or similar.
But maybe I'm just complicating things: such a double-bus could also be made as an abstraction with both [sssad TAG] and your [sssad TAG $0] inside.
Ciao
Frank Barknecht _ ______footils.org__
Frank Barknecht a écrit :
Hallo, Patrice Colet hat gesagt: // Patrice Colet wrote:
Frank Barknecht a écrit :
if the value of $2 ($0 of parent) is greater than 0, an additional send/receive bus will be created that is local to that abstraction.
Genious! I've an idea how to add this and couldn't wait to get this feature, it's attached.
Though it's not quite what I meant. Even with a $0 attached, the global sends should still be active to allow state saving of a complete patch from one central location. The $0 part would activate an *additional* bus, which could be accessed though special messages like "setlocal", "savelocal" or similar.
But maybe I'm just complicating things: such a double-bus could also be made as an abstraction with both [sssad TAG] and your [sssad TAG $0] inside.
Ciao
I'd prefer also the complicated version with a completly integrated double-bus, things would go simplier in the patcher. This version, not as complicated as it is said, could simply be an abstraction called [cssad] or something like this with both [sssad $1] and [sssad $1 $2] inside, like you've described, I'll might try...
Where can i find the latest HID? I jut got a logitech joystick for video filter control and want to try it. I am currently using sarlo's pd_joystick.
-- Patrick Pagano Sound and Light Technologist School of Theatre and Dance University of Florida
[hid] is included in Pd-extended. That's your best bet.
.hc
On Jan 6, 2008, at 2:13 PM, bigswift@cox.net bigswift@cox.net wrote:
Where can i find the latest HID? I jut got a logitech joystick for
video filter control and want to try it. I am currently using
sarlo's pd_joystick.-- Patrick Pagano Sound and Light Technologist School of Theatre and Dance University of Florida
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
"It is convenient to imagine a power beyond us because that means we
don't have to examine our own lives.", from "The Idols of
Environmentalism", by Curtis White
Hi Luke, hi Damian,
i actually thought that i had fixed that issue at an earlier time,
but obviously not.
I committed some stuff to the PD CVS that should prevent buffer
overruns in these cases. I hope that it doesn't have bad side effects.
gr~~~
Am 03.01.2008 um 11:52 schrieb Damian Stewart:
Luke Iannini (pd) wrote:
I had a look at the source, and perhaps with a little more
headbanging (I've never touched C++) I can fix it myself but I'd imagine you can do it much faster : )i know C++. perhaps i'll have a look at it while i'm in Bremen next
week...I don't mean to nag, but I have a really cool update to Memento that adds [commun]-exposed parameter listing for midi-controller
assignment to any Memento-enabled abstraction. The overrun means it kills Pd though (with any nominal level of parameters), so I had to stop development : (.... because even though i don't understand this completely, it sounds *really* *really* nice.
one thing i did notice playing around with Memento last night - if you switch substates it only seems to add whatever values you change
between switching to the pool. this means that if i have one patch substate
(call it substate 0) that sets all the parameters, then make a new substate (substate 1) and change only one value, only that one value will be
stored
- which means that to recall the state of the system completely
come next time, i would have to load first substate 0 then substate 1, to
completely set all the parameters.And if Novation ever manages to release the SDK for the RemoteSL,
I'll be adding automatic display of parameter names on the RemoteSL's LCD screens upon assignment...it might be easier to reverse-engineer the Automap protocol. it's just transmitted over sysex AFAIK. and if it's not apparently it's very
easy to sniff USB devices. i might give this a go next week..-- damian stewart | +351 967 797 263 | damian@frey.co.nz frey | live art with machines | http://www.frey.co.nz
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
On Jan 3, 2008 1:44 PM, Thomas Grill gr@grrrr.org wrote:
I committed some stuff to the PD CVS that should prevent buffer overruns in these cases. I hope that it doesn't have bad side effects.
Woop! Much love Thomas! I'm building it now and I'll have a go with it. Thanks tons!
Am 03.01.2008 um 11:52 schrieb Damian Stewart:
I don't mean to nag, but I have a really cool update to Memento that adds [commun]-exposed parameter listing for midi-controller assignment to any Memento-enabled abstraction. The overrun means it kills Pd though (with any nominal level of parameters), so I had to stop development : (.
... because even though i don't understand this completely, it sounds *really* *really* nice.
I think so too : ). Hopefully I'll have a beta out next-weekish...
one thing i did notice playing around with Memento last night - if you switch substates it only seems to add whatever values you change between switching to the pool. this means that if i have one patch substate (call it substate 0) that sets all the parameters, then make a new substate (substate 1) and change only one value, only that one value will be stored
- which means that to recall the state of the system completely
come next time, i would have to load first substate 0 then substate 1, to completely set all the parameters.
I remember playing with the substates but don't remember this happening, anyway it sounds like a bug. I'll have a look while I'm working on the other stuff (since I've been meaning to use the substates more myself).
And if Novation ever manages to release the SDK for the RemoteSL, I'll be adding automatic display of parameter names on the RemoteSL's LCD screens upon assignment...
it might be easier to reverse-engineer the Automap protocol. it's just transmitted over sysex AFAIK. and if it's not apparently it's very easy to sniff USB devices. i might give this a go next week..
Awesome! I guess I better make sure the sysex patches are in pd-extended...
(Oh, also, I got an email from Novation last week saying the SDK was still soon forthcoming, but then they also said it would be out with the 4.1 software and it wasn't)
Cheers Luke
Hey all, i added new versions for binaries of my externals at http://grrrr.org/ext/beta. Along with that i made a more elaborate skeleton for the pool pdpedia page and hope to find time for the other externals soon.
gr~~~
Luke Iannini (pd) schrieb:
On Jan 3, 2008 1:44 PM, Thomas Grill gr@grrrr.org wrote:
I committed some stuff to the PD CVS that should prevent buffer overruns in these cases. I hope that it doesn't have bad side effects.
Woop! Much love Thomas! I'm building it now and I'll have a go with it. Thanks tons!
Am 03.01.2008 um 11:52 schrieb Damian Stewart:
I don't mean to nag, but I have a really cool update to Memento that adds [commun]-exposed parameter listing for midi-controller assignment to any Memento-enabled abstraction. The overrun means it kills Pd though (with any nominal level of parameters), so I had to stop development : (.
... because even though i don't understand this completely, it sounds *really* *really* nice.
I think so too : ). Hopefully I'll have a beta out next-weekish...
one thing i did notice playing around with Memento last night - if you switch substates it only seems to add whatever values you change between switching to the pool. this means that if i have one patch substate (call it substate 0) that sets all the parameters, then make a new substate (substate 1) and change only one value, only that one value will be stored
- which means that to recall the state of the system completely
come next time, i would have to load first substate 0 then substate 1, to completely set all the parameters.
I remember playing with the substates but don't remember this happening, anyway it sounds like a bug. I'll have a look while I'm working on the other stuff (since I've been meaning to use the substates more myself).
And if Novation ever manages to release the SDK for the RemoteSL, I'll be adding automatic display of parameter names on the RemoteSL's LCD screens upon assignment...
it might be easier to reverse-engineer the Automap protocol. it's just transmitted over sysex AFAIK. and if it's not apparently it's very easy to sniff USB devices. i might give this a go next week..
Awesome! I guess I better make sure the sysex patches are in pd-extended...
(Oh, also, I got an email from Novation last week saying the SDK was still soon forthcoming, but then they also said it would be out with the 4.1 software and it wasn't)
Cheers Luke
Why do things only sink in after I've pressed 'send'? :-) Hans is saying it ([pool] and other flext stuff) is in the official PD-extended releases, just not in the auto-builds. So it's not so bad for re-distribution after all; one just has to be careful with using the auto builds, because that wipes out the flext binaries.
Phil
It's not as obvious as you might think from the archive. I searched quite a while before I posted my question. One would have to know to search on "flext + pd-extended" to find the threads you're indicating.
Someone looking to use Memento (which requires [pool]), might not know this whole history about incompatible build systems for flext-based objects, and its implications for using [pool].I'm in no way complaining about PD-extended and all the work that has gone into it, neither am I dissing the wonderful [pool] (or other flext objects) -- I realize there's no simple solution here, either. It's just another obstacle to building objects that non-PD/SVN experts can use, however. For instance, I'd like to upgrade my [polywavesynth]'s state-saving from sssad to Memento (since I'm already OSC-enabled) -- but this will complicate distribution greatly.
Thanks again for the pointer to the binaries, Thomas. Getting some of the "everybody already knows this" knowledge about flext-based objects into PDPedia would be very helpful.
Phil
Hans-Christoph Steiner wrote:
flext-based things are not built from source as part of Pd-extended.
Binaries are only included in the releases. Check the archives about this, there is lots of discussion..hc
On Jan 1, 2008, at 1:24 PM, Phil Stone wrote:
Hi Hans,
I may be misunderstanding, but are you saying it's in the officially released version of PD-extended, and not the nightly builds? (If so, why?)
I plopped the darwin [pool] binary Thomas pointed at into my "flatspace" dirctory (is there a better place?), and so far, so good. Now to figure out Memento and rradical!
Phil
Hans-Christoph Steiner wrote:
On Jan 1, 2008, at 2:33 AM, Thomas Grill wrote:
I can't seem to find [pool] in my latest download of PD-extended (0.40.3-extended-20071204, Intel Mac). I see help files and some docs for it, but no PD object -- is there an OS X i86 version of it in any of the builds, or am I looking in the wrong place?
Hi, up-to-date versions of all my externals for Windows and OSX (UB) can be found at http://grrrr.org/ext/beta
You could also just copy the binaries out of the Pd-extended release, if you want that specific version.
.hc
'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
-
bigswift＠cox.net -
Chris McCormick -
Damian Stewart -
Frank Barknecht -
Hans-Christoph Steiner -
Kyle Klipowicz -
Luke Iannini (pd) -
Martin Peach -
Mathieu Bouchard -
Miller Puckette -
Patrice Colet -
Phil Stone -
Thomas Grill