* The line6 drivers are acting very screwy and reporting thruput without anything plugged in. In 16 bit mode the measurment appears accurate. In 24 bit mode, there is some internal passthru fudging the numbers

[EDIT]
Always exact same results.
use 64 for recording and 512 for mixing. Usually audio only projects larger than 50 chanels, 24 tracks playin at once. CPU raises to 80-90% when full of fx. Very reliable.

Like Syd says below, I also run at 2.0ms/1.0ms settings for very responsive recording. I've never noticed latency recording to it, nor has anyone I've recorded with. It's not as fancy as my old motu 24IO, but since I don't do this for a living anymore, this is completely acceptable.

Last edited by themensch; 02-01-2010 at 11:23 AM.
Reason: include hardware/os specs

The first two however have not been tested under practical applications, ie- jamming.

I've currently been using ASIO 88 sample (2.0ms) buffer with fw 1.0ms buffer:
88 samples = 9.66ms
This setting is very responsive with guitar/bass/vsti so 9.66 seems a little misleading especially when compared to some of the measurements posted here.

I'd be curious to know more details from everyone regarding OS (XP32/64/ vs Vista32/64) and firewire PCI vs on-board. As always with these things, the more data the better.

i can't figure it out. at buffer of 256 it varies from 23 to 25 ms with every test --1018 to 1160 samples. i've gone through and shut down every device and service until the computer was totally crippled and still it has no effect.

i can't figure it out. at buffer of 256 it varies from 23 to 25 ms with every test --1018 to 1160 samples. i've gone through and shut down every device and service until the computer was totally crippled and still it has no effect.

even tried on 3 different computers all with similar results.

Is this somehow interface-related? Some are giving "stable" results and others don't, but they still work "as expected"?

Not to be a bother but i don't see how this is helpful. Doesn't latency change on everyone's system and even at different sample rates?
Heck I've even gotten varying latencies at the same sample rate. Is this just to give people a rough idea of the latency that you might get with that soundcard?

Not to be a bother but i don't see how this is helpful. Doesn't latency change on everyone's system and even at different sample rates?
Heck I've even gotten varying latencies at the same sample rate. Is this just to give people a rough idea of the latency that you might get with that soundcard?

not only the latency but the stability of the latency and consistency of the same interface in different systems. i'm wondering how daw's (reaper included) handle latency compensation for unstable interfaces.

not only the latency but the stability of the latency and consistency of the same interface in different systems. i'm wondering how daw's (reaper included) handle latency compensation for unstable interfaces.

I'm guessing that the asio drivers would have to keep reporting the new latency to the host. Not sure if the asio reported latency remains fixed or changes. To me if this is not the way asio drivers work currently then I think adding this would be a good way to make sure that the correct latency is properly compensated for even in unstable interfaces. Anybody in the know wanna chime in?

Since this comes up so much I thought I'd make a sticky and hopefully that will help for buying cards and such

it is perhaps also good to know that latency and other issues will differ depending on whether you are using a laptop or not. (esp. with pc's) >>>laptops use acpi to check the battery and that service causes dropouts as well as added latency. also, having wifi enabled adds latency. i have found that users' desktops almost always coast in comparison to what their laptops do.

if you are using a laptop, run your latency checking program (such as dcplat.exe) and go into your devices and disable acpi battery method and study the difference.

this may not work for everyone, but give it a try if you haven't already.

You are maybe confusing DPC latency with audio latency. There is only a faint connection between these two as in "raising ASIO buffers may or may not help avoiding dropouts due to DPC related usurpation of the CPU".

Quote:

Originally Posted by reapercurious

>>>laptops use acpi to check the battery and that service causes dropouts as well as added latency.

Not laptops in general. Some models suffer from this, others don't. It's also not always the ACPI battery services causing DPC problems in laptops.

Quote:

Originally Posted by reapercurious

also, having wifi enabled adds latency.

These problems are not confined to Laptops, some desktop PCs have problems with DPC latency as well. This is a rather complex issue and generalizations are not possible since the culprit can be a lot of things from faulty hardware to bad BIOS implementations and of course drivers.

d.gaus,
on my tests the sample size is allways the same. maybe there is a driver issue with your device since your sample size seems to be oddly high varying from 1066 to 1114 @ 256 samples where on my system it reports constantly 513 samples. In all the tests at any sample size and sample rate the measured sample size is allways close to twice the tested sample size where yours is allmost four times the sample size ... how are your dcp latency results ?

on my tests the sample size is allways the same. maybe there is a driver issue with your device since your sample size seems to be oddly high varying from 1066 to 1114 @ 256 samples where on my system it reports constantly 513 samples.

yeah, this isn't good. i hooked up a mackie onyx firewire mixer and the results were rock solid (see below). echo hasn't been much help yet. and all this time, i thought the audiofire was stable/reliable?