Home of the Squeezebox™ & Transporter® network music players.
Page 4 of 4 FirstFirst ... 234
Results 31 to 39 of 39
  1. #31
    Junior Member
    Join Date
    May 2018
    Posts
    12

    Same issue here...

    Hi! I just wanted to give my feedback as well with version 2.33.

    Starting a new song will take:
    - regular song in lms : instant
    - web radio: less than 1 sec
    - spotty from Spotify: 6 seconds (current playing song stops 2 seconds after changing track followed by a 4 seconds gap)
    - spotty from ipeng's interface: 6-10 seconds
    -spotty from lms web interface : 4-12 seconds
    Librespot from Spotify average 2-3 seconds but got as long as 12 seconds delay (instant when rewinding the song-the files are not cached)

    - Pausing from ipeng, Spotify or the web interface: instant
    - Resuming from ipeng, Spotify or the web interface: 0-3 seconds (variable)

    Running on class 10 card on a raspberry pi 2. LMS 7.9.1 Increased memory usage enabled. Also, I do not have particularly interesting logs to communicate..

    Thanks for your work!

  2. #32
    Junior Member
    Join Date
    Sep 2018
    Posts
    3
    Hi all, I'm experiencing slow Spotty behaviour on Raspberry Pi as well. Thought I would post here with what I've found in case it can help

    Setup details:
    Server: Raspberry pi 2B (exclusively running LMS)
    Clients: Raspberry pi zero w (x3)
    OS: Raspian
    LMS version: 7.9.2
    Spotty version: 2.4.4
    Client version: Squeezelite v1.8.6-957
    Internal Network: Ethernet for server, WiFi for clients
    External network: DSL 18Mbps line speed

    Browsing and playing local files is almost instant. Internet radio plays within a couple of seconds (great). Official Spottify browses and plays almost instantly too.

    I'm finding it takes about 10-20 seconds to navigate the Spotty menus (e.g. Open Albums). Interestingly, i have found it get slower the longer LMS has been running. After restarting the service menu load times go down to 2-4s (which is great). Leave it a day, and it goes slow again.

    I tried the resize cover art options (as suggested by others) but it doesn't make a differnce to the load times.

    It also takes about 10-30s to start playing a song (whether an intial load or skipping tracks). Reducing the Spotty bitrate to 160k shaves off a couple of seconds at the most. I wanted to go digging a little deeper into what's happening on the network, so fired up nload on the lms server and got the following graph when skipping a song
    Name:  spottynet.png
Views: 301
Size:  16.8 KB
    This was recorded soon after restarting LMS so the speed is about as good as it gets.
    It looks like there's a 10s delay between pressing play and anything happening on the network. Then (I guess) the song starts streaming from Spotify. 6s later LMS starts pushing the data to the clients and it plays almost immidiately.

    Is this expected behaviour? Or is there something weird going on? Our internet connection here isn't great (18Mbs), but considering the official Spottify plays almost instantly, I gather it's specific to Spotty.

    Any ideas? I'm happy to do more testing if I can help.

    Cheers

  3. #33
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,190
    Quote Originally Posted by beans View Post
    Server: Raspberry pi 2B (exclusively running LMS)
    What OS are you using? Could you be running low on memory? Can you watch "top" while you tart playing a track? Is it CPU, RAM or I/O bound?
    Michael

    http://www.herger.net/slim-plugins - Spotty, MusicArtistInfo

  4. #34
    Junior Member
    Join Date
    Sep 2018
    Posts
    3
    hey mherger,

    Running Raspian. Memory looks fine. top says ther's 500BM free. So I guess not memory bound.

    When I start playing a track squeezebox has around 12% usage with a brief spike up to 50%ish

    Name:  spottytop1.png
Views: 318
Size:  27.2 KB

    While the track is playing spotty-hf seems to be using between 3-15% with an occasional spike up to 50%ish too.

    Name:  spottytop.png
Views: 316
Size:  27.3 KB

    So doesn't look CPU bound. It's never getting to 100% of a single core.

    Disk IO wait time doesn's seem to go above 0.1. So I guess not disk bound either.

    Which only leaves network bound I guess?

  5. #35
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,190

    Spotty on Rpi3 / Very slow

    > Running Raspian. Memory looks fine. top says ther's 500BM free. So I
    > guess not memory bound.


    Agreed, nothing obviously wrong there.

    > When I start playing a track squeezebox has around 12% usage with a
    > brief spike up to 50%ish


    Hmm... I wouldn't even expect LMS to do much work in this case. It
    should mostly be spotty.

    > Which only leaves network bound I guess?


    Yes. But then why would it take forever in this case but no other issues
    with other services? You're not running LMS in all wireless mode, aren't
    you?

    --

    Michael

  6. #36
    Junior Member
    Join Date
    Sep 2018
    Posts
    3
    What do you mean by all wireless mode? As in, the way the pi connects to the network? The server pi is connected via ethernet cable. The three clients are connected via WiFi (Pi ZeroW).

    If I find a spare few hours I might try to build and debug the spotty plugin on the pi. Hopefully that'll point us in the right direction. Any tips for debugging? Looks like I use the docker image to build spotty and copy the binaries across to my installation? Owww. you're using Rust. Good excuse to learn a new programming language!

  7. #37
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,190

    Spotty on Rpi3 / Very slow

    > What do you mean by all wireless mode? As in, the way the pi connects to
    > the network? The server pi is connected via ethernet cable. The three


    Ok, that's what I wanted to know.

    > tips for debugging? Looks like I use the docker image to build spotty


    "Looks like I use docker" - didn't you do this on purpose? If so, get
    rid of docker and install LMS directly.

    > and copy the binaries across to my installation? Owww. you're using
    > Rust. Good excuse to learn a new programming language!


    It's not my choice... I had no clue about Rust when I started
    investigating Spotify options. But the project I'm using (librespot) is
    written in Rust. Therefore I had to get my hands dirty and figure some
    out :-)

    --

    Michael

  8. #38
    Junior Member
    Join Date
    Aug 2018
    Posts
    12
    Quote Originally Posted by beans View Post
    hey mherger,

    Running Raspian. Memory looks fine. top says ther's 500BM free. So I guess not memory bound.

    When I start playing a track squeezebox has around 12% usage with a brief spike up to 50%ish

    Name:  spottytop1.png
Views: 318
Size:  27.2 KB

    While the track is playing spotty-hf seems to be using between 3-15% with an occasional spike up to 50%ish too.

    Name:  spottytop.png
Views: 316
Size:  27.3 KB

    So doesn't look CPU bound. It's never getting to 100% of a single core.

    Disk IO wait time doesn's seem to go above 0.1. So I guess not disk bound either.

    Which only leaves network bound I guess?
    Just to confirm your findings beans, I'm seeing the same behaviour from my setup as well. It doesn't seem to matter what system the LMS is running (have tried Windows, Debian, Ubuntu, Raspbian).

    While playing a song, I have analysed both nload and my router, and both seem to show the connection to the spotify server capping out at around 3Mbps. As each song is around 4.5 to 5MB in size, that would equal an 8-10 second wait before playing.

  9. #39
    Junior Member
    Join Date
    Feb 2019
    Posts
    11

    Solved?

    Did anyone find a solution to this?

    I just set up a 3B+ running PCP and the Spotty plugin, wired to router with gigabit, but find Spotify Connect just as slow as others have described in 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
  •