[Pianod] Pi Woes

[Robert Huddleston]

Let pianobar run all day today.. And while the console did share a 
couple of errors.. The more enjoyment was my customer telling me that 
music lapsed for 15 - 20 minutes at periods of time.. One song would 
play - 15 - 20 minute lag.. Advertisement.. Then a song..

Pianobar console gave me the following errors (spaced out - not back to 
back)


/!\ Decoding error: Bitstream value not allowed by specification
/!\ Buffer overflow!

/!\ Decoding error: Unexpected channel configuration change
/!\ Buffer overflow!

/!\ Decoding error: Gain control not yet implemented
/!\ Buffer overflow!


> Perette Barella <mailto:perette at barella.org>
> March 17, 2014 at 8:48 AM
> Does killing pianod and restarting it work? If not—outside pianod.
>
> Install/startup pianobar and let it run for a day. If it exhibits 
> similar problems—then we know it’s not pianod specific.
>
> If pianobar runs fine for a day whereas pianod locks up every few 
> hours, then that would confirm a pianod-specific bug.
>
> A stack dump from the player thread while locked up would be helpful 
> in any scenario.
>
> What Linux distros are you guys running on the Pis? What 
> revision/variant of the pi hardware?
>
> Perette
>
>
>
> _______________________________________________
> Pianod mailing list
> Pianod at lists.deviousfish.com
> http://lists.deviousfish.com/listinfo.cgi/pianod-deviousfish.com
> Robert-GMAIL <mailto:rhuddleston at gmail.com>
> March 17, 2014 at 8:00 AM
> Neither issue resolves itself.. I'm typically forced to do a reboot 
> command
>
> Like the other poster - I have my pi running at a site where this 
> setup is somewhat mission critical - so restarting 6 times every day 
> is becoming a nuisance
>
> -------------------------------------------
> This email is being sent from a mobile device. Please excuse any 
> errors in advance.
> -------------------------------------------
>
> Perette Barella <mailto:perette at barella.org>
> March 17, 2014 at 7:41 AM
>> The majority of issues are "Stalled" with status code 106 and usually with 1 or 2 seconds left in a song... Could this be a protocol issue with libpiano and/or Pandora? As all my stalls appear to be before changing to another song.
>
>
>> The other I see is around reboots or loss of network connectivity.. Sometimes I will get no stations starting on boot.. From what I've read this could be a result of delayed network connection... Anyone have any ideas on this?
>
>
> On the no stations on start: does it stay that way, or does pianod gather them after a minute or so?  Peter had a problem with this and it required resetting the DNS lookup state, which change got into the code base.  If it does resolve itself, then this is some kind of pi boot timing issue, otherwise it should get looked into.
>
> For the stall… consistently stalling at the end of the song is odd.  Does that recover, or stay stuck?  Can anyone experiencing this capture the stack on the playback thread while it’s hung?  Ideally, with configure —-enable-debug.  The only time I’ve ever seen the playback thread hang in the Mac world is with some wack USB-enabled audio amp, which locked up libao and the player… since the rest of the libraries would be the same, this seems a likely candidate.
>
>
>
>> On 2014年03月16日, at 13:56, Robert Huddleston<rhuddleston at gmail.com>  wrote:
>>
>>> I have been experiencing issues with Pianod and thinking that it's only a Raspberry Pi issue...
>>>
>>>
>>>
>>> I would rather run pianod due to the web gateway - but is this an implementation issue with libpiano.. Would pianobar experience the same issue?
>>>
>>> Or is this a Pi issue?
>
> _______________________________________________
> Pianod mailing list
> Pianod at lists.deviousfish.com
> http://lists.deviousfish.com/listinfo.cgi/pianod-deviousfish.com
> Perette Barella <mailto:perette at barella.org>
> March 16, 2014 at 2:41 PM
> Both “Stalled” and lack of stations suggest network loss issues. The 
> stalls may happen more at song transition when there’s no buffering 
> built up yet. I’m assuming you’re on wifi; trying pinging from the pi 
> to your router and see what your packet loss looks like (use ping 
> -c100 if needed). If that seems reliable then trying pinging something 
> else in the world and how packet loss looks there, and traceroute to 
> figure out where along the way it’s happening.
>
> Setting up a network time lapse camera thing for Airigami recently, we 
> found the Pi does better with the wifi transceivers that have the 
> antenna on them and that the router we were using made a heck of a 
> difference. We could barely get signal on the closest camera with line 
> of sight with a cheapo Netgear WGR614, but with an Airport (Apple’s 
> router) we got signal 3 considerably further away and around corners. 
> I’ve also seen much better network reliability since I upgraded to a 
> higher-end Netgear here at home. It seems in this case that a few 
> bucks more does get you something.
>
> Perette
>
>
>
>
> _______________________________________________
> Pianod mailing list
> Pianod at lists.deviousfish.com
> http://lists.deviousfish.com/listinfo.cgi/pianod-deviousfish.com
> Robert Huddleston <mailto:rhuddleston at gmail.com>
> March 16, 2014 at 1:56 PM
> I have been experiencing issues with Pianod and thinking that it's 
> only a Raspberry Pi issue...
>
> The majority of issues are "Stalled" with status code 106 and usually 
> with 1 or 2 seconds left in a song... Could this be a protocol issue 
> with libpiano and/or Pandora? As all my stalls appear to be before 
> changing to another song.
>
> The other I see is around reboots or loss of network connectivity.. 
> Sometimes I will get no stations starting on boot.. From what I've 
> read this could be a result of delayed network connection... Anyone 
> have any ideas on this?
>
> I would rather run pianod due to the web gateway - but is this an 
> implementation issue with libpiano.. Would pianobar experience the 
> same issue?
>
> Or is this a Pi issue?
>
> Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deviousfish.com/pipermail/pianod-deviousfish.com/attachments/20140317/e79bb880/attachment-0003.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
URL: <http://lists.deviousfish.com/pipermail/pianod-deviousfish.com/attachments/20140317/e79bb880/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1570 bytes
Desc: not available
URL: <http://lists.deviousfish.com/pipermail/pianod-deviousfish.com/attachments/20140317/e79bb880/attachment-0007.jpg>