ETH-68: Ethernet Audio Interface for Linux

How does the receive side recover the transmit side's sample clock? There is a BNC for clock sharing between "multiple units", but I'm not sure if that's used / required between transmit and receive.

Or is there no such synchronization, in which case there would be long-term drift?

Far be it from me to discourage an H7 build, but I do question the codec choice. It's far from top of the line and it's not like the design is tight on space. TI offers much better (almost 20 dB SNR more on the ADC). Maybe a gen 2 could benefit from a better codec.

Hi, I'm Alex, I made ETH-68. I didn't create the post here on HN but I will answer some of the questions that have come up in the comments

How difficult would it be to extend it to 192kHz, or even 384kHz? Is it limited by the ESP32 hardware? This could be very handy for ultrasound capture offshore!

how do I buy this?

Really nice!!!

I wonder if gigabit would make a difference on latency, faster packet transmissions. Could packets drop from 64 to 32b?

4ms is pretty good but I feel like sub 2ms would be nicer.

> eth68 sends capture packets to 12.12.12.10:3000 by default.

Um.

> Very low latency: 3.620 milliseconds round trip at 48 kHz with 64 sample buffer

"very low latency" in audio is <=1ms. 3.6ms is good but not special.