its called cubase.. your problem i mean...

when i was thinking of moving to cubase i did the test with the same audio driver and the same vsts etc... cubase had atleast 15-20% more cpu usage than fl. live and sonar had 5-10 more i think.

But it's strange because in FL, increasing the buffer on the ASIO4ALL control panel will stop clicking and popping. I usually don't hear that in FL until my CPU gets to around 90% anyway. That's what makes me think there must be something else wrong here. Even doubling the buffer size make no difference. It still crackles along.

-Heather

The CPU performance thread (linked to in the FAQ):

http://www.tranceaddict.com/forums/...&postid=5282717

As I mentioned in reply to your other post, make sure you've actually got Cubase configured to use the correct ASIO driver. By default it selects Steinberg's "virtual" ASIO driver.

___________________
My party schedule:
2009-02-21 - DJ Attention @ I'm So Popular
2009-06-18 - DJ Annoying @ People Need To Know Where I'll Be
2012-11-32 - DJ Insufferable ɸ Or At Least the Stalkers I Complain About
2048-06-66 - Spastic & Whocares ¶ Although I'm Actually Flattered
9999-45-81 - Tweaker Gimp ☼ I Probably Won't Even Go To This But I Have To Make Sure I Fill Up All The Available Space Here

You can also try this. Device > Device Setup > VST Multitrack > uncheck direct monitoring, click on expert > set audio priority to very high and preload amount to 6 seconds. Also make sure lower latency is unchecked. That should help you get the most out of your CPU but when you have a ton of instruments and fx eventually you will have to set the audio priority back to normal cuz your computer will get too slow. That is when it's a good idea to start bouncin tracks down to audio.

how many channels of battery are you running?

how many inserts do you have on v-station and battery?

i've done a good number of tunes where i've only got 4 vst's open, but is at 70% when standing idle because of all the inserts and fx i'm running.

the clicks and pops can almost completely cured by simply raising your audio buffer to around 256 samples.

what spec is your pc?

___________________
Lets f**king ave it!

I'm comparing the exact same instruments, effects, vst's, midi patterns, etc on FL Studio and getting 15% CPU use. That's my issue. My specs and the details about how many I'm using of each thing don't matter because on FL it's fine. But if you must know - one instance of battery with one kick sample and a Waves C1 compressor as insert. 2 Instance of V-Station each playing the same riff with two different bass patches and the kick and bass routed to a group track to be compressed with another C1 compressor. That's all folks. Definitely not enough to use 50-60% of my CPU. I'm getting a new sound card. I am using the ASIO4ALL drivers and increasing the buffer does not work. I must assume Cubase does not like my soundblaster live.

there's definitely gotta be something wrong with the actual version of cubase that you have. on very rare occassions i use sx3 on a personal pc that has a soundblaster live as well and i've never had any problems with doing work on it.

quote:

Originally posted by 4am I'm comparing the exact same instruments, effects, vst's, midi patterns, etc on FL Studio and getting 15% CPU use. That's my issue. My specs and the details about how many I'm using of each thing don't matter because on FL it's fine. But if you must know - one instance of battery with one kick sample and a Waves C1 compressor as insert. 2 Instance of V-Station each playing the same riff with two different bass patches and the kick and bass routed to a group track to be compressed with another C1 compressor. That's all folks. Definitely not enough to use 50-60% of my CPU. I'm getting a new sound card. I am using the ASIO4ALL drivers and increasing the buffer does not work. I must assume Cubase does not like my soundblaster live.

btw get the kx project asio drivers... i had to get an m-audio audiophile to see how good soundblaster is with these drivers... seriusly youll have 5ms latency with 70-80 cpu. with no clicks...

I'm still assuming that you haven't configured Cubase to use the correct ASIO output, because you still haven't answered that question.

It makes absolutely no sense (and I mean none) that you'd be getting overloads in Cubase but not FL if they are both using exactly the same driver. There are no application-specific functions in the ASIO implementation that would cause that to happen. And Cubase is known for having better VST performance than any of the other sequencers, which is no surprise given that Steinberg created the VST standard.

I'm 90% sure that you've configured something incorrectly in the program. However, if you can "downgrade" your copy to version 2.2, I would seriously suggest it because version 3 is known for these types of random, silly problems.

___________________
My party schedule:
2009-02-21 - DJ Attention @ I'm So Popular
2009-06-18 - DJ Annoying @ People Need To Know Where I'll Be
2012-11-32 - DJ Insufferable ɸ Or At Least the Stalkers I Complain About
2048-06-66 - Spastic & Whocares ¶ Although I'm Actually Flattered
9999-45-81 - Tweaker Gimp ☼ I Probably Won't Even Go To This But I Have To Make Sure I Fill Up All The Available Space Here

Thanks Diginut, but since I said I had increased the buffer on the ASIO control panel, I thought you knew I was using the ASIO4ALL driver in the device setup. I'm certain I've selected the correct driver but something not being configured correctly might still be an issue. I'll play around some more tonight. I'll try KX ASIO drivers too.