One thing to keep in mind with Pd on modern computers is that 'pd-gui' is a totally separate process from 'pd', so since basically all laptops, desktops, and even tablets these days ship with 2 or more cores, that means 'pd-gui' and 'pd' will be running on separate cores. Therefore, as long as 'pd-gui' doesn't use more than say 70% of one core, it shouldn't affect 'pd' much at all.
.hc On Wed, 2012-02-08 at 17:01 +0100, batinste wrote: > Hi > > See attached patch. Open it, turn on DSP, click the toggle and compare > CPU usage with the subpatch visible or hidden. On my computer, Pd takes > 1% of CPU with the non-visible slider, and between 2 and 3% when the > slider is visible. Remember that [bang~] bangs at audio rate :) I > usually limit slider and al refresh request rate to 20ms or more : or > better, once the patch runs ok, i delete all useless sliders, bangs and > toggles. > > On 08/02/2012 15:41, Jean-Marie Adrien wrote: > > Hello list > > reading everywhere that GUI takes enormous amount of CPU. > > > > More precisely : does a GUI element, say a slider monitoring a signal, > > require lots of CPU in anycase -even when for instance it is invisible > > somewhere deep in a subpatch-, or is it requiring lots of CPU only when > > displayed in front window ? > > JmA > > _______________________________________________ > > [email protected] mailing list > > UNSUBSCRIBE and account-management -> > > http://lists.puredata.info/listinfo/pd-list > > > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
