Hello all,
I assume that if env~ exists in a patch, it is active whether or not a signal is passing through it. This means that env~ is using CPU even though it's input might be "zero"?
Is there some method of turning off env~ or perhaps change its window size dynamically so that it's not taking up so much CPU?
For example, I'm using [env~ 8192] to send a level to VU meters. I've then created a spigot-like object that will cut the signal going to that [env~] in an attempt to save CPU power so that PD doesn't have to continually update the VU meters. Like this:
[osc~] > [*~ 1/0 (depending on toggle)] > [env~ 8192] > [- 100] > [Vu meter]
However, even if the [osc~] is multiplied by "zero", CPU usage is still too high because [env~ 8192] is computing all the time (zero x whatever? over and over 5 times per second). Is there some method of actually 'turning-off' the [env~] or perhaps change its windows size to [env~ 131072] for example when I don't need to see the VU?
Thanks Dave S
The VU meter is probably taking many times as much CPU timeas the env~, so a spigot at env~'s output would probably be good enough; but you can even turn off the env~ itself by putting it in a subpatch and using "switch~" to turn the subpatch off.
cheers Miller
On Thu, Aug 01, 2002 at 08:36:09PM -0600, David Sabine wrote:
Hello all,
I assume that if env~ exists in a patch, it is active whether or not a signal is passing through it. This means that env~ is using CPU even though it's input might be "zero"?
Is there some method of turning off env~ or perhaps change its window size dynamically so that it's not taking up so much CPU?
For example, I'm using [env~ 8192] to send a level to VU meters. I've then created a spigot-like object that will cut the signal going to that [env~] in an attempt to save CPU power so that PD doesn't have to continually update the VU meters. Like this:
[osc~] > [*~ 1/0 (depending on toggle)] > [env~ 8192] > [- 100] > [Vu meter]
However, even if the [osc~] is multiplied by "zero", CPU usage is still too high because [env~ 8192] is computing all the time (zero x whatever? over and over 5 times per second). Is there some method of actually 'turning-off' the [env~] or perhaps change its windows size to [env~ 131072] for example when I don't need to see the VU?
Thanks Dave S
Hello,
I was wondering if anybody on this list is IN or NEAR Rome?
If so, please let me know. A choreographer in Rome contacted me via my website with questions about a MIDI controlled 'Intelligent Stage'.
I'd like to help the project, but I'm in Canada. Hence, the distance might make the collaboration very difficult - but if there's a PD guru near Rome then I'll refer the choreographer to you.
Regards, Dave Sabine
----- Original Message ----- From: "Miller Puckette" mpuckett@man104-1.ucsd.edu To: "David Sabine" dave@davesabine.com Cc: pd-list@iem.kug.ac.at Sent: Thursday, August 01, 2002 8:48 PM Subject: Re: [PD] Turn off env~?
The VU meter is probably taking many times as much CPU timeas the env~, so a spigot at env~'s output would probably be good enough; but you can even turn off the env~ itself by putting it in a subpatch and using "switch~"
to
turn the subpatch off.
cheers Miller
On Thu, Aug 01, 2002 at 08:36:09PM -0600, David Sabine wrote:
Hello all,
I assume that if env~ exists in a patch, it is active whether or not a
signal is passing through it. This means that env~ is using CPU even though it's input might be "zero"?
Is there some method of turning off env~ or perhaps change its window
size dynamically so that it's not taking up so much CPU?
For example, I'm using [env~ 8192] to send a level to VU meters. I've
then created a spigot-like object that will cut the signal going to that [env~] in an attempt to save CPU power so that PD doesn't have to continually update the VU meters. Like this:
[osc~] > [*~ 1/0 (depending on toggle)] > [env~ 8192] > [- 100] > [Vu
meter]
However, even if the [osc~] is multiplied by "zero", CPU usage is still
too high because [env~ 8192] is computing all the time (zero x whatever? over and over 5 times per second). Is there some method of actually 'turning-off' the [env~] or perhaps change its windows size to [env~ 131072] for example when I don't need to see the VU?
Thanks Dave S
-
David Sabine -
Miller Puckette