Bugs item #1984672, was opened at 2008-06-04 19:21
Message generated for change (Comment added) made by stffn
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1984672&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.42
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: stffn (stffn)
Assigned to: Nobody/Anonymous (nobody)
Summary: numbers in comments are not kept as literals
Initial Comment:
...but only if it's followed by a number unless it's 0's then one 0 is kept. Try to open this patch (also attached):
#N canvas 50 50 200 370 missing_0s.pd 10;
#X text 50 10 011;
#X text 50 40 foo;
#X text 50 70 0ff;
#X text 50 100 0 ff;
#X text 50 130 0;
#X text 50 160 01;
#X text 50 190 0 1;
#X text 50 220 0 ;
#X text 50 250 00;
#X text 50 280 02;
#X text 50 310 000;
#X text 50 340 0000;
It's in Pd-0.41-4 and Pd-extended-0.40.3-RC1 on Intel powered Mac OS X
----------------------------------------------------------------------
>Comment By: stffn (stffn)
Date: 2010-02-15 07:37
Message:
This seams to be a feature. Miller writes:
"It's unfortunate, but it's in fact a 'feature' - 1. is a number and all
numbers are printed in their 'simplest' form :)"
Cf. http://lists.puredata.info/pipermail/pd-list/2010-02/076005.html
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2009-02-05 08:26
Message:
Still there in 0.42-3
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2008-08-21 09:49
Message:
Logged In: YES
user_id=564396
Originator: NO
the problem is,that numbers in comments are not kept as literals (strings,
symbols) but are really interpreted as numbers, thus "019" is equivalent to
"19".
the same problem occurs if you have large numbers 8000000001 which will be
stripped to 8e09 (like everywhere else in Pd)
the workaround for this is to make sure that these numbers are really read
as symbols, e.g. by adding quotes (or other non-numerical characters):
#X text 50 310 "000";
i changed the name from "0 in start of comment gets stripped off..."
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1984672&group_…
Bugs item #2949009, was opened at 2010-02-10 06:06
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2949009&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-devel
>Group: v0.43
>Status: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: IOhannes m zmlnig (zmoelnig)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pd-gui-rewrite unusable with NumLock
Initial Comment:
when i have NumLock enabled, pd-gui-rewrite is unusable:
when creating an object, i cannot leave the creation (and thus trigger the instantiation) unless i resort to shortcuts like Ctrl-1.
i cannot connect objects
(trying to connect a messagebox will "click" it; trying to connect a numberbox will shift-drag it)
releasing NumLock fixes all problems
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-02-14 14:08
Message:
I don't know why its a mask, but its in the C code, so I just left it as
is. Here's my attempt at a fix, I don't really have numlock on my laptop,
so I can't really test it. Let me know if it works for you.
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&revision=131…
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2010-02-10 06:32
Message:
and whatever the good reasons behind adding alt/option press to the mouse
bindings, the "key-modifier" value sent to Pd is a _mask_.
since alt/option press uses the value "3", this means that the
key-modifier is actually "Shift+Alt" rather than a separate key.
is this by intention?
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2010-02-10 06:26
Message:
the bug stems from binding the mouse to "Option-Buttonpress-1" in
pd_bindings.tcl:134, which was added with revision 12849:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&revision=128…
probably on OSX the "Option-Click" has a meaning, on linux it should be
disabled.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2949009&group_…
Bugs item #2929284, was opened at 2010-01-10 08:36
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2929284&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.43
Status: Open
Resolution: None
Priority: 8
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Miller Puckette (millerpuckette)
Summary: bang to switch~ while dsp off: Pd exits
Initial Comment:
When a bang is sent to the switch~ object while dsp is turned off (after having been on at least once since start up of Pd), Pd will exit with segmentation fault. This was tested with Pd extended 0.41.4 on OSX 10.5 and on Linux Ubuntu. I guess the bug could be fixed by extending the conditional check in the bang method for block~/switch~:
if(x->x_switched && !x->x_switchon && canvas_dspstate)
(reported anonymously by Katja Vetter)
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-02-13 19:35
Message:
It seems that dsp_chain is the issue, so the code should be perhaps
something like
if (x->x_switched && !x->x_switchon && dsp_chain)
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-02-13 19:25
Message:
Reproduced using Pd-extended 0.42.5-20100120 pd-gui-rewrite/0.43 on Mac OS
X 10.5.8/Intel. Here's the stacktrace:
0 pd 0x0006b3e3 block_bang + 78
(d_ugen.c:227)
1 pd 0x00056eb4 outlet_bang + 56
(m_obj.c:370)
2 pd 0x0003e79c bng_newclick + 153
(g_bang.c:299)
3 pd 0x000378c8 canvas_doclick + 594
(g_editor.c:110)
4 pd 0x00038572 canvas_mousedown + 61
(g_editor.c:1440)
5 pd 0x00054e09 pd_typedmess + 1141
(m_class.c:792)
6 pd 0x00054ccf pd_typedmess + 827
(m_class.c:818)
7 pd 0x00058f5c binbuf_eval + 1224
(m_binbuf.c:726)
8 pd 0x00063232 socketreceiver_read + 1734
(s_inter.c:558)
9 pd 0x00061df2 sys_domicrosleep + 381
(s_inter.c:196)
10 pd 0x00061e7e sys_microsleep + 19
(s_inter.c:219)
11 pd 0x0005f004 m_mainloop + 1030
(m_sched.c:587)
12 pd 0x00061b21 sys_main + 2909
(s_main.c:304)
13 pd 0x00002852 _start + 216
14 pd 0x00002779 start + 41
Can you explain the addition of canvas_dspstate? For me, this change just
makes it so bang never turns on the canvas-local DSP.
----------------------------------------------------------------------
Comment By: Katja (katjav)
Date: 2010-02-13 18:37
Message:
Above-mentioned bug exists in Pd 0.42-4 as well. I have checked that the
problem is indeed solved with the following (where d_ugen_old.c is the
original file and d_ugen.c the modified version):
diff d_ugen_old.c d_ugen.c
222c222
< if (x->x_switched && !x->x_switchon)
---
> if (x->x_switched && !x->x_switchon && canvas_dspstate)
Hope this bug will be fixed soon cause I want to share a patch including
the switch~ object.
Katja
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2929284&group_…
Bugs item #2929284, was opened at 2010-01-10 08:36
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2929284&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.43
Status: Open
Resolution: None
>Priority: 8
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Miller Puckette (millerpuckette)
Summary: bang to switch~ while dsp off: Pd exits
Initial Comment:
When a bang is sent to the switch~ object while dsp is turned off (after having been on at least once since start up of Pd), Pd will exit with segmentation fault. This was tested with Pd extended 0.41.4 on OSX 10.5 and on Linux Ubuntu. I guess the bug could be fixed by extending the conditional check in the bang method for block~/switch~:
if(x->x_switched && !x->x_switchon && canvas_dspstate)
(reported anonymously by Katja Vetter)
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2010-02-13 19:25
Message:
Reproduced using Pd-extended 0.42.5-20100120 pd-gui-rewrite/0.43 on Mac OS
X 10.5.8/Intel. Here's the stacktrace:
0 pd 0x0006b3e3 block_bang + 78
(d_ugen.c:227)
1 pd 0x00056eb4 outlet_bang + 56
(m_obj.c:370)
2 pd 0x0003e79c bng_newclick + 153
(g_bang.c:299)
3 pd 0x000378c8 canvas_doclick + 594
(g_editor.c:110)
4 pd 0x00038572 canvas_mousedown + 61
(g_editor.c:1440)
5 pd 0x00054e09 pd_typedmess + 1141
(m_class.c:792)
6 pd 0x00054ccf pd_typedmess + 827
(m_class.c:818)
7 pd 0x00058f5c binbuf_eval + 1224
(m_binbuf.c:726)
8 pd 0x00063232 socketreceiver_read + 1734
(s_inter.c:558)
9 pd 0x00061df2 sys_domicrosleep + 381
(s_inter.c:196)
10 pd 0x00061e7e sys_microsleep + 19
(s_inter.c:219)
11 pd 0x0005f004 m_mainloop + 1030
(m_sched.c:587)
12 pd 0x00061b21 sys_main + 2909
(s_main.c:304)
13 pd 0x00002852 _start + 216
14 pd 0x00002779 start + 41
Can you explain the addition of canvas_dspstate? For me, this change just
makes it so bang never turns on the canvas-local DSP.
----------------------------------------------------------------------
Comment By: Katja (katjav)
Date: 2010-02-13 18:37
Message:
Above-mentioned bug exists in Pd 0.42-4 as well. I have checked that the
problem is indeed solved with the following (where d_ugen_old.c is the
original file and d_ugen.c the modified version):
diff d_ugen_old.c d_ugen.c
222c222
< if (x->x_switched && !x->x_switchon)
---
> if (x->x_switched && !x->x_switchon && canvas_dspstate)
Hope this bug will be fixed soon cause I want to share a patch including
the switch~ object.
Katja
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2929284&group_…
Bugs item #2929284, was opened at 2010-01-10 14:36
Message generated for change (Comment added) made by katjav
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2929284&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.41
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: bang to switch~ while dsp off: Pd exits
Initial Comment:
When a bang is sent to the switch~ object while dsp is turned off (after having been on at least once since start up of Pd), Pd will exit with segmentation fault. This was tested with Pd extended 0.41.4 on OSX 10.5 and on Linux Ubuntu. I guess the bug could be fixed by extending the conditional check in the bang method for block~/switch~:
if(x->x_switched && !x->x_switchon && canvas_dspstate)
(reported anonymously by Katja Vetter)
----------------------------------------------------------------------
Comment By: Katja (katjav)
Date: 2010-02-14 00:37
Message:
Above-mentioned bug exists in Pd 0.42-4 as well. I have checked that the
problem is indeed solved with the following (where d_ugen_old.c is the
original file and d_ugen.c the modified version):
diff d_ugen_old.c d_ugen.c
222c222
< if (x->x_switched && !x->x_switchon)
---
> if (x->x_switched && !x->x_switchon && canvas_dspstate)
Hope this bug will be fixed soon cause I want to share a patch including
the switch~ object.
Katja
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2929284&group_…
Bugs item #2950978, was opened at 2010-02-13 01:06
Message generated for change (Tracker Item Submitted) made by reduzent
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2950978&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: Roman Haefeli (reduzent)
Assigned to: Nobody/Anonymous (nobody)
Summary: iemlib/[soundfile_info]: does not load certain wav files
Initial Comment:
an example file showing described behaviour can be downloaded here:
http://www.romanhaefeli.net/test8kanal_interleaved_www.wav
when loading such a file with [soundfile_info], it prints the following error:
soundfile_info_read-error: /home/roman/projekte/liestal/soundfiles/test8kanal_interleaved_www.wav has a format-chunk not equal to 16
this and other files generated with the nuendo software have this problem. the files though seem to be compliant wav-files. [readsf~] loads and plays them fine.
'mplayer -identify test8kanal_interleaved_www.wav' prints:
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 44100 Hz, 8 ch, s16le, 5644.8 kbit/100.00% (ratio: 705600->705600)
Only [soundfile_info] seems to have troubles with those files.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2950978&group_…
Bugs item #2949009, was opened at 2010-02-10 12:06
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2949009&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-devel
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmlnig (zmoelnig)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pd-gui-rewrite unusable with NumLock
Initial Comment:
when i have NumLock enabled, pd-gui-rewrite is unusable:
when creating an object, i cannot leave the creation (and thus trigger the instantiation) unless i resort to shortcuts like Ctrl-1.
i cannot connect objects
(trying to connect a messagebox will "click" it; trying to connect a numberbox will shift-drag it)
releasing NumLock fixes all problems
----------------------------------------------------------------------
>Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2010-02-10 12:32
Message:
and whatever the good reasons behind adding alt/option press to the mouse
bindings, the "key-modifier" value sent to Pd is a _mask_.
since alt/option press uses the value "3", this means that the
key-modifier is actually "Shift+Alt" rather than a separate key.
is this by intention?
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2010-02-10 12:26
Message:
the bug stems from binding the mouse to "Option-Buttonpress-1" in
pd_bindings.tcl:134, which was added with revision 12849:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&revision=128…
probably on OSX the "Option-Click" has a meaning, on linux it should be
disabled.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2949009&group_…
Bugs item #2949009, was opened at 2010-02-10 12:06
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2949009&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-devel
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmlnig (zmoelnig)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pd-gui-rewrite unusable with NumLock
Initial Comment:
when i have NumLock enabled, pd-gui-rewrite is unusable:
when creating an object, i cannot leave the creation (and thus trigger the instantiation) unless i resort to shortcuts like Ctrl-1.
i cannot connect objects
(trying to connect a messagebox will "click" it; trying to connect a numberbox will shift-drag it)
releasing NumLock fixes all problems
----------------------------------------------------------------------
>Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2010-02-10 12:26
Message:
the bug stems from binding the mouse to "Option-Buttonpress-1" in
pd_bindings.tcl:134, which was added with revision 12849:
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=rev&revision=128…
probably on OSX the "Option-Click" has a meaning, on linux it should be
disabled.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2949009&group_…
Bugs item #2949009, was opened at 2010-02-10 12:06
Message generated for change (Tracker Item Submitted) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2949009&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-devel
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmlnig (zmoelnig)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: pd-gui-rewrite unusable with NumLock
Initial Comment:
when i have NumLock enabled, pd-gui-rewrite is unusable:
when creating an object, i cannot leave the creation (and thus trigger the instantiation) unless i resort to shortcuts like Ctrl-1.
i cannot connect objects
(trying to connect a messagebox will "click" it; trying to connect a numberbox will shift-drag it)
releasing NumLock fixes all problems
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2949009&group_…
Bugs item #2880419, was opened at 2009-10-16 11:08
Message generated for change (Comment added) made by sf-robot
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2880419&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: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: Pd patch crashes on load
Initial Comment:
I wrote a simple randomisation patch for loading up sequenced wav files, which worked last week. Now for some reason it crashes Pd when I try to load it!
This is on Windows Vista Business, 32-bit, Pd version 0.41.4-extended (I made sure I installed the latest version and tested with this before reporting the problem).
I have tried running with noloadbang startup option, and also running as administrator, but no luck. I am using some non-native objects so that may be the issue..
Problematic patch is attached.
----------------------------------------------------------------------
>Comment By: SourceForge Robot (sf-robot)
Date: 2010-02-10 02:20
Message:
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: 2010-01-26 23:52
Message:
Couldn't reproduce on WinXP with Pd-extended 0.42.5 2010-01-26.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2009-10-20 17:52
Message:
Could you try one of the latest nighly builds of Pd-extended 0.42.5 to see
if it happens there:
http://autobuild.puredata.info/auto-build/latest/
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2009-10-20 12:25
Message:
Ah, that just rerouted things. I found that changing this line:
#X obj 847 386 s track_num;
to this:
#X msg 847 386 s track_num;
AND ALSO changing the print objects to msg objects, actually fixed the
issue.
I hope this helps. I can attach a working version if need be!
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2009-10-20 11:51
Message:
I have found out that removing the lines:
#X obj 609 338 print filename;
#X obj 881 366 print tracknum;
from the file allow it to load correctly. But these are only print
objects! Why could they be causing a crash? Anyway my initial problem is
over..
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=2880419&group_…