On Mon, Jan 25, 2021 at 07:33:56PM -0600, Matt Garman wrote:
> I am using a Raspberry Pi as a "sound server". Essentially, the RPI
> is connected to the actual audio hardware. The RPI advertises itself
> via module-native-protocol-tcp and module-zeroconf-publish. My
> desktop/workstation in
My guess is that it's likely in the amp; did you try hooking up the Topping
to the new pi? Or, the converse; hook the amp up to the workstation and see
if you see a delay?
Does the Pi have a USB soundcard, or a "hat" sort of thing? Some of the
hats have buffers in them to reclock the audio
I am using a Raspberry Pi as a "sound server". Essentially, the RPI
is connected to the actual audio hardware. The RPI advertises itself
via module-native-protocol-tcp and module-zeroconf-publish. My
desktop/workstation in turn uses the RPI for playback via
module-tunnel.
Everything seems to
