-
Notifications
You must be signed in to change notification settings - Fork 34
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 sound on the videos #54
Comments
Hey @sudomax sorry to hear about the issues. Have some questions for ya:
display=:0 npm start >> log.log then paste the log.log in here? |
Hey @kevinatown,
|
Oh man, thanks for this. I think that this may have an issue with chromium and bluetooth ASLA this looks like it might work (or someone got it working): arkq/bluez-alsa#88 but it's def an issue with chromium and bluetooth, I need to get and configure one for myself so that I will have a better understanding on what's going on. I hope this helps. Also let me know if this fix works or you found another! |
Also @sudomax is the sound the only issue that you noticed? |
Hi,
[17:42:49.809] [LOG] screencast stderr: ALSA lib pcm.c:8599:(snd_pcm_set_params) Unable to set hw params for PLAYBACK: Device or resource busy The problem, this is a known limitation of Alsa with bluetooth output devices.
Which sets default to use the dmix and dsnoop method to share the physical output device (in my case my usb speakers). |
Interesting, thanks for your answer @andyb2000. |
I am using USB speakers and still appear to be getting no sound |
Sorry for the delay, was busy building the mirror itself. |
I'm working on setting my mirror up and I also don't have Audi through headphone jack. thank you guys for any help |
Hi y'all, sorry I haven't had much time to look into audio issues, but can y'all start with just checking the audio settings on the pi. I hope this is at least some help. |
This module does not work for me. I did a fresh install but it didn't solve my issues.
Would anyone have a solution to fix the sound for the videos?
The text was updated successfully, but these errors were encountered: