Audient EVO 16 - Experiences

Talk about your MIDI interfaces, microphones, keyboards...

Moderators: MattKingUSA, khz

cupakm
Established Member
Posts: 33
Joined: Thu Aug 16, 2012 8:24 am
Has thanked: 2 times
Been thanked: 3 times
Contact:

Re: Audient EVO 16 - Experiences

Post by cupakm »

icaria36 wrote: Wed Sep 06, 2023 8:02 am

No, but I can measure it if someone tells me how to (big plus if there is an Ubuntu package).

Thanks! You will need a loopback cable - connect physical output with a physical input. For example take a jack-jack cable, insert into Mic/Line input 8 and Line output 8.

Then there are two options:

1) Ardour - when starting up, usually Audio/MIDI Setup window opens, choose Audio system "ALSA", Input device Evo16, Output device Evo16, Sample rate 48 kHz, Buffer size as low as possible without getting sound artifacts, Periods 3. (You may want to experiment with sample rate, buffer size and periods and see how they change the latency); then -> Advanced settings -> Calibrate Audio -> Playback channel choose Line Output 8, Capture channel choose Mic/Line Input 8, then click Measure button. After a brief beep-tone you'll get systemic latency and round-trip latency (RTL) in [ms]. Let us please know the numbers :)
Then you may want to go ahead and use your measurement to let Ardour compensate the latency.

Note the the actual number of Input / Output Latency samples may change when you reconnect the interface.

2) JACK only - let me know if the above mention won't work, this one is I think less convenient and can result in a tad bit higher RTL

icaria36 wrote: Wed Sep 06, 2023 8:02 am

Chipset, do you mean my PC's processor?

No, your USB controller's chipset. That one where you connect the Evo into. For example Renesas uPD720201:

Code: Select all

marek@desktop:~$ lspci | grep Renesas
03:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03)

...or Fresco, Intel, AMD, VIA...

icaria36
Established Member
Posts: 14
Joined: Sat Jul 01, 2023 9:56 am
Has thanked: 9 times
Been thanked: 3 times

Re: Audient EVO 16 - Experiences

Post by icaria36 »

Thank you. I have checked some combination, without really knowing what I'm doing. Following instructions. :)

32 samples
Detected roundtrip latency: 255 samples (5,312 ms)
Systemic latency: 159 samples (3,312, ms)

2 periods: 223 (4,646) & systemic 159 (3,312)

64 samples
375 (7,812 ms)
183 samples (3,812, ms)

96
472 - 9,812
183 - 3,812

128
567 - 11,812
183 - 3,812

192
759 - 15,812
183 - 3,812

1024
3255 - 67,812
183 - 3,812

3256 - 67,833
184 - 3,833

2 periods: 2232 (46,500)

USB controller: Intel Corporation Alder Lake-S PCH USB 3.2 Gen 2x2 XHCI Controller (rev 11)

I'm curious about why you ask and what does this data tell you. :)

cupakm
Established Member
Posts: 33
Joined: Thu Aug 16, 2012 8:24 am
Has thanked: 2 times
Been thanked: 3 times
Contact:

Re: Audient EVO 16 - Experiences

Post by cupakm »

icaria36 wrote: Sat Sep 09, 2023 11:03 pm

I'm curious about why you ask and what does this data tell you. :)

Thanks a lot!

What the data do tell us:

  • Evo16 can go for very low buffer size (32 samples)
  • it achieves sub 6 ms round-trip latency, around 5-ish. One most probably could comfortably record overdubs even without Ardour's latency compensation.

USB controller: if you're still curious whether you could squeeze even lower RTL, you may want to experiment connecting the interface to other USB controllers. Ideally reserve one USB controller for the interface only, so no other USB device could interfere. In case of a PCIe expansion card with multiple ports and a single controller (for example one offering 4x USB 3.1 port per controller), you'd connect only the interface and nothing else to that card. Trying out another controller will vary the results.

Even simpler method how to further lower the latency (but increase computing requirements) is using higher sample rate. I suppose you did the measurements at 48 kHz. Try doing the same at 96 kHz.

What could be interesting too is measuring RTL in stand-alone mode, which would mean connecting it via ADAT ports to a host interface and measuring latency of both host and Evo16 through that host, and subtracting the host's latency. Why would one do that? To see how much latency will be added expanding another interface. I guess Evo SP8's latency would be pretty same, as I suppose they're internally almost identical, but this is only my speculation.

Anyway, given you did not notice any sound artifacts, pops, noises, etc. on lowest RTL settings -and- cost of the unit, I would deem the interface's latency quite usable.

Last edited by cupakm on Tue Sep 12, 2023 6:50 am, edited 2 times in total.
icaria36
Established Member
Posts: 14
Joined: Sat Jul 01, 2023 9:56 am
Has thanked: 9 times
Been thanked: 3 times

Re: Audient EVO 16 - Experiences

Post by icaria36 »

Thank you very much, I'm impressed with this knowledge!. Since I'm happy with the performance of my setup, I won't touch anything. The only one lagging and making cracking noises in my studio is... me. :D

cupakm
Established Member
Posts: 33
Joined: Thu Aug 16, 2012 8:24 am
Has thanked: 2 times
Been thanked: 3 times
Contact:

Re: Audient EVO 16 - Experiences

Post by cupakm »

Just one more question...

icaria36 wrote: Mon Sep 11, 2023 9:45 pm

Since I'm happy with the performance of my setup, I won't touch anything.

...maybe you could :-) how hot is it running?
If you'd have a contactless thermometer at hand, could you give it a try? After like an hour or so of usage, or at least idling.

Post Reply