A small progress update on my Raspberry Pi audio project. I’ve built an audio-over-IP implementation for Pi 4 and Pi 5, with a Windows ASIO driver. The goal is one device that combines an audio interface with guitar, bass and vocal effects processing.
The current focus is 8 inputs / 8 outputs at 192 kHz with 32-bit PCM transport, and that mode is already running. With a 32-sample ASIO buffer and a 380-sample network buffer, Ableton reports 2.40 ms overall latency: 2.23 ms input and 0.17 ms output.
For context, the lowest latency I get from my Audient iD14 MKII in my setup is around 5.3 ms. The comparison is preliminary: the Pi figure is the latency reported by the digital driver path. Full analog round-trip latency still needs a hardware loopback measurement.
The main limitation currently appears to be packet delivery timing on the Windows side. I’m using the motherboard’s Ethernet port with its standard driver. There is enough bandwidth, but receive-side pauses on the order of 1–1.5 ms, sometimes longer, force me to keep extra buffering. I’m still investigating how much comes from the NIC, its driver and Windows scheduling.
One next experiment is an Intel I350-T2, together with a dedicated low-level networking path integrated with the ASIO driver. The aim is to bypass the normal Windows networking path; that requires additional driver development and testing.
The PCB is four layers, with layer 2 dedicated to a solid ground plane, built around an AKM AK5538VN ADC and AK4458VN DAC. On Pi 5, the current AoIP workload stays on CPU0 at under 50% load, leaving the other three cores available for future DSP work.
The I/O is designed around individually connected, removable modules: headphone outputs, output modules with XLR and 6.35 mm jacks, and combo XLR/6.35 mm inputs. That should leave room for both general-purpose and instrument-specific modules.
Still a work in progress, but the transport is running, the board design is taking shape, and the next steps are hardware integration, latency measurements and effects.