have been over at
www.kvraudio.com speaking with my friends at camelaudio ...
McLilith wrote:Hi pHz,
I'll look into this.
I'm not aware of any denormal problems in Cameleon.
Does it still consume lots of CPU if you close the Cameleon GUI and continue to play Cameleon with the GUI closed?
Can you give me any actual statistics for the CPU usage?
It would also help to know what speed and type your CPU is, which Cameleon preset you were playing when this happened, and how many notes you are holding down when you make your CPU measurement. All of that is important to know when evaluating your CPU usage.
take care,
Glen
Camel Audio Tech Support
GUI open or closed makes no difference ...
... track i was working on running at about 35%-40% according to live 5 CPU meter ... after a while (maybe 20 seconds or so) of cameleon coming in it goes 60% > 90% > 125% over the course of about 10 seconds ...
... 3.2Ghz p4 laptop ... happended initially with the
ober basstrings patch ... switched to
prophet brass but still the same phenomenon ... have tried lots of other patches and seeing the same effect on
most of them (some bass patches seem unaffected) although not always to such an extreme degree ...
... no more than 3 notes played (dropping cameleons polyphony down has little effect BTW)
Ben [Camel Audio] wrote:Hi pHz,
I´m not aware of any issues with Cameleon under live. However, as is noted in the manual and on the email when you purchased Cameleon, it does cause much higher loads for very low buffer sizes. Try raising your buffer size to 256 or 512 samples, and see if this solves the problem. For further details, please refer to the Cameleon FAQ on the support page.
Thanks
Ben
soundcard buffer size was already 256 ... have tried it up at 512 and even 1024 with little effect ... have also tried playing with the live 5 internal plugin processing buffer and that makes little difference too ...
... given the fact ive done a fair amount of testing for various devs over the last few years ive tried all the things i would normally do to track this problem down already ... hence my perplexment ...
... stripping down the arrangement to just the 4 elements playing at the time has no beneficial effect either ... ive also duplicated the setup from live in tracktion 2 without seeing the spikes (general CPU use on the track is comparable at about 30%-35%) ...
... i thought it might be occuring at the junction of 2 different MIDI clips but merging them made no difference ... i thought it might be due to me clicking around in live to change the playback point while the engine is running but leaving the track to play through gives the same result (and clicking madly around in tracktion 2 during playback doesnt cause the spikes anyway) ...
... having just spent another 2 1/2 fruitless hours on this im inclined to think its either unique to my setup and ill have to live without cameleon when using live 5 or that theres just something about the way cameleon and live interact thats causing this ???
slainte
rob
rob