Just trying to help... has anybody experimenting the problem tried this trick?

- Mario

the problem is not about 100% but about the cpu using more cpu rythmicaly when you use the filter LP2 fat
as a workaround, which filter is the closest ?

Tried the nromaliser (from digitalfishphones) , but no effect, that I could discern. Still getting crackles, with that filter. Hope that helps!

I also have CPU spikes with CamelSpace 1.50.0.570 and in a lesser extent with CamelPhat 3.50.0.591.

After half a day of messing with them (in Studio One and Live) here are the facts, step by step:

A) CamelSpace LP2 Fat in S1
1. load Impact with 4 outputs (CPU 5% playing);
2. insert CamelSpace on an Fx Channel; choose an empty patch (CPU 7% playing);
3. activate MMFilter with LP2 Fat type with everything in default position (CPU 7% playing);
4. hit Stop (CPU jumps and stays at 37%; in S1 Performance Monitor with Show Devices activated it's clear that CamelSpace is the reason).

B) CamelSpace LP2 Fat and TranceGate in S1
1. load Impact with 4 outputs (CPU 5% playing);
2. insert CamelSpace on an Fx Channel; choose an empty patch (CPU 7% playing);
3. activate MMFilter with LP2 Fat type with everything in default position (CPU 7% playing);
4. activate TranceGate - with no steps in the Step Editor (CPU 38% playing);
- with some steps (CPU oscilates very fast: when it reaches a step is under 10%, when not, back to 38%);
5. hit Stop (CPU stays at 38%).

C) CamelSpace CombP or CombM in S1
1. load Impact with 4 outputs (CPU 5% playing);
2. insert CamelSpace on an Fx Channel; choose an empty patch (CPU 7% playing);
3. activate MMFilter with either Comb type (CPU 7% playing);
4. hit Stop (CPU 3%);
5. hit Play again; Cutoff and Mix stay in the default position; tweak a bit the Resonance (CPU 8% playing);
6. hit Stop - Resonance in the left part (CPU 3%);
- Resonance in the right part (CPU jumps and stays at 15%).

D) CamelSpace CombP or CombM and TranceGate in S1
1. load Impact with 4 outputs (CPU 5% playing);
2. insert CamelSpace on an Fx Channel; choose an empty patch (CPU 7% playing);
3. activate MMFilter with either Comb type (CPU 7% playing);
4. hit Stop (CPU 3%);
5. hit Play again; Cutoff and Mix stay in the default position; tweak a bit the Resonance (CPU 8% playing);
6. activate TranceGate - with no steps in the Step Editor (CPU 5% playing);
- with some steps (CPU oscilates very fast between 3% and 20%);
7. hit Stop - Resonance in the left part (CPU 3%);
- Resonance in the right part (CPU stays at 15%).

E) CamelPhat LP2 Fat or CombP or CombM in S1
Same situations as for CamelSpace but with lower values spikes and the fact that CPU doesn't stay at those peaks when it reaches them.
Here spikes appear only when I hit Stop and for a very short time.

PC: Intel Core2Duo E6750 @ 2.66Ghz, 2Gb DDR-800 Corsair, RME Fireface UC buffer 128 Samples, 24Bit 48Khz.
OS: WinXP SP3 x32.
DAWs: PreSonus Studio One Professional 2.0.3.17299 and Ableton Live 8.2.5.
VSTIs: S1's built-in Impact, replaced by Korg M1 Legacy and after that a 606 Kit Drum Rack in Live.

I've tried the above steps multiple times with the same results in both DAWs.
Note: when I say 5% or 37% CPU use, it's the maximum value it reaches at that step (VSTi + CamelSpace); usually it oscilates with -2% from the value I posted.
Last edited by e@rs on Thu Feb 02, 2012 6:50 am; edited 1 time in total

I meant to come answer this sooner. I did try it, and it made some difference. I can load CamelSpace after GNormal and have it not immediately overload; it looks like it wants to, and the CPU is quite high still on that default setting (I think that adjusting the settings on GNormal affects this, but I haven't been systematic about testing it), but I don't have to turn it off, change the preset, and restart it before using it now. Using GNormal also seems to completely fix a problem I had with at least one other plug, so thank you for the suggestion.

Thanks for the detailed post, this will be incredibly useful during testing

We will have a new beta build available soon that addresses the problem (yes, denormals ... !) once I've had a chance to test the build and make it available to download.

Peace,
Andy.

Great news. Keep up the good work.

Happy New Year!

I have CPU spikes and higher than normal CPU usage with the new version of CS, and have had since the last beta version. I reported it during the beta, and hoped it would be ironed out for release, but it is still present. (And a bummer.)

Apologies - that's my fault for having an AMD CPU. The bug doesn't happen the same way, just a very small spike that's hardly noticeable. I'll have a new Intel based PC soon, so this doesn't happen again.

Peace,
Andy.

I solved a problem with a song I'm currently working on thanks to this post. I could hardly play a certain part of the song in Ableton Live. I got a CPU spike but after a couple of bars it settled down (though still quite heavy). I went through all tracks and turned off plugins to narrow down the one that was causing the problem. I must have missed CamelSpace somehow but after reading this post I went directly to the track that's using it, turned it off and voila - it's playable again. I'm using the LP2 Fat filter btw

Hi,

Public beta versions of CamelPhat and CamelSpace are now available to download from your support account.

These updates fix the denormals problem that could overload the CPU when using the default preset or certainly filter types. The new builds are labelled:

CamelPhat

• CamelPhat Plugin v3.50.1.630 - PUBLIC BETA (Mac)
  
• CamelPhat Plugin v3.50.1.628 - PUBLIC BETA (Win 32-bit)
  
• CamelPhat Plugin v3.50.1.629 - PUBLIC BETA (Win 64-bit)

CamelSpace

• CamelSpace Plugin v1.50.1.609 - PUBLIC BETA (Mac)
  
• CamelSpace Plugin v1.50.1.607 - PUBLIC BETA (Win 32-bit)
  
• CamelSpace Plugin v1.50.1.608 - PUBLIC BETA (Win 64-bit)
  

I've tested these builds on Mac (Intel) and Windows (AMD). The minor CPU fluctuations in Live seem to be fixed, but since I was not able to reproduce the problem consistently it's difficult to say for sure. If you have time to try these new builds, please let us know how you get on, thanks.

Peace,
Andy.

A quick test and its looking good, back down to almost no cpu use on the 4bar preset. Ill try to remember to give it a more thorough run-through later today

Quick test: seems to have fixed my problem. I'll keep testing tomorrow.

Hi Andy,

Done a quick test of CS, in Studio One 2 and Cubase V6.0x, on Win XP SP3, Cakewalk UA-25EX, Intel Quad2core, with 4 GB RAM, and although the CPU useage meters seem to be OK now, I am still getting odd very fine clicks on the default patch. Not getting this when I change filter to LP2BQ. It is more like the faint clicks you used to get on a very slightly dirty vinyl, not a loud click but several faint clicks in the background - if that makes sense!! (and you are old enough like me to remember LP's!!)

Just noticed that if you drop the cutoff to under 2000Hz, the "crackles" stop! Probably makes sense to the experts!!

Hope that helps, and please feel free to email me if you need more specific information.

BW and many thanks,

Mark.

Hi,

Thanks for the feedback everyone, sounds like we're almost there.


I'm not sure if it's possible to reproduce this. There is some stepping when using the mouse to adjust the filter cutoff, but this doesn't happen with modulation / MIDI control / automation.

Does it occur if the resonance is set to 0? It could be internal clipping of the LP2-Fat filter. If you could record the output and send it as an attachment to support I can compare it to the output here.


Yes!

Peace,
Andy.