Hi,
After checking in some changes for cyclone, I hoped to see the results
in the last remaining daily build, the
Pd-0.44.0-extended-20150104-debian-wheezy-amd64.deb
<http://autobuild.puredata.info/auto-build/2015-01-04/Pd-0.44.0-extended-201…>.
But it appears it is no longer synced with the svn repository and builds
the same code every day.
To make sure the state of cyclone code is still ok, I checked out the
repositry and recompiled. Cyclone is ok, but some other libraries fail:
.…
[View More]/pure-data-svn/externals/iem/iem_ambi/src/ambi_decode2.c:7:20: fatal
error: iemlib.h: No such file or directory
./pure-data-svn/externals/iemlib/iemlib1/src/biquad_freq_resp.c:8:20:
fatal error: iemlib.h: No such file or directory
./pure-data-svn/externals/iem/iem_delay/src/block_delay~.c:7:20: fatal
error: iemlib.h: No such file or directory
loaders-pdlua: pdlua.c:45:17: fatal error: lua.h: No such file or directory
gem: TextBase.h:38:22: fatal error: FTFont.h: No such file or directory
For the loaders-pdlua library I found it expects the lua.h in
/usr/lib/lua/ while the actual directory is lua5.2.
This is on Xubuntu 14.04.1 LTS x86_64
Fred Jan
[View Less]
This is exactly what we were *nudging* for. It's not a movement against,
just a growing process. The SVN has served it's purpose but now a more
decentralized approach works since the tools and dev approach have changed.
I created the "pure-data" GH group as an umbrella for this kind of
development, so we could think about moving generally useful & actively
support externals there. Then anyone can do a PR or be given externals
development access via GH groups, etc without worrying about "…
[View More]stepping on
anyones toes" or being stuck with something on their personal account.
Original authors, of course, are free to take over their own projects and
move them if they want, but there are definitely cases of externals which
have become more community developed.
A centralized SVN repository with all externals in it seems like it has
> been a point of friction in the Pd development ecosystem.
>
> You could set up your stuff in Github repositories, and if somebody
> wants to continue to use SVN and also wants your fixes then they can
> figure out how to merge them back. I would make contact with people who
> are doing packaging of the externals for distributions and tell them
> that you have versions of those externals with newer modifications and
> they can decide whether to continue to use the SVN version or your newer
> versions with changes.
>
> Hm, maybe this is too aggressive a strategy, I don't know.
>
> In any case, I don't think there is anything inherently wrong with
> forking code and putting it in a Github repository and making
> improvements. That's basically the whole point of FLOSS. Then if people
> want to use your new versions, great.
>
--
Dan Wilcox
@danomatika
danomatika.comrobotcowboy.com
[View Less]
---
** [patches:#555] never send NULL selectors to objects**
**Status:** open
**Group:** bugfix
**Labels:** puredata-dev crash
**Created:** Fri Aug 28, 2015 08:07 PM UTC by IOhannes m zmölnig
**Last Updated:** Fri Aug 28, 2015 08:07 PM UTC
**Owner:** Miller Puckette
when an object receives bang/float/symbol/pointer messages without having a bang/float/symbol/pointer method defined, it will use the list method instead (if the object has set one).
however, this list method is called with a …
[View More]selector set to 0 (NULL).
if the object passes on the exact incoming message to its outlet (keeping the NULL selector intact), this will lead to a crash, in most cases:
-if the downstream object has an `anything` method and accesses the selector name without checking for NULL first (e.g. `[print]` will simply crash because it tries to print the non-existing selector) OR
- if the downstream object has no `anything` method, the dispatcher will crash when trying to display the `no method for ...` error
since this means that NULL-selectors are forbidden within Pd, Pd shouldn't emit them intentionally.
attached are two patches:
- `0001-never-send-NULL-selectors-to-objects.patch` makes sure that the dispatcher does not generate messages with a NULL-selector.
- `0002-gracefully-handle-messages-with-NIL-selector.patch` makes sure that at least the dispatcher does not crash if it encounters a method with a NULL-selector (as generated by some random object).
the first patch is more important.
---
Sent from sourceforge.net because pd-dev(a)lists.iem.at is subscribed to https://sourceforge.net/p/pure-data/patches/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pure-data/admin/patches/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[View Less]
---
** [patches:#554] make un-created objects findable**
**Status:** open
**Group:** bugfix
**Labels:** error-messages puredata-dev
**Created:** Mon Aug 24, 2015 01:51 PM UTC by Anonymous
**Last Updated:** Mon Aug 24, 2015 01:51 PM UTC
**Owner:** nobody
**Attachments:**
- [0001-make-un-created-objects-findable.patch](http://sourceforge.net/p/pure-… (2.3 kB; text/x-diff)
when an object cannot be created, Pd prints the error `foo couldn't create`
so the user knows that the object failed to …
[View More]instantiate.
unfortunately there is no way to easily find this failed object (in a huge patch).
this patch uses `pd_error()` to print the error-message, so the failed object is
findable via:
- *Find last error*
OR
- *Ctrl-clicking on the error-message*
the patch also reduces the error to a single line,
so you get
[foo] ... couldn't create
rather than
foo
... couldn't create
the buf0-logic works even if resizebytes() actually fails...
---
Sent from sourceforge.net because pd-dev(a)lists.iem.at is subscribed to http://sourceforge.net/p/pure-data/patches/
To unsubscribe from further messages, a project admin can change settings at http://sourceforge.net/p/pure-data/admin/patches/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[View Less]
Hi list,
I'm not a m4/autotools expert and such i'm a bit stuck with codes below (from "m4/universal.m4")
https://github.com/pure-data/pure-data/blob/master/m4/universal.m4#L68
$1[]_CFLAGS="$[]$1[]_CFLAGS $_pd_universal"
$1[]_LDFLAGS="$[]$1[]_LDFLAGS $_pd_universal"
What's the meaning of the "$1[]" and "$[]$1[]" syntaxes?
I guess it is related to macro expansion (to properly obtained ARCH_CFLAGS and ARCH_LDFLAGS), but is that anybody could give me some explanations about that trick?
---
** [bugs:#1214] (Tcl) ERROR ... while executing... : no such object**
**Status:** open
**Group:** v0.46
**Labels:** Tcl ERROR .x10698a0: no such object
**Created:** Fri Aug 07, 2015 09:28 PM UTC by Anonymous
**Last Updated:** Fri Aug 07, 2015 09:28 PM UTC
**Owner:** nobody
This problem has been frustrating me since Pd-extended v.43-4 came. The error renders Pd unusable, the only option being to kill the program and restart it after its occurrence. As no corrections or updates came …
[View More]after Pd-extended v.43.4, a solution is still pending and desired.
I have tried to look for errors in the code of the external object connected to the problem, which simply implements a GUI using tcl/tk, but in fact this code has always worked without problems in the v.42.x and nothing was modified after that. The problem is likely to be connected somehow to tcl/tk flags generation/interception in the Pd-extended v.43.4.
The error comes when a patch window having the GUI object is closed. What follows is that the GUI object is in fact deleted in the window, but the window itself never goes away: it remains open, with just a few text objects on it.
The following error message (in red) appears on the console:
(Tcl) ERRO NÃO TRATADO: image "1081750SPEAKER0" doesn't exist
while executing
"image delete 1081750SPEAKER0"
("uplevel" body line 618)
invoked from within
"uplevel #0 $cmds_from_pd".x10698a0: no such object
.x10698a0: no such object
.x10698a0: no such object
.x10698a0: no such object
.x10698a0: no such object
...
...
The last lines shown above keep coming in dozens as I move the mouse.
After that, the only option is to kill Pd and restart it.
The line in the original c code containing the "image delete" command is shown below, within a "for" loop:
...
for ( ei=0; ei<x->x_num_src; ei++ )
{
sys_vgui(".x%x.c delete %xOUT%d\n", canvas, x, ei );
sys_vgui(".x%x.c delete %xISPEAKER%d\n", canvas, x, ei );
sys_vgui(".x%x.c delete %xSPEAKERNUM%d\n", canvas, x, ei );
sys_vgui("image delete %xSPEAKER%d\n", x, ei );
}
...
I would appreciate any help to provide means to turn off Tcl messaging mechanisms in Pd, or suggestions of flags and additional code that I could insert into the external code so to fix it, or even suggestions to change order of things in the code that could lead to a solution.
Thanks a lot in advance!
Problem reported in Pd-extended v.43.4
MAC OS 10.8.5/Intel
---
Sent from sourceforge.net because pd-dev(a)lists.iem.at is subscribed to http://sourceforge.net/p/pure-data/bugs/
To unsubscribe from further messages, a project admin can change settings at http://sourceforge.net/p/pure-data/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[View Less]
Hi list,I'll have a working deb package of the GUI port of Pd-l2ork in a day or two. However, I don't have access to a Mac atm.
Does anyone want to take a stab at building Pd-l2ork on OSX with the new GUI? If so, let me know.
Some issues:* the Pd-extended build preparations listed on puredata.info still apply for Pd-l2ork on OSX, but some of it might be out of date atm* I don't really understand _why_ the OSX App requires the GUI to start Pd, and not the other way around. …
[View More]Thus, I don't yet havea function to do this in the GUI. (But I think the relevant tcl proc is pretty clear so it shouldn't be too difficult.)
-Jonathan
[View Less]