Nov 17, 2004 09:32 am Yes Topman I did.
I am supprised that you are experinecing it with a 2G processor. Ozone pluged into Cubase SX 1.xx over-ran my 850mhz processor resulting in clicks, staggered response, and finally lock up especially if I tried to use the verb. I am ok now with a pentium 4 2.4G, 2G mem machine. It is a function of inadiquate bandwith interupting the streaming.
Things to check:
Monitor your processor. If it is being maxed out, check out the services and background tasks that you are running in XP. dB has a fine article on services that can be illiminated if necessary.
Hopefully you have the vst version of Ozone as opposed to direct-x. The vst version will play a little better with Cubase than dx.
Hopefully your hard drive is 7200 rpm and udma. Cubase w ozone does not constantly access the drive as most of ozone is processor math, but when it does it wants the data NOW. A second hard drive for just song data is always a great idea. Definately defrag your hard drive(s). This makes a huge difference.
You can also take a peek at memory usage. I did not experience Cubase/oz using a lot of memory as everything is "real time" streaming for the most part, although a G of memory is what is recomended.
Lastly, (now there's a word) I did find that the tech support at ozone are very good. Got back to me by phone in very good time and followed up via e-mail.
Oh, just hit me. I am making one assumption that I am aware of. I am assuming that you are mixing down your song, then bringing it back into the mastering template as an interleaved stereo track and applying ozone. If you are attempting to apply ozone as a mastering effect at the mix stage with numerous other plugs working as well... you can see where I am going.
