Cubase SX Overload !!!

Bonkuz · May 29, 2003, 11:15 AM

I have a problem with Cubase SX and the kX Drivers I think?

The problem is:
My current project contains 14 tracks:
1 MIDI Atmosphere
7 audio Amplitube
6 no FX audio

The funny thing is when the song is recently opened ewerything goes great, the VST performace
is on alow lewel. But after a while Cubase runs out of VST performance and gets overloaded, EWEN if i dont do anything!
Slowly the VST performance meter goes up to maximum without doing anything, the onlything I've done is
to open the god damned project.

When VST performance meter goes up to maximum and I start playing the song, there's cracks and pops in the beginning,
BUT the more audiotracks playing at the same time, the VST performance meter goes down again to 20% and ewerything
sounds great!.....shouldnt it be the other way around? the more audiotracks and fx playing, less VST performance

I run the kX 3533 drivers, latency 5 ms, Win XP

XP is set to ACPI computer!...read that this isnt to good when working with audio?
Anyway, is there a way out without having to reinstall XP if thats the issue?

THANX TO THE GUYS BRINGING THE kX DRIVERS TO THE WORLD!!! CREATIVE SUCKS!

Daniel Drummond · May 29, 2003, 10:14 PM

Increase latency to 20ms and see what happens.

Bonkuz · May 30, 2003, 06:33 PM

Done that...no change!...problem remains!

I´ve expected better performance from my new
computer and soundcard, maybe I got to high expetations?

Anyway, I still thing that i can squeeze more performance out of my
computer with the right settings.

Seems to be somce kind of memoryleak or something, due to my previous
explained problem???

NOTE! I have installed "win XP SP2 Build 2600 only for testing purposes" realese,
but I dont think that should be the problem....?

surealsurrender · Aug 6, 2003, 08:01 PM

I don't own a P4 processor myself but I have done a little reading about the P4 Denormalizing problem with FX plugins... try turning off all your FX plugins and see if the problems still exists... if not it is very possibly a denormal problem and there are solutions for you on the Net, just jump on Google and search for p4 denormalizing...

Good Luck

Sur

scottdru · Aug 8, 2003, 07:18 AM

That would be my guess too. Sounds like you are getting a CPU spike due to the denormalisation function of your processor. All CPUs do this, but the P4 goes into denormalise mode quicker than some of the other CPUs.

Are you using the latest versions of your software/plugins, etc.? Most of the major plugins, VSTis and sequencers have been updated to be optimised for P4s, and you can get the updates on the site. But, if you are using cracks or freeware that isn't well supported, you may be out of luck.

But, as the previous poster mentioned, there are a few options that may work. There is a very good article on denormalisation here.

If you find this is not the problem, there is a very good PC Music FAQs section here at the Sound on Sound forum, and this is a very good source (one of the best, IMHO) for learning how to tweak your computer for the best possible performance for audio.

Hope that helps.

guitarre · Aug 12, 2003, 01:57 AM

This is a problem with amplitube...
it strangely boosts the cpu usage when there's no sound in its input. However as long as it detects a sound, the cpu usage turns to normal. And with 7 amplitubes doing this, it's highly possible that it overloads your cpu...

scottdru · Aug 12, 2003, 12:16 PM

Yep, that's denormalisation then. The best solution is to got to the AMplitube site and download any updates or patches that are available, as one of them surely must optimise amplitube for P4. Should you not have this option (for some reason), the second best thing to do is to insert a dither plug-in into the effects chain ahead of Amplitube. This will keep at least some noise (though inaudible) going through the path, and will prevent the P4 from going into denormalisation mode. Again, you can read about this in the article I posted the link to above.

Hope that is helpful.

Scott

ACIDman · Aug 22, 2003, 11:27 PM

Hmm..Have same problem with my Athlon 1200+.. Everything goes normal if I turn off amplitube.. I'll go look for some updates and tell u if that will work..

Bonkuz · Aug 23, 2003, 09:29 AM

Updated to Amplitube v1.1 and ewerything is OK now, thanx for all the help!!

ACIDman · Aug 23, 2003, 08:24 PM

Still have the same problem ... I downloaded the last version (1.2.0 - just to test) and nothing changed ...