-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crackling sound on USB soundcard #971
Comments
I dont know why but the sound going more bad when i touch the piscreen. |
Since you mention piscreen, I assume you use the fbtft drivers. This is a similar case: #888 (comment) |
You can verify if this is the problem by not loading the piscreen device. |
Hello, Yes i use the fbtft driver. Thx notro for your answer and for yours works. |
That depends on how you load it.
Or you can unload the module after it is loaded: |
Thx i will try. |
The sound going better after unload the fbtft. |
You can try txbuflen=128 (256,512,1024,2048). If you use fbtft_device, you can use it directly as an argument. You will see that the change has taken effect in the log: https://github.com/notro/fbtft/wiki/fbtft_device |
Ok, i will try to make my own overlay. Can you tell me in which section I must add this line : txbuflen = <128>; I'm sorry for my incompetence. |
Add it alongside fps, buswidth and regwidth:
If you add this to overrides (DT overlay argument), then you can tweak the value easily:
dtoverlay=piscreen,txbuflen=256 |
Ok, |
The fbtft default is 4k=4096. txbuflen is the size of the transmit buffer, how much is transferred in one SPI message. |
Thanks. |
It's probably a buffer underun in the usb audio device. But I know to little about the processor internals to say anything about where the bottleneck is. |
Hello,
I have a raspberry pi 2 with a USB soundcard and i can't get clean sound on it.
After many search and meny try, i dont know what to do.
If someone can help me, i would appreciate.
I post an audio file to show you the problem : https://clyp.it/j3hnfvvt
Thank you.
The text was updated successfully, but these errors were encountered: