As some members might already know, I use an IQaudIO DAC HAT PRO which is producing intermittently audio artifacts. During boot, a short beep-like sound is emitted. This beep-like sound is also emitted intermittently during audio playback. I would like to know whether this issue is caused by software or caused by hardware failure.
Dunno. Don't know what a "beep-like" sound is exactly. Is the sound always exactly the same? Does it only occur when playing music? Do you have a schematic for the dac?
Seems more likely its a software thing, but can't say for sure.
Seems more likely its a software thing, but can't say for sure.
Odd mechanical clock-like sound, at least sounds more like that than a beep to me. Sorta reminds me of the the noise iphone makes when you log off. My first guess would be software, but it might turn out to be something else.
I understand that you have a problem with some of the RPi audio OS's (reference your other recent posts) but for the sake of elimination, can you load up an SD card with Moode or pCp (which I know both work with your DAC) and see if the 'artifact' is still present? Doing so would at least prove the integrity of the DAC.
What is your music source? What is the DAC feeding downstream?
What is your music source? What is the DAC feeding downstream?
The music is either from an internet radio (absolute-chillout) or from SDCard inserted into the Raspberry Pi. The DAC is feeding two LM3886 amplifier chips powered by a 12V split power supply. The output speakers are Titan12 by Warfedale.Yatsushiro said:
A Debian, preferably Devuan based OS is sufficient for me but it has to recognise the IQaudIO DAC sound card. Editing the /boot/config.txt and installing driver and firmware packages are no problems for me. I can install these through a terminal.
Have you tried another OS that supports this DAC, like Volumio? If this works OK then you know for sure it is the software.
During the boot sequence, the wifi chip is initialised and a network (wifi) connection is set up. The beep is emitted during that time. Other beeps may be emitted at other times when the network managing software detects a connection failure and tries to reconnect. I found that running ifconfig wlan0 down followed by ifconfig wlan0 up always causes the beep to be generated. The beep is preceded by a buzz-like sound followed by some seconds of silence.
This means, the onboard wifi circuitry is causing the interference. Since I use a wifi to connect to the network, a solution requires that this interference be moved away from the DAC HAT using a USB wifi card.
This means, the onboard wifi circuitry is causing the interference. Since I use a wifi to connect to the network, a solution requires that this interference be moved away from the DAC HAT using a USB wifi card.
More information:
I disabled both the wifi and bluetooth using /boot/config.txt. The beep did not sound again. This is yet another corroborate that it was the wifi causing the beep. I will try to use an external usb wifi.
I disabled both the wifi and bluetooth using /boot/config.txt. The beep did not sound again. This is yet another corroborate that it was the wifi causing the beep. I will try to use an external usb wifi.
Is it wifi, bluetooth or both?
Again, I have not had such issues with the RPi onboard wifi and numerous DAC's, including IQAudIO.
I still think this is a problem with software, probably drivers. Try a different distro if you have the energy. At least it's just a change of SD card not reformatting a PC 🙂 Moode is a straightforward install.
That said there's a point at which all you want is something that works... I went through something similar with the USB port on a Schiit DAC and eventually lost the will to live trying to get the DAC to talk to either my PC or raspi or anything else via USB.
That said there's a point at which all you want is something that works... I went through something similar with the USB port on a Schiit DAC and eventually lost the will to live trying to get the DAC to talk to either my PC or raspi or anything else via USB.
I am disabling bluetooth because I do not use it. I also do not use an ethernet (wired) connection to the network. This means, I will need to use an external wifi.
Regarding using another distribution, I do not think that will solve much of my issues as what intefaces and uses hardware is the kernel, kernel modules/drivers, and libc*, the c-library of functions. These are so low level, that distribution makers most probably do not even change.
Regarding using another distribution, I do not think that will solve much of my issues as what intefaces and uses hardware is the kernel, kernel modules/drivers, and libc*, the c-library of functions. These are so low level, that distribution makers most probably do not even change.
At some point software events are propagated outside the kernel to code that'll be very different between distributions.
Also, though distros start from the same place, the people that build them choose how the kernel operates and which bits are included or not. A lot of behaviour can be influenced by the way they're configured. It's a complex environment.
So you may gain some insight into the problem by trying another distro. Was all I was trying to say. But it's time, and time is precious.
Also, though distros start from the same place, the people that build them choose how the kernel operates and which bits are included or not. A lot of behaviour can be influenced by the way they're configured. It's a complex environment.
So you may gain some insight into the problem by trying another distro. Was all I was trying to say. But it's time, and time is precious.
With your like of Debain/Devuan, have you tried dietPi? The devs are very responsive to support, development and improvements.
https://dietpi.com/