I've read further and searched the archives of the list.
Is this related to denormals?
Isn't pd now handling denormals correctly? (that is, avoiding them) I mean vanilla 0.40.
I ask that because I've seen discussion dating back to 2003 about this issue. Is it still an issue?
Another thing I don't understand is why that is a problem only in pentium4: don't other processors have denormals as well?
thanks m.
----- Original Message ----- From: "Matteo Sisti Sette" matteo.sistisette@email.it To: pd-list@iem.at Sent: Wednesday, May 02, 2007 12:36 PM Subject: P4-optimized 0.40 vanilla precompiled for windows?
Hi,
I'm having the "CPU jumps after a while" problem. That is, the same patch which at the beginning is consuming about 30% of CPU, after a while it is running (and absolutely nothing changes in it, and I am totally sure this is true) suddenly jumps to a CPU consumption over 70%.
I've read in the archives it is an issue specific to Pentium4, and that there is an optimized version of PD that solves it.
Is there a 0.40.x pentium4-optimized version of pd-vanilla precompiled for windows? If so, where can I find it?
Thanks a lot in advance bye m.
----- Original Message ----- From: pd-list-request@iem.at To: pd-list@iem.at Sent: Wednesday, May 02, 2007 12:00 PM Subject: PD-list Digest, Vol 26, Issue 7
Send PD-list mailing list submissions to pd-list@iem.at
To subscribe or unsubscribe via the World Wide Web, visit http://lists.puredata.info/listinfo/pd-list or, via email, send a message with subject or body 'help' to pd-list-request@iem.at
You can reach the person managing the list at pd-list-owner@iem.at
When replying, please edit your Subject line so it is more specific than "Re: Contents of PD-list digest..."
Today's Topics:
Message: 1 Date: Wed, 2 May 2007 18:28:18 +0900 From: "hard off" hard.off@gmail.com Subject: Re: [PD] Implementing "switch-and-ramp" technique to cancel discontinuities To: pd-list@iem.at Message-ID: 161320dd0705020228o35662cf8o41fdd4a8f7e2e59f@mail.gmail.com Content-Type: text/plain; charset="iso-8859-1"
btw. just found a bug in my patch. corrected here: