S
A
ambi
New member
What is a bad thing? high numbers?
Stealthtech
LOGIC ABUSER
ambi said:
On Latency ?? YES
MS=milli second delay
A
aschek
New member
I have the Tascam us428, it's being rated here as 10ms on a pIII-700 with 128 ram and win2000...
I have a p4-2Ghz, 1Gb Ram and WinXP-Pro.... can I expect less latency ??? Is this latency thing a soundcard, driver or computer problem ?? If it's a combination, where is the biggest bottleneck?
THanks !
Alex
I have a p4-2Ghz, 1Gb Ram and WinXP-Pro.... can I expect less latency ??? Is this latency thing a soundcard, driver or computer problem ?? If it's a combination, where is the biggest bottleneck?
THanks !
Alex
B
Bigus Dickus
New member
Wow, my M-audio delta is 1 ms? Oh... and it says the buffer sample size is 64. The default in the driver control panel is set to 384 samples (DMA buffer). Should I reduce that to 64?
A
ambi
New member
Hmm. I was looking at the aardvark q10, i think the quality is on par if not better than a delta 1010, is that correct?
moskus
The Creator of Æ, Ø and Å
That looks like the table from Computer Music... well I don't entirely trust these quys when it comes to latency.
Slackmaster2K
Gone
Latency numbers like this are really meaningless, and only give you an idea of the *potential* minimum latency of a card on a specific system.
I guarantee that you will not work on more than a couple tracks, if that, if you've configured your system for 1ms of latency. In fact, if you plan on working on typical 16+ track projects, your latency will typically be around 50-60ms, and that's fine for mixing.
The only time latency is a serious issue is when you're doing live input processing...that is, applying effects WHILE recording. If you're not doing this, don't worry about it. You should adjust your buffers such that you can work without a lot of dropouts. If you are doing live input processing, then you'll have to work with smaller submixes for it to be feasible. As a rule, you'll need to get your latency down to under 10ms for the delay to be nearly unnoticable. On most systems, getting latency values that low will require that you seriously limit the number of tracks and effects you're working with (hence using submixes).
Slackmaster 2000
I guarantee that you will not work on more than a couple tracks, if that, if you've configured your system for 1ms of latency. In fact, if you plan on working on typical 16+ track projects, your latency will typically be around 50-60ms, and that's fine for mixing.
The only time latency is a serious issue is when you're doing live input processing...that is, applying effects WHILE recording. If you're not doing this, don't worry about it. You should adjust your buffers such that you can work without a lot of dropouts. If you are doing live input processing, then you'll have to work with smaller submixes for it to be feasible. As a rule, you'll need to get your latency down to under 10ms for the delay to be nearly unnoticable. On most systems, getting latency values that low will require that you seriously limit the number of tracks and effects you're working with (hence using submixes).
Slackmaster 2000
Seanmorse79
New member
How would this compare to virtual instrument (VSTi) latency?
My C-Port shows 6ms on this chart, but I've never been able to get anything remotely useable (usually about a second and a half).
I usually have to patch the audio output of my keyboard into the cans for tracking, but it'd be really nice to hear the VSTi's output instead because it really affects the feel of what I'm playing.
My C-Port shows 6ms on this chart, but I've never been able to get anything remotely useable (usually about a second and a half).
I usually have to patch the audio output of my keyboard into the cans for tracking, but it'd be really nice to hear the VSTi's output instead because it really affects the feel of what I'm playing.