I have a DSP chain. It begins with pitch tracking with sigmund~ and then a series of abstractions follow that have a switch~ in each, controlled by polygate~ output (i.e. once I switch off an abstraction in the chain, polygate~ sends a zero to switch~ in that abstraction. Vice versa. It works well.

The problem. When I load the patch and switch~ on the 6 instances of sigmund~ (which is generally CPU heavy in itself, but I have never had a problem with it until now) the CPU rises to around 90%, whereas before redesign of the chain (I've replaced a few abstractions which may be a little more CPU intensive, but not much), the CPU was barely over 50%.

The weird thing. When I switch ON the rest of the DSP chain, the CPU drops to 70% (which is where I would expect it to be).

My question(s). What the hell is going on? Why is sigmund~ wetting the bed before the rest of the chain is on? Is my computer having a crisis?

Cheers,

Ricky

p.s. Abstractions are not in parent patch.

Do you have any [vline~]s in the switched-off abstractions that are still being triggered? For whatever reason they seem to build up some anger if you keep sending them messages with DSP off, and then they just let it all out when it's turned on. It's a good idea to use whatever is turning off [switch~] to also close a [spigot] going into [vline~].

Ha. I like the idea of an angry [vline~] object. That may make the next conf/conv t-shirt design Good to know man. Thanks for the info, looking into it now.

yeah, we can expect to see "The Angry Vlines" headlining some big festivals soon.

Seems to have made a difference, thus far. Thanks .mmb.

Or rather..

V
line
~