One instance of Corpus maxes out CPU load when dry/wet = 0

[mwbrock]

Processing any audio through Corpus with dry/wet set to 0 maxes out my CPU usage after 5-10 seconds, causing audio dropouts and system freezes. This is with single-track projects, and synths or clips that only use <5% of CPU power themselves.

For example:

1. Open new live set
2. Load a clip into an audio track in session view. Make sure it's set to loop.
3. Load Corpus onto same track, keep settings at default (dry/wet at 0)
4. Play the clip
5. After ~5-10 seconds, CPU usage spikes to 100 and audio glitches.

The same happens if Corpus is on a midi track after a synth (with sustained playing of even one note), or when an audio track is armed with an external input selected.

The really weird thing is that this only happens with the dry/wet at 0. If I turn up that knob up before I start processing audio through Corpus, no problem -- cpu load stays around 5%. If I turn dry/wet back down to 0 when audio is playing thorugh, the CPU spikes.

I'm trying to determine if there is a dependence on the resonance type (beam vs string). But for any type, cpu usage is higher with dry/wet at zero, which seems counterintuitive/buggy.

Collision is CPU-heavy for me (20-40% sometimes), but never causes these spikes to 100%. My system isn't the newest out there (3.6 GHz P4, 1G RAM), but this seems like buggy behavior.

Cheers,
Mat

[Angstrom]

strange, I reported this bug ages and ages ago.
still there eh.

[db91977]

Yes- Alex @ Ableton mentioned this in the 8.0b9 announcement at
http://forum.ableton.com/viewtopic.php?t=107357 --

Known issues:
....
The Windows version of Corpus still has a bug which result in a heavy CPU usage when dry/wet is set to 0.

[mwbrock]

Whoopsy. Sorry to waste bandwidth. Will do a more exhaustive search next time . But, yes, the bug still there.

Cheers,
Mat

[Amaury]

Hi,

This is fixed for a while now. I moved the thread away, please create a new one if you experience other problems.

Regards,
Amaury