Restarted song may be skipped

Answered

Comments

6 comments

  • Official comment
    Tony W.
    Product Support Manager

    Hi Erland

    What you are seeing is unlikely related to your previous problem. Like your previous problem however, your best way to find a solution is select Send Support Request from the Settings menu of the App. This way our Support Crew can review the log file to see what is happening from the Player's event log. Once they review it they will provide feedback via e-mail.

  • Erland Sommarskog

    As I said, I have already submitted the support request.

    Yes, I agree that it is unlikely that there is a direct relation to the previous bug as that was corrected. (And things worked well for several months after the bugfix.) However, I still felt that it made sense to refer to back to that situation.

    0
  • SimonB

    I see the same issue. Very annoying. I'll try and send a support request from the app as well

    0
  • Erland Sommarskog

    My case is currently on hold. The support person couldn't repro it - well, I did not expect that. I had expected interest in looking at the information I had submitted, and also collecting more information.

    What I have found is:

    • I have been able to reproduce the issue on all my four pair of speakers.
    • The issue is much more prone to appear if the player is in standby. (I was not aware of that the players goes into standby when I submitted the case, but learnt from the support person, so that was a useful lead.) But it occasionally happens after the player being paused for just like two minutes, but less often.
    • When I have split the pairs, and played from a single speaker, the issue has not appeared on single speakers.
    • Possibly, but this needs more verification, the issue seemed to be less prone to happen on paired speakers when I had two of my pairs. I'm planning to unplug six of my speakers, and only play from one of them for a while to test this further.

    Since the behaviour is transient, troubleshooting is difficult.

     

    0
  • SimonB

    I reported my similar issue. I have a stereo pair of Pulse Mini's. 
    Was advised that it was because the players were being disconnected from my NAS, but that seems unlikely since the NAS does not sleep or disconnect clients, and the players skip to, and play, the next track, so obviously they can connect to the NAS. 
    Was then advised to factory reset the players. That hasn't resolved the issue, but now while playing a track they will skip to the next queued track. So now worse, generally

    0
  • Erland Sommarskog

    >  but now while playing a track they will skip to the next queued track.

    That's awful! I had that problem with playing from Spotify for a while, but when I came home after 3½ weeks of vacation, it was all gone. Thankfully, I have not had the problem with playing from the NAS. (With Bluesound. I had Sonos before, and whenever Sonos experience a network interruption, it opted to move on in the queue instead of just stalling.)

    My own case is progressing, if slowly. I played with settings in my router in attempt to escape from WiFi noise from neighbours (I live in a block of flats), but it does not seem to resolve the problem. But it so strange, because one day can be without skips, and the next day the skips occur almost everytime after a standby.

    The support person eventually asked for logs, and I had a skip earlier this morning, so I submitted logs. Looking the logs, I noticed this:

    Jul  8 08:31:09 (none) user.info ms [362]: proxy_codec.go:728: Stream connection timed out
    Jul  8 08:31:11 (none) user.info ms [362]: events.go:326: decodingFailed: streamId=1953
    Jul  8 08:31:11 (none) user.info ms [362]: grouping.go:1461: 192.168.145.171:11002 <- decodingFailed: from=192.168.145.172%3A11002&slaveId=192.168.145.172%3A11002&streamId=1953
    Jul  8 08:31:11 (none) user.info dspout: Command(l=5): F1953
    Jul  8 08:31:11 (none) user.info dspout: state=1 new_state=0
    Jul  8 08:31:11 (none) user.info dspout: Command(l=4): I100
    Jul  8 08:31:11 (none) user.info dspout: Command(l=5): I5000
    Jul  8 08:31:11 (none) user.info ms [362]: grouping.go:2125: trackClockSkew: invalid response: 

    Could be a clue. We'll see what Bluesound finds out.

    0

Please sign in to leave a comment.