Page 1 of 1

Posted: Sun Feb 03, 2002 2:17 pm
by glockh210
a call out to subhuman. yet another issue all my music apps are sounding great. Low latency in everything except cubase when playing a VST instrument in real time about every four seconds a whole lot of static fuzz rears its ugly head. Not sure why thought you might help. no sign of this in reaktor or reason in real time just cubase. thanks in advance

Posted: Mon Feb 04, 2002 8:07 am
by glockh210
Uhm. anyone can respond to this if they have a suggestion. thanks... Subhuman has just helped alot in the past so /// any takers?

thanks

Posted: Mon Feb 04, 2002 10:24 am
by subhuman
What do you have your ULLI set to now? When you get the noise inside Cubase, how many audio tracks do you have in your project - or is it just the VST instrument?

Finally - which VST instruments does this happen with?

Just need a little more info before I can take a stab at this one...

Posted: Mon Feb 04, 2002 2:29 pm
by glockh210
thanks for the reply! the ULLI setting that I am getting good results with (except vst instruments) is the (44,1 Khz 7ms). If I increase this the static during VST use goes away yet I also lose good latency and my other music apps (like media player) are scratchy. this setting works well for everything else. I am getting this with any VST instrument I try, ones included with cubase as well as third party plug-ins.
Thanks

Posted: Tue Feb 05, 2002 9:04 am
by subhuman
Which ASIO drivers are you using in your Luna project? You might try the basic ASIO2 module, with only as many channels as you need... the 64 channel ASIO2 taxes your system more, and if you're not using the channels, no need to have them...

Posted: Wed Feb 06, 2002 6:06 am
by glockh210
It happens just using the "ASIO Dest" module with 2 channels. And most recently I'm getting errors from Cubase that I can't open the instrument interface to edit and that an error has occured in cubase and it has to shut down. when this happens though cubase is minimized and I can't get to it to close it properly the error just keeps reappearing and I have to close it via ctrl-alt-del. losing everything I've been working on! Do cubase and Luna ever work well together? Not the case here.

Posted: Wed Feb 06, 2002 10:09 am
by subhuman
ULLI settings below 13ms are not guaranteed - they are host dependant - if you have a well optimized machine that is 500mhz or more, then 7ms is very likely, maybe less depending on your system load.

A few examples: My old 933mhz CUSL2 system worked at 7ms reliably, occasionally with low track counts 4ms (and before that a 366 @ 550mhz Celeron worked well at 13ms ocassionally 7ms), even with VSTi's and audio channels running. Never a glitch. It was setup properly and I never had problems, never touched it once I got it running. It is still running reliably, now for well over a year - I only applied my GHOST image for a clean start when one of the local studios bought it from me.

Different versions of windows also provide different performance. Win2k is probably the worst I've used for audio, WinXP is better due to I think must be better drivers (ACPI is definitely better on XP for example), media limitations of devices have been removed (eg # wave drivers). WinME doesn't work too well until you make sure System Restore is removed or at the minimum, disabled.

The main point is yes, this does work well and without problems with the proper hardwdare and software setup. I don't know enough about your hardware/software configuration to fix it, nor how long it's been since you've reformatted or what programs might be lingering on your HD.

The top list for getting lower ASIO latency:
1. Creamware card must not share an IRQ with anything (IRQ steering okay).
2. No background programs should be running, if running 2k/XP, many of the background services should be disabled or turned off. Anything that occasionally grabs CPU, including screen savers, etc.
3. Proper chipset/IDE drivers should be installed

If you have problems at lower latency, and believe that you've gone through all the optimizations you can find, it could just be a limitation of your current install of Windows or your computer's hardware.