What does "audioState is 0" mean in the log?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • steve781
    Member
    • Jan 2011
    • 99

    What does "audioState is 0" mean in the log?

    I have a post in the Squeezebox Radio forum (http://forums.slimdevices.com/showthread.php?t=87432), but I'll post a more specific question here. Unlike most I've found the Radio alarm very reliable until recently. I run my own SBS 7.5.2 and the ServerPowerCtrl plugin with a Radio, Boom, Duet, and Touch. Last Friday I started getting the fallback alarm instead of the configured internet stream. It has occurred 4 days in a row, so I think the issue is here to stay. Comparing the log of a fallback alarm with one from a successful alarm I noticed that one of the entries had audioState is 0 (fallback) vs. audioState is 1 when the internet stream played. Here's the line from the log of a failed alarm:

    May 2 06:00:12 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:312 notify_playerModeChange: - audioState is 0


    What does audioState 0 mean? Is the SqueezeOS source code available anywhere? For anyone interested the log entries around the failure are in the post on the Radio forum. Thanks in advance,

    Steve
  • bklaas
    Ne'er-do-well, Vagabond
    • Apr 2005
    • 2034

    #2
    it means no audio is being currently decoded out the speaker, which is a general flag that things are failing.

    FYI, in the 7.6 firmware we stepped the aggressiveness about kicking back to the internal fallback alarm sound. audioState has to be 0 on six consecutive checks before falling back to the fallback. It checks every 5 seconds, so only after 30 seconds of failing to stream a stream will it give up on the network stream.

    The Squeezeplay code is open source and available if you want to look at it, but if I had to guess 7.6 is going to clear this issue for you.

    svn repository is at http://svn.slimdevices.com/repos/squ...nk/squeezeplay (replace 7.6/trunk with whatever branch path you are interested in)

    cheers,
    #!/ben
    Former Logitech Developer: Squeezeplay/SqueezeOS/SqueezeboxController/SqueezeCenter
    Community Developer: Nokia770Skin (r.i.p.)

    http://www.last.fm/user/bklaas/

    Comment

    • bklaas
      Ne'er-do-well, Vagabond
      • Apr 2005
      • 2034

      #3
      FYI, see bug 16663 for expanded discussion of the fallback alarm and what was done in 7.6 to step back the aggressive behavior of it:
      Former Logitech Developer: Squeezeplay/SqueezeOS/SqueezeboxController/SqueezeCenter
      Community Developer: Nokia770Skin (r.i.p.)

      http://www.last.fm/user/bklaas/

      Comment

      • bklaas
        Ne'er-do-well, Vagabond
        • Apr 2005
        • 2034

        #4
        sorry, bad svn link above. You want http://svn.slimdevices.com/repos/jiv...nk/squeezeplay
        Former Logitech Developer: Squeezeplay/SqueezeOS/SqueezeboxController/SqueezeCenter
        Community Developer: Nokia770Skin (r.i.p.)

        http://www.last.fm/user/bklaas/

        Comment

        • steve781
          Member
          • Jan 2011
          • 99

          #5
          I may give 7.6 a try at some point. Last night I restarted the SBS and the alarm worked 3 for 3 in testing. This morning it also fired properly. Still I far from convinced that all is well with my SBS installation. For one thing the Server Power Control no longer puts the machine to sleep like it has for the past couple of months. I've even uninstalled the plug-in and reinstalled. Somethings not right so I think I may do an uninstall/reinstall of SBS as a last resort to get things well again.

          Thanks for the info and your help Ben!

          Steve

          Comment

          Working...