-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Pianobar is having trouble opening audio device #739
Comments
I'm adding this to the 0.4.x board to triage before our next meeting. |
One solution to this problem may be to build the latest pianobar release from source. Currently the deb package is at least several years out of date. |
Our current version is 2019.02.14, there have been 3 releases since then, the latest being: 2022.04.01. Source https://github.com/PromyLOPh/pianobar/blob/master/ChangeLog |
Just noting here that Pianod (https://deviousfish.com/pianod/) is based on pianobar, so we probably shouldn't switch to that. |
Since pianobar doesn't see a lot of development it might not be too risky
to maintain our own fork. There might be an easy fix. See
https://github.com/PromyLOPh/pianobar/blob/caf14ba90b9aca483d13dff12d03af48dd6936b6/src/player.c#L548
…On Wed, Jun 19, 2024 at 4:03 PM Klayton Smith II ***@***.***> wrote:
update to this:
updating pianobar didn't help, it broke the same way
image.png (view on web)
<https://github.com/micro-nova/AmpliPi/assets/5252693/e37b9acf-cdeb-46be-bc56-5febe168f007>
—
Reply to this email directly, view it on GitHub
<#739 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEZPO4DRYUFG5ZUMHL5SY3ZIHPY7AVCNFSM6AAAAABIYYJNN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZZGM4TCOJWHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
So I forked pianobar and made a couple changes to the current release version, built it and replaced the binary on the inhouse amplipi and it seems like it's more stable. I'm going to let it run over the weekend but my question now is what should we do, try to get this change merged into pianobar or maintain a fork ourselves? |
Can we do both?
…On Fri, Jun 21, 2024 at 1:53 PM Klayton Smith II ***@***.***> wrote:
So I forked pianobar and made a couple changes to the current release
version
<PromyLOPh/pianobar@master...klay2000:pianobar:master>,
built it and replaced the binary on the inhouse amplipi and it seems like
it's more stable. I'm going to let it run over the weekend but my question
now is what should we do, try to get this change merged into pianobar or
maintain a fork ourselves?
—
Reply to this email directly, view it on GitHub
<#739 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE2KUN6CBLOHFXWNXTPCEKTZIRSBBAVCNFSM6AAAAABIYYJNN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBTGE4DSMBSGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
the updated link for changes between forks is PromyLOPh/pianobar@master...micro-nova:pianobar:master |
Pianobar the underlying client we use to play Pandora streams appears to sometimes be unable to open the audio device. The user will see this as a Pandora stream that will stop playing audio. Switching streams or using the Pandora station browser to switch to a different station will usually fix the problem. Here is a log from pianobar:
Currently we are not sure if this happens mid song, when starting up, or when changing songs, or some combination. Current thoughts are our virtual sources are possibly interfering with pianobars behavior / expectations.
This was the original reason we had tried to add a process monitor to pianobar.
Current thoughts are we could fork pianobar and attempt to make the changes to the source ourselves. Other options are https://deviousfish.com/pianod/ and pydora as replacements for pianobar.
The text was updated successfully, but these errors were encountered: