Bugs item #1749885, was opened at 2007-07-08 14:16
Message generated for change (Comment added) made by stffn
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1749885&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: 7
Private: No
Submitted By: Frank Barknecht (fbar)
Assigned to: Nobody/Anonymous (nobody)
Summary: zl nth from cyclone crashes on lists with more than 32 items
Initial Comment:
The object [zl nth] from cyclone crashes Pd when dealing with lists of more than 32 items. See attached patch.
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-10-16 14:47
Message:
Logged In: YES
user_id=1658640
Originator: NO
I can not reproduce. Instead it works as expected.
This is Pd-extended (0.39.3) of the 13th of October 2007 autobuilds on
core due macbook running mac os x.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1749885&group_…
Bugs item #1702883, was opened at 2007-04-18 14:08
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1702883&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: frey (freynz)
Assigned to: Nobody/Anonymous (nobody)
Summary: zexy's >~, <~, ==~ etc objects not loading - OSX
Initial Comment:
On both pd-0.39.2-extended-rc2 and Miller's vanilla pd-0.40-2 under OSX on an Intel MacBook, >~, <~, ==~ objects are not loading, even though the 0x2e0x7e.pd &c. files are present in the path.
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-10-16 14:36
Message:
Logged In: YES
user_id=564396
Originator: NO
hmm, pd-0.40 has no hexloader anymore.
you have to use the "hexloader"-external (to be found in
loaders/hexloader) in order to enable it.
does it work then?
----------------------------------------------------------------------
Comment By: Luke Iannini (lukeiannini)
Date: 2007-07-02 00:55
Message:
Logged In: YES
user_id=1541432
Originator: NO
Hi, I can confirm that they are working with Pd-Extended 0.39.2 RC4 on
Mac/Intel. But! That is not my platform; I am using 0.40.2 autobuilds.
Any idea what's necessary to get them working there? If it's informative,
the mtx_* etc. object only work after spawning e.g. mtx_mul still (I know
this is a known issue). But >~ and friends do not have alphabetic
equivalents, so that workaround is not available.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-04-20 04:32
Message:
Logged In: YES
user_id=27104
Originator: NO
I can reproduce this on pd-0.39.2-extended-rc1 on Mac/PowerPC with the
namespace prefix. But if I use [import zexy], then they work. I attached
a patch.
File Added: zexy_hexloader.pd
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1702883&group_…
Bugs item #1242459, was opened at 2005-07-21 19:29
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1242459&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: 6
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Nobody/Anonymous (nobody)
Summary: [bonk~] reads and writes to / by default
Initial Comment:
When reading and writing files with [bonk~], it
defaults to / if no directory is specified. [qlist]
and [textfile] default to the current directory of the
patch. This seems to me to be the correct behavior.
To see this bug in action, save the attached patch to
/tmp and open it.
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-10-16 14:32
Message:
Logged In: YES
user_id=564396
Originator: NO
hmm, on pd-0.40 (linux), bonk~ correctly reads from/writes to the current
directory.
can you confirm whether the bug still exists?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1242459&group_…
Bugs item #1724027, was opened at 2007-05-23 11:57
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1724027&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.40.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Matteo Sisti Sette (sistisette)
Assigned to: Nobody/Anonymous (nobody)
Summary: netsend connect error not displayed in main window in winXP
Initial Comment:
Hi,
I don't know whether this is Windows-specific: only tested it on Windows XP.
In Windows, PD's errors and system messages (as well as [print] outputs) are usually displayed in the main PD window (the one with the "DIO errors" button and "compute audio" checkbox etc.)
However, when a [connect( message is sent to a [netsend] object and the connection cannot be established because nobody is listening to the port (but the host does exist), the following error:
"Connecting stream socket: Unknown error (10061)"
is not displayed in the main window. If running pd from line command, the message is displayed in the dos window. If running PD "directly" without dos window, the error message is not displayed at all.
I guess the message is sent to the stdout or stderr instead of being correctly "catched" and displayed in the main window.
The problem is that no error message at all is displayed in the main window.
Try this to reproduce the bug:
[connect localhost 5000(
|
[netsend]
obviously, with nobody listening to port 5000.
When the host itself is unreachable, a "bad host?" message is correctly displayed in the main window, so the following WON'T reproduce the bug:
[connect badhostname 5000(
|
[netsend]
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-10-16 14:27
Message:
Logged In: YES
user_id=564396
Originator: NO
the problem here is that the error-message is not output by Pd itself but
rather by the underlying library that provides the networking stuff.
this output is sent to stderr directly (and not to Pd which can then
decide where to put it)
a solution for this would be to re-direct the stderr (and stdout when we
are there...) to the pd-console;
i have no idea how to do that.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1724027&group_…
Bugs item #1191610, was opened at 2005-04-28 12:28
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1191610&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: 7
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Miller Puckette (millerpuckette)
Summary: subpatch rename
Initial Comment:
1 create a subpatch (pd sub).
2 create object (ctl 1) click only once into the canvas
(the object is still blue)
3 rename the subpatch to a unknown object (trtrtrtrtr)
4 pd freezes.
marius.schebella_at_chello.at
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-10-16 13:35
Message:
Logged In: YES
user_id=564396
Originator: NO
raised priority since it (still) hangs Pd
----------------------------------------------------------------------
Comment By: ClaudiusMaximus (claudiusmaximus)
Date: 2005-11-09 00:33
Message:
Logged In: YES
user_id=769033
I just ran into this bug (or related bug):
1. create a subpatch [pd test]
2. create a couple of number boxes in the subpatch
3. click into the canvas of the subpatch
4. select the number boxes in the subpatch
5. click into the [pd test] box and rename it to the object
[mtof]
6. on clicking into the canvas, Pd hangs:
Pd version 0.39-1
compiled 05:20:44 Nov 7 2005
(gdb) where
#0 glist_deselect (x=0x828b2a0, y=0x8289178) at g_editor.c:215
#1 0x08086de1 in glist_noselect (x=0x828b2a0) at g_editor.c:222
#2 0x0805961c in canvas_free (x=0x828b2a0) at g_canvas.c:873
#3 0x080a4387 in pd_free (x=0x828b2a0) at m_pd.c:33
#4 0x0805c2a9 in glist_delete (x=0x8249318, y=0x828b2a0) at
g_graph.c:120
#5 0x08062b82 in text_setto (x=0x0, glist=0x8249318,
buf=0x4b <Address 0x4b out of bounds>, bufsize=54) at
g_text.c:1293
#6 0x080818c1 in glist_deselect (x=0x8249318, y=0x828b2a0)
at g_editor.c:207
#7 0x08083229 in canvas_doclick (x=0x8249318, xpos=115,
ypos=82, which=1,
mod=137019608, doit=1) at g_editor.c:222
#8 0x080875db in canvas_mousedown (x=0x8295a88, xpos=0,
ypos=0, which=0,
mod=0) at g_editor.c:1252
#9 0x080a54ed in pd_typedmess (x=0x8249318, s=0x82ac0c8,
argc=136614680,
argv=0x42e60000) at m_class.c:728
#10 0x080a53b6 in pd_typedmess (x=0x82bfc90, s=0x82ac0c8,
argc=4,
argv=0x81266e8) at m_class.c:749
#11 0x080a8894 in binbuf_eval (x=0x8295a88,
target=0x82bfc90, argc=0, argv=0x0)
at m_binbuf.c:574
#12 0x080b0cf0 in socketreceiver_read (x=0x8243228, fd=0) at
s_inter.c:540
#13 0x080b28bf in sys_domicrosleep (microsec=136927880,
pollem=1)
at s_inter.c:180
#14 0x080b1f58 in sys_microsleep (microsec=136927880) at
s_inter.c:202
#15 0x080ad6cf in m_scheduler () at m_sched.c:487
#16 0x080b80db in main (argc=136927880, argv=0x8295a88) at
s_entry.c:27
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1191610&group_…
Bugs item #1121314, was opened at 2005-02-12 13:38
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1121314&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: Closed
>Resolution: Fixed
Priority: 8
Private: No
Submitted By: Tim Blechmann (timblech)
Assigned to: Miller Puckette (millerpuckette)
Summary: writesf~ bug
Initial Comment:
hi all,
there is a terrible bug in writesf~. if the file is
opened, when dsp is off, the file won't be written:
- switch dsp off
- send |open( message to writesf~
- switch dsp of
- send |start( message to writesf~
using the print |message( it can be seen, that fifo
head is working, fifo tail stays equal to zero...
tim
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-10-16 13:28
Message:
Logged In: YES
user_id=564396
Originator: NO
this seems to be fixed at least in pd-0.40
(attached patch works for me)
File Added: writesf~-nowrite.pd
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1121314&group_…
Bugs item #1416539, was opened at 2006-01-27 16:34
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1416539&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: Closed
>Resolution: Duplicate
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: [print] behaves oddly with numeric symbols
Initial Comment:
[symbol 5(
|
[print]
produces: "symbol"
[5]
|
[symbol]
|
[print]
produces: "symbol float"
See attached pd patch.
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-10-16 13:19
Message:
Logged In: YES
user_id=564396
Originator: NO
this is a duplication of bug#1443281
----------------------------------------------------------------------
Comment By: Mathieu Bouchard (matju)
Date: 2006-01-30 05:30
Message:
Logged In: YES
user_id=801174
a [symbol 5( does not produce a symbol atom whose contents
is "5"; instead it's a garbage message, as the special
selectors float/symbol/pointer often imply that the $1 is
of type A_FLOAT/A_SYMBOL/A_POINTER and so in various
situation the value will be replaced by a dummy value, such
as either the empty string symbol (&s_) or the "float"
symbol (&s_float).
Compare with this:
[53(
|
[makefilename %c]
|
[print]
which produces a message whose $1 is a A_SYMBOL and so
prints "symbol 5".
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1416539&group_…
Bugs item #1267819, was opened at 2005-08-24 11:00
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1267819&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: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: crash on array rename
Initial Comment:
in Pd 0.39-test5 (windows), renaming an array with a
message [; array1 rename array2] makes pd crash.
it is possible to rename once (only the name-graphics
isn't updated until the array itself is moved). after
that trying to rename again makes pd crash.
not sure if this is the right place to report a bug for
the test-version?
Rune Søchting
runesoc(a)post11.tele.dk
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2007-10-16 13:17
Message:
Logged In: YES
user_id=564396
Originator: NO
this seems to have been fixed in pd-0.40
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1267819&group_…
Bugs item #1285041, was opened at 2005-09-08 17:49
Message generated for change (Settings changed) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1285041&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: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Georg Holzmann (grholzi)
Assigned to: Nobody/Anonymous (nobody)
Summary: writesf_open bug
Initial Comment:
in a construction like this
[savepanel]
|
[open $1(
|
[writesf~]
clicking directly on the [open( message kills Pd
gdb output:
0x080e7512 in writesf_open (x=0x811af68, s=0x81137e8,
argc=1, argv=0x80f92d0)
at d_soundfile.c:2312
2312 x->x_filename = filesym->s_name;
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-01-13 21:00
Message:
Logged In: YES
user_id=564396
fixed in 0.39-2
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1285041&group_…