Can anyone tell me the version of VST that Blue Cat Audio is presently using in their commercial plug-ins? Compared to the average, How do Blue Cat's VST plugz do with CPU utilization?
Thanks,
-Mark
Latest VST version and CPU Utilization
-
- KVRist
- 280 posts since 4 May, 2007 from New York
Intel Bad Axe 2 Mobo, Core™2 Quad 2.4GHz Q6600 CPU, 4GB Corsair SDRAM, Nvidia GeForce 8800 GT, PreSonus Firestudio Mobile audio interface/sound card, 4 Seagate 320GB 7200.10 HDDs. Powered KRK V4 Monitors.
-
- KVRian
- 1290 posts since 13 Mar, 2007
I have tested the dynamic plugg in wavelab6 and found the normal mode used about 8-14 % (according to WL). Tha 4x oversampling took it to 28-34%. my machine is 2.8 mhz P4 W/ 1gb of ram. Hope it helps. I found the pluggs to run smoothly and are pretty inovative when you get into the midi cc capabilities, I'm not sure which version of the VST standard the programmer uses ; but I'm sure it's probably up to date as he seems to be good at this stuff!
My $.02 !!
My $.02 !!
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 6343 posts since 8 Sep, 2004 from Paris (France)
Hi,
Thank you for your interest in our products.
today we implement the VST 2.3 standard, as the 2.4 version does not provide many improvements and the new 3.0 should be released this year. This is also a way to avoid breaking compatibility with most hosts.
Regarding CPU consumption, our policy is to create scalable products which only use the CPU they actually need for the settings you choose. It means that with most common options they usually do not use much CPU (most of them are below 7%), and when you switch everything on it can increase a bit, or sometimes a lot (the Blue Cat's Dynamics product is a good example of "hardcore" usage when pushing the oversampling to 4x, which is usually not needed in most cases, especially in real time). This allows you to really optimize your CPU power for your exact needs. Note that when the plug-ins are fed with silence, no processing occurs, which helps you save a lot of CPU in a multi-track environment.
Thank you for your interest in our products.
today we implement the VST 2.3 standard, as the 2.4 version does not provide many improvements and the new 3.0 should be released this year. This is also a way to avoid breaking compatibility with most hosts.
Regarding CPU consumption, our policy is to create scalable products which only use the CPU they actually need for the settings you choose. It means that with most common options they usually do not use much CPU (most of them are below 7%), and when you switch everything on it can increase a bit, or sometimes a lot (the Blue Cat's Dynamics product is a good example of "hardcore" usage when pushing the oversampling to 4x, which is usually not needed in most cases, especially in real time). This allows you to really optimize your CPU power for your exact needs. Note that when the plug-ins are fed with silence, no processing occurs, which helps you save a lot of CPU in a multi-track environment.