S3 AVB interface LATENCY is a problem..

[propower]

A direct monitoring path (with Reverb comp and EQ - on a mini HDX card even) summing to the outputs and HP would have been a great feature for this.

[ronnievanoverveld]

Interesting responses here! Like I said, I didn't check the latency really long, I plugged in a microphone and recorded it in Pro Tools. During recording I didn't mention that much latency. Alhough it was speech only, so maybe it's harder when it's used for Music recording..

Other point; are there users here who upgraded the AVB IO with another AVB unit? Curious if it works and if there are some high quality options...

[kriszuki]

ok, another issue has come up with using the mic pres. So if the latency to monitor the pres is too high for music recording, an option would be to utilise the pres by sending the signal analog out of the s3 and send it to an interface to do the A/D duties with low latency.

but when I assign the analog outs 1+2 to main outs it automatically disables 48phantom power and enables the pad. doh. Why is this an automatic setting?
can this be over-ridden?

[kriszuki]

Hi, any Avid people here with an answer to this? -

"when I assign the analog outs 1+2 to main outs it automatically disables 48phantom power and enables the pad. doh. Why is this an automatic setting?
can this be over-ridden?"

Be great if I can get an answer about this, it is not documented in the manual.

[Amack]

You might find this process useful for measuring your latencies and PT's RTL compensation error http://duc.avid.com/showthread.php?t=368814.

Originally Posted by kriszuki

Yeah that looks like the logical way forward. I just wanted to maximize my investment in the S3 and not buy an extra interface.

[kriszuki]

good idea, i will do that and report back

[kriszuki]

So if i have done this correctly I measure a latency of 8.125ms.

method:

Send a pip out of OUT 3 from pro tools, patch the S3 OUT3 into the S3's IN3.

Record the pip and measure the delay in samples between the original pip on the timeline and the recorded one. The result was 390samples, at 48khz that is the sum 390/48 = 8.125ms.

[Amack]

If that's all you did, it sounds like your PT RTL compensation error is 8.125 ms - not so good! Does "patch" mean connect interface Out3 to IN3 with a cable.?

Originally Posted by kriszuki

So if i have done this correctly I measure a latency of 8.125ms.

method:

Send a pip out of OUT 3 from pro tools, patch the S3 OUT3 into the S3's IN3.

Record the pip and measure the delay in samples between the original pip on the timeline and the recorded one. The result was 390samples, at 48khz that is the sum 390/48 = 8.125ms.

[kriszuki]

Originally Posted by Amack

If that's all you did, it sounds like your PT RTL compensation error is 8.125 ms - not so good! Does "patch" mean connect interface Out3 to IN3 with a cable.?

Yes patch with a trs jack cable between the physical output to input.

[kriszuki]

I have been reading up on Motu's AVB products and it seems though Apple's drivers are not up to par with the potential of AVB, ie once Apple's drivers improve the latencies will get better.

Anyone at Avid here that can comment on the S3 AVB interface in relation to this?

Or anyone using S3 as an audio interface?