Hi, I looked at your patch and it actually has nothing to do with the array being displayed via gop but rather the VU meter. Namely, your patch reads from the input and uses [env~] object to capture input values. What you didn't do, however, is given env~ object's buffer size, and I think it may default to some awfully small buffer size, so you are asking VU meter to update gui possibly thousands of times per second. To fix this, simply do env~ 16384 or some other power of 2 number and you will be fine. Checked here, after doing this it works fine. You can also try to enable gop but remove vu meter from it and I suspect it will run heck of a lot faster...
If ever in doubt, you can always run pd-l2ork (or pd) with -d 3 flag which will output to console all the gui communication. I did this and found bunch of calls with RCOVER in one of the tags and traced that to vumeter external.
HTH
On 12/09/2012 05:36 AM, Oded Ben-Tal wrote:
hello, Here is the offending patch. playsample is the subpatch that seems to be causing the problems. I turned off the graph on parent option. Let me know if it works with the option turned on. (I am a bit reluctant to install 2 versions of Pd on my system. I did it once, but because I'm not suffiecently good as a sys admin things got a bit messy for me...)
Many thanks Oded
Oded Ben-Tal http://ccrma.stanford.edu/~oded oded@ccrma.stanford.edu
-- Ivica Ico Bukvic, D.M.A Composition, Music Technology Director, DISIS Interactive Sound & Intermedia Studio Director, L2Ork Linux Laptop Orchestra Head, ICAT IMPACT Studio Virginia Tech Department of Music Blacksburg, VA 24061-0240 (540) 231-6139 (540) 231-5034 (fax) disis.music.vt.edu l2ork.music.vt.edu ico.bukvic.net
My latest fixes should help with the problem you describe. Basically, the GUIs will only request a redraw when there is an actual change. Oded, can you try it with a Pd-extended 0.43.4 beta build? Or post the patch so I can try it.
Another optimization I've been thinking of is sending GUI updates on a clock, so the updates will be sent at around 60Hz, since that's the rate the vast majority of screens update at these days.
.hc
On Dec 9, 2012, at 5:53 PM, Ivica Ico Bukvic wrote:
Hi, I looked at your patch and it actually has nothing to do with the array being displayed via gop but rather the VU meter. Namely, your patch reads from the input and uses [env~] object to capture input values. What you didn't do, however, is given env~ object's buffer size, and I think it may default to some awfully small buffer size, so you are asking VU meter to update gui possibly thousands of times per second. To fix this, simply do env~ 16384 or some other power of 2 number and you will be fine. Checked here, after doing this it works fine. You can also try to enable gop but remove vu meter from it and I suspect it will run heck of a lot faster...
If ever in doubt, you can always run pd-l2ork (or pd) with -d 3 flag which will output to console all the gui communication. I did this and found bunch of calls with RCOVER in one of the tags and traced that to vumeter external.
HTH
On 12/09/2012 05:36 AM, Oded Ben-Tal wrote:
hello, Here is the offending patch. playsample is the subpatch that seems to be causing the problems. I turned off the graph on parent option. Let me know if it works with the option turned on. (I am a bit reluctant to install 2 versions of Pd on my system. I did it once, but because I'm not suffiecently good as a sys admin things got a bit messy for me...)
Many thanks Oded
Oded Ben-Tal http://ccrma.stanford.edu/~oded oded@ccrma.stanford.edu
-- Ivica Ico Bukvic, D.M.A Composition, Music Technology Director, DISIS Interactive Sound & Intermedia Studio Director, L2Ork Linux Laptop Orchestra Head, ICAT IMPACT Studio Virginia Tech Department of Music Blacksburg, VA 24061-0240 (540) 231-6139 (540) 231-5034 (fax) disis.music.vt.edu l2ork.music.vt.edu ico.bukvic.net
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
hi Hans,
I am attaching the patch. changing env~ parameter solved the problem. I did, however, test what happens if the vumeter is in the top patch (rather then inside the subpatch) and that doesn't create the same problem (i.e. doing [env~] without giving it a large buffer size). So there might be some additional issue with gop property there.
thanks Oded ___________________________________________________ Oded Ben-Tal http://ccrma.stanford.edu/~oded oded@ccrma.stanford.edu
I think it does it is just that when it is inside a gop it may be more noticeable as array is one of components GUI has to circumnavigate to find the right thing to draw. Try putting both the array and vumeter onto the root canvas and see if it still is better than the one in gop. My hunch would be it would be the same.
Let me know.
-----Original Message----- From: Oded Ben-Tal [mailto:oded@ccrma.Stanford.EDU] Sent: Monday, December 10, 2012 6:37 AM To: Hans-Christoph Steiner Cc: Ivica Ico Bukvic; pd-list@iem.at Subject: Re: [PD] graph on parent problem?
hi Hans,
I am attaching the patch. changing env~ parameter solved the problem. I
did,
however, test what happens if the vumeter is in the top patch (rather then inside the subpatch) and that doesn't create the same problem (i.e. doing [env~] without giving it a large buffer size). So there might be
some
additional issue with gop property there.
thanks Oded ___________________________________________________ Oded Ben-Tal http://ccrma.stanford.edu/~oded oded@ccrma.stanford.edu
-
Hans-Christoph Steiner -
Ivica Ico Bukvic -
Oded Ben-Tal