Music keeps stalling/hanging

This topic contains 13 replies, has 4 voices, and was last updated by  Heiner Moderator 3 days, 14 hours ago.

Viewing 14 posts - 1 through 14 (of 14 total)
  • 21. August 2017 at 11:01 #30707

    After about a song or two of playback, my music pauses for about 10 seconds then come back on. It usually stays ok for a minute or two, then stall again for even longer. It continues to get worse and worse till it is barely playing at all.
    Often the buttons are unresponsive at this time too.
    I have noticed it during spotty playback, and also during airplay.
    Not sure about NAS streaming music yet

    Ryan

    21. August 2017 at 13:26 #30721

    Hi Ryan,

    Please have a look at your Health Checker during these issues and report back.

    21. August 2017 at 21:40 #30755

    What is the health checker and how do I look at it?
    thanks
    Hilary

    22. August 2017 at 6:48 #30756

    Hi Heiner,

    I can’t find the health checker either. Is it available on the raspberry pi?

    22. August 2017 at 9:22 #30766

    Hi guys,

    You should find in the Settings/Reboot menu in our current version. Here is our announcement: https://www.max2play.com/en/2017/04/health-checker/

    8. September 2017 at 10:05 #31189

    Hi Heiner,

    First of all big thank you for the great support you and the team are giving. That’s marvelous!

    With regards to the issue mentioned in this thread: I have the same issue, and have screened the forum, have found it on a couple of threads but I didn’t find a solution.

    My constellation: Pi 3, current m2p image, airplay settings, hifiberry amp+ card. Great sound, works like a charm, however, hanging/dropouts every now and then. The stream continues silently, as the music sets in again as if nothing had happened. Health checker green during these intervals of about 6-10 seconds.

    Would you be able to help?

    Thank you again

    Roger

    8. September 2017 at 11:57 #31208

    Hi Roger,

    Thanks for the kind words.

    Please first try disabling build-in audio in the Raspberry Settings. However, in your case there can be a lot of factors. Including the cable to the passive speakers, the speakers themselves, the AirPlay device, the WiFi or LAN connection. Please try isolating and switching some of these factors around if you are able to, to rule them out as sources of error. Also, if you are not using it, perhaps deactivate Bluetooth as well.

    8. September 2017 at 22:11 #31226

    Hi Heiner,

    Thank you for the advise. Following comments/questions from my side:

    1) Reg the recommendations:
    – disabled built-in audio
    – connected different speakers
    – checked cables
    – ran everything with other distro (was stable, but clearly inferior to m2p with regards to features)
    – disabled bt, wifi
    => all with no improvement, but only showing that hardware setup is ok

    2) Question: have there by any means been solutions for the hangs/stalls that other users reported? Also in other threads? If yes, what helped them?

    3) My current findings:
    – after some research I found that shairport is no longer maintained since 3+ years
    – however, there are two dozen forks of which mikebrady/shairport-sync is the active one
    – I replaced shairport on m2p with shairport-sync and – bingo! – it’s working fine

    Maybe something to consider in m2p next update?
    Happy to test if you are to issue a beta.

    Thank you

    Roger

    11. September 2017 at 14:16 #31260

    Hi Roger,

    Thanks for the detailed follow-up.

    Your issue of stalling/hanging music playback has come up a lot of times in this forum. The recommendations I mentioned have all been the root of the problem for some users that have posted here. However, the issue is very vague and can thus stem from all kinds of issues.

    The fix that you have found for yours is peculiar as the shairport instance we have running has been stable and reliable for a few years.
    Nonetheless, we appreciate the feedback and will look into a possible replacement. We will let you know, when a new beta is available for testing.

    Thanks 🙂

    13. September 2017 at 14:35 #31306

    Hi Roger,

    Quick update: I confirmed with our head developer that indeed the version of Shairport installed on our current Max2Play is already Shairport-Sync. However, we will further update to the newest version 3.1.2 and add some info in the debug log to include this.

    13. September 2017 at 15:28 #31310

    Hi Heiner,

    Thank you, very kind to letting me know. Will test the update once available.
    Seemingly you renamed the executable as the process is called shairport and not shairport-sync. But that is good to know.

    14. September 2017 at 11:45 #31320

    Yes, we will also try to indicate the version and name more clearly in a future update.

    17. September 2017 at 11:21 #31357

    Heiner,

    Digged a bit deeper in this and the following might be helpful for your developers.

    1.) Logged with shairport -vvv and receive all regular log, but this is faulty:

    RTP: Packets out of sequence: expected: 20714, got 20716.
    RTP: Packets out of sequence: expected: 20769, got 20772.
    RTP: Packets out of sequence: expected: 20773, got 20780.
    RTP: Packets out of sequence: expected: 20846, got 20847.
    requesting resend of 1 packets starting at 20714.
    requesting resend of 1 packets starting at 20715.
    requesting resend of 1 packets starting at 20769.
    requesting resend of 1 packets starting at 20770.
    requesting resend of 1 packets starting at 20771.
    requesting resend of 1 packets starting at 20773.
    requesting resend of 1 packets starting at 20774.
    requesting resend of 1 packets starting at 20775.
    requesting resend of 1 packets starting at 20776.
    requesting resend of 1 packets starting at 20777.
    requesting resend of 1 packets starting at 20714.
    requesting resend of 1 packets starting at 20778.
    requesting resend of 1 packets starting at 20715.
    requesting resend of 1 packets starting at 20779.
    requesting resend of 1 packets starting at 20714.
    requesting resend of 1 packets starting at 20715.
    requesting resend of 1 packets starting at 20714.
    requesting resend of 1 packets starting at 20715.
    requesting resend of 1 packets starting at 20769.
    requesting resend of 1 packets starting at 20714.
    requesting resend of 1 packets starting at 20770.
    requesting resend of 1 packets starting at 20715.
    requesting resend of 1 packets starting at 20771.
    requesting resend of 1 packets starting at 20773.
    requesting resend of 1 packets starting at 20774.
    requesting resend of 1 packets starting at 20775.
    requesting resend of 1 packets starting at 20776.
    requesting resend of 1 packets starting at 20777.
    Aliasing of buffer index — reset.
    Player: packets out of sequence: expected: 20714, got: 21226, sync error: 0 frames.
    Lost sync with source for 4 consecutive packets — flushing and resyncing. Error: -6287.
    Flush requested up to 5399129. It seems as if 0 is special.
    syncing to seqno 21619.
    CSeq: 124.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 125.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 126.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 127.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    RTP: Packets out of sequence: expected: 27513, got 27515.
    RTP: Packets out of sequence: expected: 27578, got 27579.
    requesting resend of 1 packets starting at 27513.
    requesting resend of 1 packets starting at 27514.
    requesting resend of 1 packets starting at 27513.
    requesting resend of 1 packets starting at 27514.
    requesting resend of 1 packets starting at 27578.
    requesting resend of 1 packets starting at 27513.
    requesting resend of 1 packets starting at 27514.
    requesting resend of 1 packets starting at 27513.
    requesting resend of 1 packets starting at 27514.
    requesting resend of 1 packets starting at 27513.
    requesting resend of 1 packets starting at 27514.
    Aliasing of buffer index — reset.
    Player: packets out of sequence: expected: 27513, got: 28025, sync error: 0 frames.
    ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
    Error -32 in delay(): Broken pipe. Delay reported is 0 frames.
    Lost sync with source for 4 consecutive packets — flushing and resyncing. Error: -6254.
    Flush requested up to 7792377. It seems as if 0 is special.
    syncing to seqno 28416.
    CSeq: 128.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 129.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    culling threads.
    New RTSP connection on port 5000
    Apple-Challenge: VQzJdlgSdxv+NjMZNak8Fg.
    CSeq: 1.
    Client-Instance: 409A007CF03B5253.
    Content-Length: 574.
    Content-Type: application/sdp.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    Already playing.
    CSeq: 2.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    Client-Instance: 409A007CF03B5253.
    This RTSP conversation thread doesn’t think it’s playing, but it’s sending a response to teardown anyway
    RTSP shutdown requested.
    Now closing RTSP connection.
    This RTSP conversation thread doesn’t think it’s playing for a close RTSP connection.
    Now terminating RTSP conversation thread.
    culling threads.
    one joined…

    2.) Have been streaming with Android AirAudio. Read in the log, that latency per default is 1sec. Changed this from 2 to 1 in AirAudio. Dropouts improved but still occured. See further log:

    RTP: Packets out of sequence: expected: 7083, got 7084.
    RTP: Packets out of sequence: expected: 7145, got 7148.
    requesting resend of 1 packets starting at 7083.
    requesting resend of 1 packets starting at 7083.
    requesting resend of 1 packets starting at 7083.
    requesting resend of 1 packets starting at 7083.
    requesting resend of 1 packets starting at 7145.
    requesting resend of 1 packets starting at 7146.
    Aliasing of buffer index — reset.
    Player: packets out of sequence: expected: 7083, got: 7595, sync error: 0 frames.
    Lost sync with source for 4 consecutive packets — flushing and resyncing. Error: -6192.
    Flush requested up to 23669689. It seems as if 0 is special.
    syncing to seqno 7736.
    CSeq: 152.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    RTP: Packets out of sequence: expected: 9100, got 9101.
    requesting resend of 1 packets starting at 9100.
    requesting resend of 1 packets starting at 9100.
    requesting resend of 1 packets starting at 9100.
    requesting resend of 1 packets starting at 9100.
    Aliasing of buffer index — reset.
    Player: packets out of sequence: expected: 9100, got: 9612, sync error: 0 frames.
    ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
    Error -32 in delay(): Broken pipe. Delay reported is 0 frames.
    Lost sync with source for 4 consecutive packets — flushing and resyncing. Error: -5667.
    Flush requested up to 24379673. It seems as if 0 is special.
    syncing to seqno 9751.
    CSeq: 153.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 154.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 155.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 156.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 157.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 158.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    RTP: Packets out of sequence: expected: 20439, got 20441.
    RTP: Packets out of sequence: expected: 20498, got 20506.
    requesting resend of 1 packets starting at 20439.
    requesting resend of 1 packets starting at 20440.
    requesting resend of 1 packets starting at 20439.
    requesting resend of 1 packets starting at 20440.
    requesting resend of 1 packets starting at 20439.
    requesting resend of 1 packets starting at 20440.
    requesting resend of 1 packets starting at 20439.
    requesting resend of 1 packets starting at 20440.
    requesting resend of 1 packets starting at 20498.
    requesting resend of 1 packets starting at 20499.
    requesting resend of 1 packets starting at 20500.
    requesting resend of 1 packets starting at 20501.
    requesting resend of 1 packets starting at 20502.
    Aliasing of buffer index — reset.
    Player: packets out of sequence: expected: 20439, got: 20951, sync error: 0 frames.
    Lost sync with source for 4 consecutive packets — flushing and resyncing. Error: -6229.
    Flush requested up to 28371001. It seems as if 0 is special.
    syncing to seqno 21092.
    CSeq: 159.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.
    CSeq: 160.
    Client-Instance: 0DA5CFCFDDC458D8.
    Session: 1.
    User-Agent: iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4.

    3.) Tried with AirPlay from Apple device, MacBook Pro in this case, both from itunes and from webplayer via system wide settings.
    No dropouts here.

    So: seemingly a sync issue with non proprietary AirPlay sources. Tried also Allstream as alternative app. Also dropouts. Didn’t look into log with this, but likely similar.

    This all with original version of shairport sync in your latest build. I think it’s 2.8.0. shairport sync.

    Maybe your guys have some ideas on how to further deal with this?

    Thank you,

    Roger

    18. September 2017 at 15:49 #31380

    Hi Roger,

    Thanks for the update and the detailed log you shared. We will keep testing the newest version and see whether we can recreate them.

    For now you can still make a beta update to get to our newest version.

Viewing 14 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic.

Register here