My solution to pops and clicks

Raspberry Pi related support

Re: My solution to pops and clicks

Postby tux » 26 Mar 2014, 21:14

An additional step that results in eliminating all the "FIQ Reported NYET " errors is to unbind the usb dac from usbhid. I tested it and it's the first time that rpi reproduces music with zero errors.

it depends on the port that the device is attached but the commands are:

Code: Select all
echo -n "1-1.3:1.0" > /sys/bus/usb/drivers/usbhid/unbind
echo -n "1-1.2:1.0" > /sys/bus/usb/drivers/usbhid/unbind


I run a custom linux os and i have put these command on a startup script. If the device is unplugged and plugged in again the command has to be given again but i assume that some generic rule could prevent the usb devices to bind to usbhid.

This fix was suggested by the driver developer here:

http://www.raspberrypi.org/phpBB3/viewt ... 0&start=50

and thanks to this my rpi is finally a machine i can trust for my music reproduction!


A new BRANCH=next rpi-update will also have an affect on the FIQ errors according to the developer.
User avatar
tux
 
Posts: 34
Joined: 22 Jan 2014, 23:39
Location: Greece

Re: My solution to pops and clicks

Postby FauDrei » 27 Mar 2014, 15:05

How does one find proper USB device numbers for unbinding usbhid?

When I try to unbind usbhid with proposed commands on my RPi (custom PiBang installation), all I get is:

Code: Select all
-bash: echo: write error: No such device


for both "1-1.3:1.0" and "1-1.2:1.0".
FauDrei
 
Posts: 19
Joined: 04 Mar 2014, 16:59

Re: My solution to pops and clicks

Postby tux » 27 Mar 2014, 15:43

just dmesg and see these numbers for your usb dac!
User avatar
tux
 
Posts: 34
Joined: 22 Jan 2014, 23:39
Location: Greece

Re: My solution to pops and clicks

Postby FauDrei » 27 Mar 2014, 19:26

Code: Select all
[    3.526125] usb 1-1.3: new high-speed USB device number 5 using dwc_otg
[    3.646893] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.656856] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.666174] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.675024] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.684614] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.693491] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.702945] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.711622] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.720910] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.729448] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.739054] usb 1-1.3: config 1 has an invalid interface number: 2 but max is 1
[    3.747505] usb 1-1.3: config 1 has no interface number 0
[    3.755237] usb 1-1.3: New USB device found, idVendor=8605, idProduct=5023
[    3.763485] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.771844] usb 1-1.3: Product: audiophilleo2 v1.29 SN00578
[    3.779805] usb 1-1.3: Manufacturer: Audiophilleo
[    3.785551] usb 1-1.3: SerialNumber:  00578

Does that mean that my DAC (USB/SPDIF converter) is "1-1.3"?

...still getting the same error.
FauDrei
 
Posts: 19
Joined: 04 Mar 2014, 16:59

Re: My solution to pops and clicks

Postby tux » 27 Mar 2014, 19:56

for my DAC i find the following:

Code: Select all
[ 1768.295305] input: HiFimeDIY Audio SA9023 USB Audio as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input4


so in this case the command should be:

Code: Select all
echo -n "1-1.3:1.0" > /sys/bus/usb/drivers/usbhid/unbind


Please note that a friend of mine did a test on his Dac Magic and the above command did not solve the issue of FIQ Reported NYET errors. In my case, i have been listening for about 17 hours without any error, so unfortunately it's not a universal solution.
User avatar
tux
 
Posts: 34
Joined: 22 Jan 2014, 23:39
Location: Greece

Re: My solution to pops and clicks

Postby tux » 28 Mar 2014, 11:16

It' seems i have to study more on usb devices and linux :p

I believed that these numbers refer to the bus id. I found out that they change with different devices (athough it's not a device id as i understand).

I had the opportunity to retest the friends' dacmagic and with the correct id, the FIQ reported NYET errors disappeared.

So until now the issue has been fixed in 2 dacs i have tested and i believe that this tweak will have an positive effect for many of you.
User avatar
tux
 
Posts: 34
Joined: 22 Jan 2014, 23:39
Location: Greece

Re: My solution to pops and clicks

Postby vortex » 28 Jun 2014, 15:13

I've applied the solution in the first post but unfortunately it made things worse. While I used to have loud clicks that are intermittent and come far in between, now I have softer but continuous clicks.

My external DAC is AudioEngine D1. I guess I will have to wait for 0.3 alpha and hope that the clicks and pops do get eliminated eventually.
vortex
 
Posts: 8
Joined: 08 Jun 2014, 04:30

Re: My solution to pops and clicks

Postby cmh714 » 15 Aug 2014, 02:59

this appears to be baked into v0.3 now

just edit /boot/cmdline_rune.txt

currently line 4 is enabled but line 5 has the setting from this post. Change and reboot. Should be good to go....
cmh714
 
Posts: 470
Joined: 04 May 2014, 03:06

support RuneAudio Donate with PayPal

Previous

Return to Raspberry Pi

Who is online

Users browsing this forum: No registered users and 11 guests