Heavy cpu spikes with VDM and Studio 1...

[thebdp]

Is anybody else having this issue? It's really a bummer cause i love the sounds in the VDM but it's hardly useable for me at the moment due to all the cpu spike i get. 

I'm running a 24" intel imac duo core with 4gb ram and an Echo audiofire as my interface.I use the Padkontrol to trigger the vdm btw. while i realize that this isn't the ideal machine for recording, i honestly don't have too many issues with other 3rd party instruments... I picked up the V-collection recently and have had issues with some of the other instruments in there as well, but not nearly as bad as the VDM.

As always, any help is much appreciated.

[Kevin]

Hi,
are you using VDM in a DAW?
If yes, do you have same problems in standalone mode?

Kevin

[thebdp]

Ya, as it says in the post title  ... all kidding aside, I never use it in stand alone mode although i had it running in standalone for a bit earlier and didn't see much cpu activity. It's pretty bad in Studio One.

[Kevin]

Sorry I was reading at the post when answering and did not check the title.
Can you tell me the sample rate and audio buffer size you are using in Studio One?

[thebdp]

I typically switch between 256 and 512 samples at 44.1 khz.

[mpc60champ]

stick to 512 sample buffer. Are you using the asio4all driver? I am running asio4all in studio 1 with 512 sample buffer and spark CDM and VDM work fine even if I am doing a ton of filter sweeps and automations.

[vaikl]

stick to 512 sample buffer. Are you using the asio4all driver? I am running asio4all in studio 1 with 512 sample buffer and spark CDM and VDM work fine even if I am doing a ton of filter sweeps and automations.

ASIO4ALL is not for Macs and is not made for "speeding up" something. It's just a bridge between very old and crappy Windows audio frameworks and the ASIO drivers for pro equipment.