Bugs item #1736518, was opened at 2007-06-13 10:49
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1736518&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: hardoff (hardoff)
Assigned to: Miller Puckette (millerpuckette)
>Summary: [switch~]ing [vline~] causes ever increasing CPU usage
Initial Comment:
it was recently brought to my attention that vline~ continues storing messages it receives when dsp processing is switched off. this can lead to a gradual rise in dsp usage of patches containing vline~. i wrote a quick note about it in the documentation to warn others.
for more info seed claude's explaination here:
http://lists.puredata.info/pipermail/pd-list/2007-06/050998.html
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-13 11:28
Message:
Logged In: YES
user_id=27104
Originator: NO
File Added: cputest.zip
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1736518&group_…
Bugs item #1736518, was opened at 2007-06-13 10:49
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1736518&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: hardoff (hardoff)
>Assigned to: Miller Puckette (millerpuckette)
Summary: vline~ doc ammendment
Initial Comment:
it was recently brought to my attention that vline~ continues storing messages it receives when dsp processing is switched off. this can lead to a gradual rise in dsp usage of patches containing vline~. i wrote a quick note about it in the documentation to warn others.
for more info seed claude's explaination here:
http://lists.puredata.info/pipermail/pd-list/2007-06/050998.html
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1736518&group_…
I am trying to get a external written using functions outside of Pd. I have my header files included and
the external is compiling but when I try to load it into Pd I get this error:
10): Symbol not found: _whatever-external-function
Expected in: dynamic lookup
[import]: ERROR: can't load library in FTIR_CXX
What can I do to fix this?
Alain
Feature Requests item #1736518, was opened at 2007-06-13 23:49
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478073&aid=1736518&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
Priority: 5
Private: No
Submitted By: hardoff (hardoff)
Assigned to: Nobody/Anonymous (nobody)
Summary: vline~ doc ammendment
Initial Comment:
it was recently brought to my attention that vline~ continues storing messages it receives when dsp processing is switched off. this can lead to a gradual rise in dsp usage of patches containing vline~. i wrote a quick note about it in the documentation to warn others.
for more info seed claude's explaination here:
http://lists.puredata.info/pipermail/pd-list/2007-06/050998.html
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478073&aid=1736518&group_…
On Tue, Jun 12, 2007 at 12:27:20PM +0200, Tim Boykett wrote:
>
> On 11/06/2007, at 10:54 AM, Chris McCormick wrote:
> >
> >I await your silent assent with baited breath.
>
> I think we would all prefer it if your breath was bated and
> not baited,
Hehe. Well spotted, sir. I'll have to think twice now before engaging my
anal retentive grammer reflex on other people!
Best,
Chris.
-------------------
http://mccormick.cx
Bugs item #1645862, was opened at 2007-01-27 06:12
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1645862&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.39.2
>Status: Closed
Resolution: Postponed
Priority: 5
Private: No
Submitted By: stffn (stffn)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: delread~/delwrite~ not working on Intel Mac builds
Initial Comment:
There seam to be some issues some internal object for the intel mac build of Pd-extended-0.39.2-test7.
The (known) objects that have problems are:
[delwrite~]
[delread~]
[sqrt~]
How they don't work
-------------------
* sqrt~ of the signal 9 returns -\infty, hence not 3 as expected. All tried int signals greater then zero returns -\infty. To test this, see either the attached patch (which is very close to the help-patch for [sqrt~]) or the help-patch for [sqrt~].
See also:
http://lists.puredata.info/pipermail/pd-list/2007-01/046266.html
* delread~ and delwrite~ don't work in the sense that if one open the delread~ help file and change the value of the "input to delay line" number box. Then nothing happens in the number box connected to the snapshot, which was expected.
See also:
http://lists.puredata.info/pipermail/pd-list/2007-01/046077.html
A "tried" solution
------------------
It has been suggested that it had to do with CPU optimizeing compile flags, see:
http://lists.puredata.info/pipermail/pd-list/2007-01/046016.html
I have done builds which tries different compile flags on my intel mac machine, and none of those builds have problems with the named objects, see:
http://lists.puredata.info/pipermail/pd-list/2007-01/046044.html
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-06-12 08:18
Message:
Logged In: YES
user_id=1658640
Originator: YES
In the autobuild from 12th of june it works on mac-intel (macbook core
duo) and on powerpc (ibook G4). Both running Mac OS 10.4.9.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-12 00:25
Message:
Logged In: YES
user_id=27104
Originator: NO
I removed these from the compiler flags and it seems to have fixed the
problem on Intel Macs:
-ftree-vectorize -ftree-vectorizer-verbose=2
Please confirm that this is fixed in both Intel and PowerPC.
This thread discusses the root causes of why the auto-vectorization causes
this problem:
http://lists.puredata.info/pipermail/pd-dev/2007-04/008689.html
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-05-05 09:11
Message:
Logged In: YES
user_id=1658640
Originator: YES
Still present in the nightly build of RC2 from 5th of May. It does however
work in the test build of .040.2-extended of the same date.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-04-01 19:17
Message:
Logged In: YES
user_id=27104
Originator: NO
Following up on Steffen's tests, it sounds to me like this bug is probably
caused by one of the patches in packages/patches.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2007-03-22 22:23
Message:
Logged In: NO
I will second this for ppc g4+ optimized version (iMac G5) - delays work
but sqrt~ is getting the same problem.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1645862&group_…
Bugs item #1692649, was opened at 2007-04-01 23:51
Message generated for change (Settings changed) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1692649&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.39.2
>Status: Open
Resolution: Postponed
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: sqrt~ giving only -inf/inf
Initial Comment:
For the G4 and Intel optimized builds of Pd-0.39.2-extended-test7 on Mac OS X, sqrt~ only returns -inf or inf. (Does this affect other platforms?) This is probably related to the auto-vectorization. This is not a problem on Pd-0.39.2-extended-test7 that was built for G3s.
Check the sqrt~-help.pd file for a test patch.
sqrt~ of the signal 9 returns -\infty, hence not 3 as expected. All tried int signals greater then zero returns -\infty. To test this, see either the attached patch (which is very close to the help-patch for [sqrt~]) or the help-patch for [sqrt~].
See also:
http://lists.puredata.info/pipermail/pd-list/2007-01/046266.html
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-06-12 08:18
Message:
Logged In: YES
user_id=1658640
Originator: NO
In the autobuild from 12th of june it now works on mac-intel (macbook core
duo), but - sadly - not on powerpc (ibook G4). Both running Mac OS 10.4.9.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-12 00:26
Message:
Logged In: YES
user_id=27104
Originator: YES
I removed these from the compiler flags and it seems to have fixed the
problem on Intel Macs:
-ftree-vectorize -ftree-vectorizer-verbose=2
Please confirm that this is fixed in both Intel and PowerPC.
This thread discusses the root causes of why the auto-vectorization causes
this problem:
http://lists.puredata.info/pipermail/pd-dev/2007-04/008689.html
Ideally the root of the problem would be fixed so that we can use
auto-vectorization.
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-05-05 09:11
Message:
Logged In: YES
user_id=1658640
Originator: NO
Still present in the nightly build of RC2 from 5th of May. It does however
work in the test build of .040.2-extended of the same date.
----------------------------------------------------------------------
Comment By: frey (freynz)
Date: 2007-04-18 08:06
Message:
Logged In: YES
user_id=1772500
Originator: NO
I have this same problem with pd-0.39.2-extended-rc2 on my Intel MacBook.
It doesn't appear in Miller's vanilla pd-0.40-2, on the same machine.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-04-02 00:08
Message:
Logged In: YES
user_id=27104
Originator: YES
d_math.c, where sqrt.c isn't auto-vectorized, so this is probably caused
by a different optimization flag. Or maybe it's related to these
warnings:
d_math.c: In function 'init_rsqrt':
d_math.c:79: warning: dereferencing type-punned pointer will break
strict-aliasing rules
d_math.c: In function 'q8_rsqrt':
d_math.c:93: warning: dereferencing type-punned pointer will break
strict-aliasing rules
d_math.c: In function 'q8_sqrt':
d_math.c:101: warning: dereferencing type-punned pointer will break
strict-aliasing rules
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1692649&group_…
Bugs item #1692649, was opened at 2007-04-02 05:51
Message generated for change (Comment added) made by stffn
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1692649&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.39.2
Status: Pending
Resolution: Postponed
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: sqrt~ giving only -inf/inf
Initial Comment:
For the G4 and Intel optimized builds of Pd-0.39.2-extended-test7 on Mac OS X, sqrt~ only returns -inf or inf. (Does this affect other platforms?) This is probably related to the auto-vectorization. This is not a problem on Pd-0.39.2-extended-test7 that was built for G3s.
Check the sqrt~-help.pd file for a test patch.
sqrt~ of the signal 9 returns -\infty, hence not 3 as expected. All tried int signals greater then zero returns -\infty. To test this, see either the attached patch (which is very close to the help-patch for [sqrt~]) or the help-patch for [sqrt~].
See also:
http://lists.puredata.info/pipermail/pd-list/2007-01/046266.html
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-06-12 14:18
Message:
Logged In: YES
user_id=1658640
Originator: NO
In the autobuild from 12th of june it now works on mac-intel (macbook core
duo), but - sadly - not on powerpc (ibook G4). Both running Mac OS 10.4.9.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-12 06:26
Message:
Logged In: YES
user_id=27104
Originator: YES
I removed these from the compiler flags and it seems to have fixed the
problem on Intel Macs:
-ftree-vectorize -ftree-vectorizer-verbose=2
Please confirm that this is fixed in both Intel and PowerPC.
This thread discusses the root causes of why the auto-vectorization causes
this problem:
http://lists.puredata.info/pipermail/pd-dev/2007-04/008689.html
Ideally the root of the problem would be fixed so that we can use
auto-vectorization.
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-05-05 15:11
Message:
Logged In: YES
user_id=1658640
Originator: NO
Still present in the nightly build of RC2 from 5th of May. It does however
work in the test build of .040.2-extended of the same date.
----------------------------------------------------------------------
Comment By: frey (freynz)
Date: 2007-04-18 14:06
Message:
Logged In: YES
user_id=1772500
Originator: NO
I have this same problem with pd-0.39.2-extended-rc2 on my Intel MacBook.
It doesn't appear in Miller's vanilla pd-0.40-2, on the same machine.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-04-02 06:08
Message:
Logged In: YES
user_id=27104
Originator: YES
d_math.c, where sqrt.c isn't auto-vectorized, so this is probably caused
by a different optimization flag. Or maybe it's related to these
warnings:
d_math.c: In function 'init_rsqrt':
d_math.c:79: warning: dereferencing type-punned pointer will break
strict-aliasing rules
d_math.c: In function 'q8_rsqrt':
d_math.c:93: warning: dereferencing type-punned pointer will break
strict-aliasing rules
d_math.c: In function 'q8_sqrt':
d_math.c:101: warning: dereferencing type-punned pointer will break
strict-aliasing rules
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1692649&group_…
Bugs item #1645862, was opened at 2007-01-27 12:12
Message generated for change (Comment added) made by stffn
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1645862&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.39.2
>Status: Open
Resolution: Postponed
Priority: 5
Private: No
Submitted By: stffn (stffn)
Assigned to: Hans-Christoph Steiner (eighthave)
Summary: delread~/delwrite~ not working on Intel Mac builds
Initial Comment:
There seam to be some issues some internal object for the intel mac build of Pd-extended-0.39.2-test7.
The (known) objects that have problems are:
[delwrite~]
[delread~]
[sqrt~]
How they don't work
-------------------
* sqrt~ of the signal 9 returns -\infty, hence not 3 as expected. All tried int signals greater then zero returns -\infty. To test this, see either the attached patch (which is very close to the help-patch for [sqrt~]) or the help-patch for [sqrt~].
See also:
http://lists.puredata.info/pipermail/pd-list/2007-01/046266.html
* delread~ and delwrite~ don't work in the sense that if one open the delread~ help file and change the value of the "input to delay line" number box. Then nothing happens in the number box connected to the snapshot, which was expected.
See also:
http://lists.puredata.info/pipermail/pd-list/2007-01/046077.html
A "tried" solution
------------------
It has been suggested that it had to do with CPU optimizeing compile flags, see:
http://lists.puredata.info/pipermail/pd-list/2007-01/046016.html
I have done builds which tries different compile flags on my intel mac machine, and none of those builds have problems with the named objects, see:
http://lists.puredata.info/pipermail/pd-list/2007-01/046044.html
----------------------------------------------------------------------
>Comment By: stffn (stffn)
Date: 2007-06-12 14:18
Message:
Logged In: YES
user_id=1658640
Originator: YES
In the autobuild from 12th of june it works on mac-intel (macbook core
duo) and on powerpc (ibook G4). Both running Mac OS 10.4.9.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-12 06:25
Message:
Logged In: YES
user_id=27104
Originator: NO
I removed these from the compiler flags and it seems to have fixed the
problem on Intel Macs:
-ftree-vectorize -ftree-vectorizer-verbose=2
Please confirm that this is fixed in both Intel and PowerPC.
This thread discusses the root causes of why the auto-vectorization causes
this problem:
http://lists.puredata.info/pipermail/pd-dev/2007-04/008689.html
----------------------------------------------------------------------
Comment By: stffn (stffn)
Date: 2007-05-05 15:11
Message:
Logged In: YES
user_id=1658640
Originator: YES
Still present in the nightly build of RC2 from 5th of May. It does however
work in the test build of .040.2-extended of the same date.
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-04-02 01:17
Message:
Logged In: YES
user_id=27104
Originator: NO
Following up on Steffen's tests, it sounds to me like this bug is probably
caused by one of the patches in packages/patches.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2007-03-23 03:23
Message:
Logged In: NO
I will second this for ppc g4+ optimized version (iMac G5) - delays work
but sqrt~ is getting the same problem.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1645862&group_…
Bugs item #1508138, was opened at 2006-06-18 09:47
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1508138&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.39.2
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: João Miguel Pais (jmmmp)
Assigned to: Nobody/Anonymous (nobody)
Summary: program crash leads to system crash
Initial Comment:
If pd crashes once (for whichever reason it may be),
when the program is loaded again a system error occurs,
and a blue screen appears.
The error message of the blue screen is
IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0X0000000A (0X00000004, 0X00000002,
0X00000000, 0X804E39A7)
Therefore, if pd crashes, it is necessary to reboot the
system in order to avoid a system crash (logging out
doesn't help).
Pd-ext 0.39-2 t3
XP Prof
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2007-06-12 00:55
Message:
Logged In: YES
user_id=27104
Originator: NO
a STOP 0x0A message generally means either bad drivers or bad hardware.
Microsoft says "Typically, this error occurs when a driver uses an
incorrect memory address. Other possible causes of this error are an
incompatible device driver, a general hardware problem, and incompatible
software. "
http://support.microsoft.com/kb/314063
Pd really shouldn't be able to cause a blue screen on its own, I think
that even Windows isn't that bad.
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2006-10-10 09:13
Message:
Logged In: YES
user_id=564396
"I don't have a patch, because it was corrected already (I
don't remember now)."
does this mean that it works now?
can we close this?
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2006-06-19 02:49
Message:
Logged In: NO
then also try to test your RAM sanity, with software like
memtest86.... it could be a bad bank of ram...
----------------------------------------------------------------------
Comment By: João Miguel Pais (jmmmp)
Date: 2006-06-18 16:01
Message:
Logged In: YES
user_id=1523458
The problem has nothing to do with audio, as actually in
most of the cases I didn't had audio on. I don't have a
patch, because it was corrected already (I don't remember
now).
But the error that made pd crash the first time might had to
do with a cpu overload (or whatever is it called) due to an
infinite loop.
Which kind of hardware info is necessary? I guess saying IBM
Thinkpad R51 1,6Mhz 1GbRam doesn't help much.
----------------------------------------------------------------------
Comment By: Thomas Grill (xovo)
Date: 2006-06-18 13:24
Message:
Logged In: YES
user_id=350252
Although the information given about the crash is close to nothing (for
whichever reason that may be), it's almost certainly a driver bug, not a
pure
pd bug. You should include info about what you are doing (include patches,
description etc.) and about your hardware. And you should try to find
newer/
different drivers for your audio hardware and see if the problem persists.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1508138&group_…