• Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Subsonic stuck at buffering every 2:30 on MacOS

    Scheduled Pinned Locked Moved
    Technical Help
    2
    5
    126
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      palvji
      last edited by

      Using Strawberry 1.2.7 in MacOS, when playing tracks via Subsonic (Navidrome server) every track plays until about the 2:30 mark, then it gets stuck at Buffering 0%...:

      Screenshot 2025-02-06 at 12.29.40.png

      If I use the navigation bar to go to any part of the song, it resumes playing as normal, but only for another 2:30 mins. Then it get's stuck again.

      The server works ok, it's been tested with different players. In fact, Strawberry in Kubuntu 24.04 works ok, so I believe this is something MacOS specific

      This started some versions ago, I believe 1.2.3 was the first one with the issue.

      I've reproduced the issue capturing the log

      GST_DEBUG=5 GST_DEBUG_FILE=/tmp/strawberry-gst-debug.log ./strawberry
      

      but the output is 700mbs. I can upload it somewhere if useful

      P 1 Reply Last reply Reply Quote 0
      • P
        palvji @palvji
        last edited by

        Just tested now, 1.2.3 works ok, 1.2.5 has the issue. Can't test 1.2.4 as it is missing from the strawberry-downloads Github

        Hopefully that helps narrowing down the issue to some change between those 2 versions

        jonasJ 1 Reply Last reply Reply Quote 0
        • jonasJ
          jonas @palvji
          last edited by

          @palvji
          It most likely has to do with GStreamer or libsoup was upgraded in one of the versions that perhaps has introduced a bug.
          Can you try enabling "Enable HTTP/2 for streaming" in Tools / Settings / Backend. The default is to turn off HTTP/2 because of some issues in the past, but that should be resolved. Restart strawberry to make sure it's enabled, as this setting is a bit special, since not a normal setting but rather a environment variable set by strawberry that libsoup picks up.

          P 1 Reply Last reply Reply Quote 0
          • P
            palvji @jonas
            last edited by

            Thanks @jonas . It was actually the other way around, I had HTTP/2 enabled for streaming and when I disabled it the Buffering issue did not appear.

            With this setting disabled, it works in 1.2.5 and 1.2.7

            It looks like a bug when using that config. Let me know if you want me to open a ticket for it or test further, for now I'll use HTTP/1.1 👍

            Thanks again!

            jonasJ 1 Reply Last reply Reply Quote 1
            • jonasJ
              jonas @palvji
              last edited by jonas

              @palvji
              I can confirm this, just tested on Linux with HTTP/2, stuck on buffering after 54 seconds into the song when playing a tidal track.
              I'm guessing there is regression in one of the recent libsoup versions. I will do some more testing when I have more time.
              Luckily the default in Strawberry is still to force off HTTP/2 for streaming unless you manually check the HTTP/2 option in the settings.

              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Powered by NodeBB | Contributors