I would agree with you, but I'd be guessing as to what the exact cause
is. I've seen devices behave like this before, and it's very much
device-specific. Unless you can show that Alsa is kicking off a stream
and sending garbage I would definitely think it's the DAC driver.
As a general comment I
paul- wrote:
> The above is pretty simple to do. So far the firmware and the new dtb
> file is the only thing added for the zero, so it should work with just
> the firmware update.
>
> But we will get zero support in the next release for sure.
Thats great to hear!
Just got my pi zero w today,
drmatt wrote:
> Based on what OS, kernel, and software stack?
>
> The udev system should handle initialisation of the DAC if it's plugged
> in post boot. You should at least see a kernel log message when the DAC
> joins the USB bus, even if no driver subsequently loads to manage it.
Armbian os
Based on what OS, kernel, and software stack?
The udev system should handle initialisation of the DAC if it's plugged
in post boot. You should at least see a kernel log message when the DAC
joins the USB bus, even if no driver subsequently loads to manage it.
--
Hardware: 3x Touch, 1x Radio, 2
Hi,
I am working on an arm64-based, squeezebox touch-like system.
The system plays through a USB DAC (C_MEDIA 6632A) using
squeezelite.
The results vary depending on how I start up the system:
If I connect and power on the DAC first, then the squeezebox system, I
get this:
1. The DAC is pick
Has someone looked into this a bit deeper?
http://forums.slimdevices.com/showthread.php?105198-ANNOUNCE-AirPlay-Bridge-integrate-AirPlay-devices-with-LMS-(squeeze2raop)
respectively
https://github.com/philippe44/LMS-to-Raop
Sounds like a pretty useful extension to me, though I don't own a single
