Bugs item #1893096, was opened at 2008-02-13 12:57
Message generated for change (Comment added) made by sf-robot
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1893096&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: puredata
Group: v0.41.0
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: pd-0.41-0.msw: path and startup dialog don't show values
Initial Comment:
in pd 0.41-0 on msw i set my paths and libraries using the file-path/file-startup dialogs in the gui. the settings seem to be stored all right (according to the windows registry) and the libraries are loaded at next startup. but they don't show up in the path and dialog menus when opened again, so when adding a new library for instace, all the other ones have to be entered again.
----------------------------------------------------------------------
>Comment By: SourceForge Robot (sf-robot)
Date: 2008-06-11 19:20
Message:
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2008-05-28 09:18
Message:
Logged In: YES
user_id=27104
Originator: NO
is this still an problem with 0.41-4?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1893096&group_…
Bugs item #1976100, was opened at 2008-05-27 23:39
Message generated for change (Comment added) made by sf-robot
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1976100&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: None
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: stffn (stffn)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: colorgrid not working on osx
Initial Comment:
colorgrid is not working properly on intel mac osx running Pd-extended 0.40.3 22th of May build.
It does output the RGB values when moving the red square around the grid but the there is no colors in the grid so it's fairly pointless.
(still no 0.40.3 group to choose from in the dropdown)
----------------------------------------------------------------------
>Comment By: SourceForge Robot (sf-robot)
Date: 2008-06-11 19:20
Message:
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2008-05-28 04:52
Message:
Logged In: YES
user_id=27104
Originator: NO
Ok, this should be fixed in tomorrow's build. Works on my machine.
Please test :)
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2008-05-27 23:40
Message:
Logged In: YES
user_id=1658640
Originator: YES
That is pdp_colorgrid of cause. Sorry.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1976100&group_…
hi all
i finally switched over from dapper to hardy and compiled all the
iemlibs fine (using the original makefiles), but they couldn't be
loaded:
/usr/local/lib/pd/extra/iemlib/iemlib1.pd_linux: undefined symbol:
__stack_chk_fail_local
iemlib1: can't load library
i got the same error for iemlib2 and iem_mp3
after googling a bit around, i found some forum-posts saying, that this
error comes from default settings for gcc, that were changed between
ubuntu versions. they also said, that it could be circumvented/fixed
(don't know really) by adding '-fno-stack-protector' to the CFLAGS.
after applying that change to <pd-svn>/externals/iemlib/Make.include and
a recompile, all libs could be loaded fine.
to make a long story short:
would it cause any harm to change the Make.include file in svn repo
accordingly?
roman
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Bugs item #1945042, was opened at 2008-04-17 17:29
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1945042&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: None
>Status: Pending
>Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Roman Haefeli (reduzent)
Assigned to: Nobody/Anonymous (nobody)
Summary: [avg~] and [tavg~] from zexy broken in pd-ext
Initial Comment:
my test-patch:
[avg~]
|
[print]
doesn't print anything at all, even if audio is turned on or a non-zero signal is sent (e.g. [1 ( - [sig~] )
the same goes for [tavg~]
i tested with pd-extended-0.40.3-20080308 on ubuntu dapper.
----------------------
the same behaviour i get with a current checkout of zexy from pd-svn, when i use the pd-extended makefile and compile zexy like this:
cd pd-svn/externals
make zexy
--------------------------
[avg~] and [tavg~] work perfectly, if i compile them with the original makefile:
cd pd-svn/externals/zexy/src
./configure
make
the resulting zexy.pd_linux _doesn't have his bug
---------------------
-> the problem seems to be related to how zexy is compiled and not to the source of avg~ or tavg~.
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2008-06-11 14:39
Message:
Logged In: YES
user_id=564396
Originator: NO
i cannot reproduce this using
Pd-0.40.3-extended-20080611-debian-testing-i386.deb
and should this be a "bug" rather than a "patch"
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1945042&group_…
Patches item #1990686, was opened at 2008-06-11 11:52
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1990686&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: puredata
Group: wishlist
>Status: Closed
>Resolution: Invalid
Priority: 7
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: load abstractions using sys_loader
Initial Comment:
in the current implementation "external" objects are loaded using a "sys_loader" mechanism, whereas "abstractions" are handled in a special way.
the attached patch tries to remove this special handling by using the "sys_loader" mechanism for abstractions as well.
WHY: there are several reasons for why i want this patch:
- unification of object loading (why would we want to handle abstractions and "externals" separately?)
- loading speed (currently when try to create an abstraction [foo], Pd will start searching all of its paths for foo.l_i386 and foo.pd_linux, then it will call all other loaders to try to open "foo" and finally it will search the all paths for "foo.pd"; if i use the abstraction multiple times, i will repeat all(!) of the above steps;
when using the loader-mechanism this can be improved as we already know that a certain object is implemented as an abstraction; therefore there is no need to try to load the object via (e.g.) a dll-loader or the lua-loader.
esp. when running with "-verbose", i have encountered a speedup from 37.941seconds to 14.350seconds when openeing a largish patch (without "-verbose" the speedup should be smaller though)
- (external) hexloader likes to call sys_load_lib() recursively with mangled names; with this patch hexloader (and other advanced stuff) will be working with abstractions as well
COMPATIBILITY ISSUES: currently i cannot think of any; the abstraction load is still called after all other loaders; abstractions are still read from file as they are instantiated
NOTE: this patch requires patch-#1990599 to be applied beforehand http://sourceforge.net/tracker/index.php?func=detail&aid=1990599&group_id=5…
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2008-06-11 12:43
Message:
Logged In: YES
user_id=564396
Originator: YES
actually it doesn't do everything promised; i will try to fix it an reopen
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1990686&group_…
Patches item #1990686, was opened at 2008-06-11 11:52
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1990686&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: puredata
Group: wishlist
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: load abstractions using sys_loader
Initial Comment:
in the current implementation "external" objects are loaded using a "sys_loader" mechanism, whereas "abstractions" are handled in a special way.
the attached patch tries to remove this special handling by using the "sys_loader" mechanism for abstractions as well.
WHY: there are several reasons for why i want this patch:
- unification of object loading (why would we want to handle abstractions and "externals" separately?)
- loading speed (currently when try to create an abstraction [foo], Pd will start searching all of its paths for foo.l_i386 and foo.pd_linux, then it will call all other loaders to try to open "foo" and finally it will search the all paths for "foo.pd"; if i use the abstraction multiple times, i will repeat all(!) of the above steps;
when using the loader-mechanism this can be improved as we already know that a certain object is implemented as an abstraction; therefore there is no need to try to load the object via (e.g.) a dll-loader or the lua-loader.
esp. when running with "-verbose", i have encountered a speedup from 37.941seconds to 14.350seconds when openeing a largish patch (without "-verbose" the speedup should be smaller though)
- (external) hexloader likes to call sys_load_lib() recursively with mangled names; with this patch hexloader (and other advanced stuff) will be working with abstractions as well
COMPATIBILITY ISSUES: currently i cannot think of any; the abstraction load is still called after all other loaders; abstractions are still read from file as they are instantiated
NOTE: this patch requires patch-#1990599 to be applied beforehand http://sourceforge.net/tracker/index.php?func=detail&aid=1990599&group_id=5…
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1990686&group_…
Patches item #1990599, was opened at 2008-06-11 10:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1990599&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: puredata
Group: feature
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: allow recursive calls of new_anything()
Initial Comment:
currently there is a protection mechanism against recursively calling "new_anything()".
unfortunately this mechanism is the main obstacle that prevents abstractions to be loaded via a "loader" mechanism (and instead requires special case handling)
the attached patch will allow some recursive calling of new_anything() (but still has a protection against stack overflow, at a depth of MAXOBJDEPTH=1000)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1990599&group_…
Patches item #1990592, was opened at 2008-06-11 10:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1990592&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: puredata
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: prevent multiple registration of loaders
Initial Comment:
if a single loader is registered multiple times with sys_register_loader(), it will be inserted multiple times in the loader-chain.
thus it might be called several times when a new object is instantiated.
i guess this could be considered a feature, but i was not able to think of any application that would need such a feature.
otoh i stumbled across it, as a (rather naive) implementation of a new loader registered itself permanently, resulting in a very long list of identical loaders to be executed
(yes, the bug was in my loader code, but still i think it rather weird that a loader can be registered several times)
so here is a tiny patch that will prevent already registered loaders to be added to the list of loaders.
--- s_loader.c (Revision 9979)
+++ s_loader.c (Arbeitskopie)
@@ -218,6 +218,9 @@
loader_queue_t *q = &loaders;
while (1)
{
+ /* prevent loaders from being registered multiple times */
+ if (q->loader == loader) return;
+
if (q->next)
q = q->next;
else
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1990592&group_…
Hi,
Using VC++2008 Express on WinXP-SP2,
Referring to "How to write an External in Puredata"
http://pdstatic.iem.at/externals-HOWTO/
In short, the code "helloworld" builds and runs fine on both
pd-Vanilla0.39 and the latest nightly build of pd-extended.
However, the second demonstration "counter" does not work as it lacks
symbolic links to _s_float.
Following is an "excerpt" of the output message since parts of the
original message is in a foreign language.
hworld.obj : error LNK2001: External symbol "_s_float" unresolved.
fatal error LNK1120: 1 unresolved externals
I've found previous posts going back to 2003 with similar issues of
_s_**** not being resolved under VC++ so I am imagining this particular
situation is somewhat an FAQ.
The sad part is that I found no useful solution suggested.
Does anyone have any idea of what is going on?
--
David Shimamoto