Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 3 of 3
  1. #1
    Senior Member
    Join Date
    Dec 2011
    Posts
    111

    Spotty: odd behavior under slow internet

    Hello all, I'm one of those cord-cutters whose only internet connection is a mobile hot-spot.
    When t-mo is open full-throttle (up till 10gb), it can clock up to 30mbps or even higher and everything's beautiful.
    But when 10gb allotment runs out, the speed goes down to 600kbps and that's when odd behaviors appear.
    It is not an impossible situation but I'm hoping for some explanations.

    Here's my setup:
    RaspberryPi 3B+ runs squeezlite/jivelite. It has a Allo DigiOne which feeds into external DAC.
    When it works, the sound is absolutely great and I can't imagine it getting better.
    Intel NUCi7 runs LMS 7.9.1 and that's all it runs with local music stored in SSD.
    All devices are on LAN where the local router is hard-wired to a WAP which connects to the hotspot.

    Odd behavior:
    1) with Spotty audio set at Extreme (320kbps), gap between songs is av. 50 seconds.
    when set at High (160kbps), gap is "normal" anywhere from 1 to 5 seconds.

    2) with either setting, if I disrupt the bandwidth by surfing the net for other activities,
    music stops playing at the end of the current song and does not continue. The Connect device is gone.
    Only remedy at this point is to restart LMS; I've made a button for that purpose.
    When LMS comes up, Spotty device appears again, and I activate it to begin the playback.

    Here's some relevant server log:
    ===================>>>
    [19-03-13 14:53:32.0050] Slim::Player::StreamingController::_eventAction (273) b8:27:eb:fd:ab:5a: StatusHeartbeat in PLAYING-TRACKWAIT -> Slim::Player::StreamingController::_CheckSync
    [19-03-13 14:53:33.0062] Slim::Player::StreamingController::_eventAction (273) b8:27:eb:fd:ab:5a: StatusHeartbeat in PLAYING-TRACKWAIT -> Slim::Player::StreamingController::_CheckSync
    [19-03-13 14:53:34.0069] Slim::Player::StreamingController:layerStopped (2157) b8:27:eb:fd:ab:5a
    [19-03-13 14:53:34.0073] Slim::Player::StreamingController::_eventAction (273) b8:27:eb:fd:ab:5a: Stopped in PLAYING-TRACKWAIT -> Slim::Player::StreamingController::_PlayIfReady
    [19-03-13 14:53:34.0075] Slim::Player::StreamingController::_setPlayingStat e (2357) new playing state STOPPED
    [19-03-13 14:53:34.0078] Slim::Player::StreamingController::_eventAction (303) b8:27:eb:fd:ab:5a: Stopped - new state STOPPED-TRACKWAIT
    [19-03-13 14:53:35.0039] Slim::Player::StreamingController::_eventAction (273) b8:27:eb:fd:ab:5a: StatusHeartbeat in STOPPED-TRACKWAIT -> Slim::Player::StreamingController::_NoOp

    ==================>>>> bunch of same log entries here

    [19-03-13 14:58:17.0068] Slim::Player::StreamingController::_eventAction (273) b8:27:eb:fd:ab:5a: StatusHeartbeat in STOPPED-TRACKWAIT -> Slim::Player::StreamingController::_NoOp
    [19-03-13 14:58:22.0053] Slim::Player::StreamingController::_eventAction (273) b8:27:eb:fd:ab:5a: StatusHeartbeat in STOPPED-TRACKWAIT -> Slim::Player::StreamingController::_NoOp
    [19-03-13 14:58:26.0068] Slim::Player::StreamingController::_eventAction (273) b8:27:eb:fd:ab:5a: StatusHeartbeat in STOPPED-TRACKWAIT -> Slim::Player::StreamingController::_NoOp
    2019-03-13 14:58:27 squeezeboxserver_safe stopped. <<<<<<<<================ this is when I restarted LMS manually
    2019-03-13 14:58:27 squeezeboxserver_safe started.
    [19-03-13 14:58:27.8780] main::init (387) Starting Logitech Media Server (v7.9.1, 1522157629, Fri Mar 30 12:25:29 CEST 2018) perl 5.026002 - x86_64-linux-gnu-thread-multi
    [19-03-13 14:58:29.6531] Slim::Web::Cometd::handler (422) errorNeedsClient: b8:27:eb:fd:ab:5a, status, -, 10, menu:menu, useContextMenu:1, subscribe:600
    2019-03-13 16:58:14 squeezeboxserver_safe stopped.
    2019-03-13 16:58:14 squeezeboxserver_safe started.
    [19-03-13 16:58:14.9822] main::init (387) Starting Logitech Media Server (v7.9.1, 1522157629, Fri Mar 30 12:25:29 CEST 2018) perl 5.026002 - x86_64-linux-gnu-thread-multi
    [19-03-13 16:58:17.4470] Slim::Web::Cometd::handler (422) errorNeedsClient: b8:27:eb:fd:ab:5a, status, -, 10, menu:menu, useContextMenu:1, subscribe:600
    [19-03-13 17:10:09.4097] Plugins::Spotty::API::__ANON__ (1465) Invalid data <<<<<<<<================ i think it's here where Spotty disappears
    2019-03-13 17:23:17 squeezeboxserver_safe stopped. <<<<<<<<================ and i restarted LMS manually
    2019-03-13 17:23:17 squeezeboxserver_safe started.
    [19-03-13 17:23:17.4645] main::init (387) Starting Logitech Media Server (v7.9.1, 1522157629, Fri Mar 30 12:25:29 CEST 2018) perl 5.026002 - x86_64-linux-gnu-thread-multi
    [19-03-13 17:23:19.7654] Slim::Web::Cometd::handler (422) errorNeedsClient: b8:27:eb:fd:ab:5a, status, -, 10, menu:menu, useContextMenu:1, subscribe:600
    [19-03-13 18:35:56.9779] Plugins::Spotty::API::__ANON__ (1465) Invalid data
    2019-03-13 18:40:49 squeezeboxserver_safe stopped.
    2019-03-13 18:40:49 squeezeboxserver_safe started.
    [19-03-13 18:40:49.5637] main::init (387) Starting Logitech Media Server (v7.9.1, 1522157629, Fri Mar 30 12:25:29 CEST 2018) perl 5.026002 - x86_64-linux-gnu-thread-multi
    [19-03-13 18:40:50.3901] Slim::Web::Cometd::handler (422) errorNeedsClient: b8:27:eb:fd:ab:5a, status, -, 10, menu:menu, useContextMenu:1, subscribe:600
    [19-03-13 18:40:53.3816] Slim::Web::Cometd::handler (422) errorNeedsClient: b8:27:eb:fd:ab:5a, status, -, 10, menu:menu, useContextMenu:1, subscribe:600

  2. #2
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,312

    Spotty: odd behavior under slow internet

    > Odd behavior:
    > 1) with Spotty audio set at Extreme (320kbps), gap between songs is av.
    > 50 seconds.
    > when set at High (160kbps), gap is "normal" anywhere from 1 to 5
    > seconds.


    Are you using the latest and greatest? What helper binary would you be
    using (see Settings/Advanced/Spotty)? There's some recent work being
    done to improve the download behaviour.

    --

    Michael

  3. #3
    Senior Member
    Join Date
    Dec 2011
    Posts
    111
    Quote Originally Posted by mherger View Post
    > Odd behavior:
    > 1) with Spotty audio set at Extreme (320kbps), gap between songs is av.
    > 50 seconds.
    > when set at High (160kbps), gap is "normal" anywhere from 1 to 5
    > seconds.


    Are you using the latest and greatest? What helper binary would you be
    using (see Settings/Advanced/Spotty)? There's some recent work being
    done to improve the download behaviour.

    --

    Michael
    yes, i'm running v2.7.5 with the default (auto) setting for the helper.
    i've always been curious about the Helper Application; what exactly is its function?
    i tried the raspotify in RPi as an independent, local Spotify Connect but it did not behave much better.
    in fact, it would stop after the current song, so i'm back to Spotty.

    the long song gaps are something that i can live with but much more troublesome is the disappearance of Connect device
    and my having to restart LMS to bring it back.
    please see the short excerpt of another server log.
    my best guess is that Spotify itself is very sensitive to streaming rate and when the client is not consuming in perfect order,
    it terminates the connection. is that what's happening?


    [19-03-14 10:35:05.4551] Slim::Web::HTTP::sendResponse (2008) Sent 202 to 192.168.1.23:57866
    [19-03-14 10:35:05.4554] Slim::Web::HTTP::sendResponse (2014) No more segments to send to 192.168.1.23:57866
    [19-03-14 10:35:05.4557] Slim::Web::HTTP::sendResponse (1970) No segment to send to 192.168.1.23:57866, waiting for next request...
    [19-03-14 10:35:05.5905] Slim::Web::HTTP::sendStreamingResponse (2127) sendStreaming response begun...
    [19-03-14 10:35:05.5910] Slim::Web::HTTP::sendStreamingResponse (2258) Nothing to stream, let's wait for 0.4 seconds...
    [19-03-14 10:35:05.5914] Slim::Web::HTTP::sendStreamingResponse (2371) $httpClient is: Slim::Web::HTTP::ClientConn=GLOB(0x561b5347e998)
    [19-03-14 10:35:05.5917] Slim::Web::HTTP::sendStreamingResponse (2373) $peeraddr{$httpClient} is: 192.168.1.23
    [19-03-14 10:35:05.5919] Slim::Web::HTTP::sendStreamingResponse (2374) Got nothing for streaming data to 192.168.1.23

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •