-
Notifications
You must be signed in to change notification settings - Fork 548
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
No audio - problem #333
Comments
Curious to know what your output device is - could you share details? Could you dump the
My guess would be that it doesn't support the predefined buffer size utilised in the current alsa implementation. Should probably add in a check against |
hey, thanks for the reply. I will post it right when I get home from work. I tried to look into this params, but I don't have the knowlage for this yet, need to study it more deep to understand that, meanwhile I turned for help here. |
I manage it to work, actualy pulseaudio did. I found similar problem from last year, guy in the topic talks about bad audio drivers for his VERO 4k sound card and hes got it work by setting up pulseaudio. I did the same and it's now working after countless hours of pain :D. There is a new error msg now, but it's playing good through SPDIF output. Thanks bud! |
@Madvih Were you just using the Pi's HDMI output or some other audio board? It's great you have a workaround but we need to recreate this issue and fix it. The hw_param values would have been useful. |
BTW this information could help too. This thread sovle the problem for me and has same problem, more detailed written. |
When I see raspotify I keep mistakingly assuming it's a raspberry pi. So this is vero4k and whatever soundcard (AML M8 audio) that thing has. We'd specifically need the hw_params output when it's trying to play in the broken state, which I guess is no longer available since its fixed. Oh well. |
Yeh that does help, specially:
So Yeh. They've got buggy software which they don't seem too bothered about fixing, presumably cause it's outside the scope of the product they sell - fair enough. We can close this, we don't need to worry about a half-baked sound driver. |
|
That's kind of you to do that but personally I'm all for closing this now. Probably isn't anything we can do. |
Yeah gotcha, but big thanks for help anyway, your quick answers and keen to help me is much appreciated. If this was different kind of problem, I'm sure of that, you would help me to resolve it quickly! Thanks and have a good night! |
@kingosticks I'm currently getting the same error:
In my case, I'm running on Arch with jack audio. |
@markerdmann could you add the info from #333 (comment) so we can look at what the expected Also, it would seem that your using the alsa backend, and not jack? |
@ashthespy Yes, I'll run those commands and post the info here. After I posted my comment, I noticed librespot has a jack backend. I recompiled and tried running it with the jack backend, but for some reason I'm not hearing any audio or seeing any librespot errors. I'll try running it again in verbose mode. This is my current setup:
With that setup, audio is working with:
It's not working with:
|
@ashthespy Here's the output for those three commands:
Is there something else I should print out for the jack device that I see in
These are my qjackctl settings: |
I read this issue #195 and it sounds like the alsa and jack backends are potentially being deprecated in favor of the rodio backend? I tried recompiling with the rodio backend, and that's working on my system. 👍 |
Necro tip. I got it working with my DAC which has show the same errors by using |
That's a good solution. Also in the upcoming |
Having this issue, when trying to play this error occurs:
My audio is on SPDIF, I tried change of bitrate, reinstall, changing --device hw:0,1(what should be my SPDIF output)
But nothing helps.
Please help, if you know how.
Thank you
The text was updated successfully, but these errors were encountered: