My issue appeared after the latest update. 3.3.4 In a playlist all songs from a particular album are skipped but that album will play if I find it outside of the playlist. It doesn't pause but skips. However once I try to play that track by selecting it in the playlist it skips again but then I lose control of the app. It won't respond to pause / play, if I select another track it ignores the command and continues wherever it was. Then while playing the visual track time indicators and track image is disconnected from what is playing, it plays but the screen shows the progress as playing until it reaches 10 seconds then goes back to 0 seconds and just repeats itself, visually. The actual track audio progresses to the next track while images are stuck in a loop. I have to shut the unit down to restore control. But if return to this list it does the same thing. I haven't yet experimented with other albums or playlists.
simultaneous playback issues
- Thread starter Grasshopper
- Start date
Hi Grasshopper, there could be a bug here with regards to the Now Playing losing sync with what is actually being played, so we may need to look into this.
In the meantime, to avoid this it would be best to amend your playlist so that the problem does not happen again.
It would be best to remove the tracks that are no longer available, and then go back to the original album and add them back on to the playlist again. This should fix it.
In the meantime, to avoid this it would be best to amend your playlist so that the problem does not happen again.
It would be best to remove the tracks that are no longer available, and then go back to the original album and add them back on to the playlist again. This should fix it.
Hi @Stephen Healy - FYI, I think I have also experienced this (these symptoms) also, since the v3.3.4 upgrade, which has been very atypical for me (in my Sense tenure). You eluded above (paraphrasing) "... there could be a bug here..". Thus, when convenient, can you advise (in this thread) if your engineers (i.e., Innuos digital team) have deemed this experience as an actual bug within the v.3.3.4 firmware? If so, it would give me (us) confidence that it was not a fluke (mental reassurance 
), and, satisfaction to know your team is tracking it down for resolution. Thank you..!
), and, satisfaction to know your team is tracking it down for resolution. Thank you..!
Last edited:
At the moment I am just speculating on the basis of what is described - we would need to try to repeat and replicate the behaviour first to confirm if this is in fact the case, or if not related to something else. It would be curious to be a result of 3.3.4 since that update made no changes at all to playback or queueing behaviour, it just amended a network DNS issue and Spotify playback. Nonetheless, I will try and get the QA team to replicate what is described above.Hi @Stephen Healy - FYI, I think I have also experienced this (these symptoms) also, since the v3.3.4 upgrade, which has been very atypical for me (in my Sense tenure). You eluded above (paraphrasing) "... there could be a bug here..". Thus, when convenient, can you advise (in this thread) if your engineers (i.e., Innuos digital team) have deemed this experience as an actual bug within the v.3.3.4 firmware? If so, it would give me (us) confidence that it was not a fluke (mental reassurance
To put it concisely, if a playlist contains several unavailable tracks then when they are reached in the queue, they are all skipped but then the player becomes unstable, and the Now Playing info loses sync with what is actually being audibly output?
Understood. Thank you! FYI - I may have experienced this (these atypical tracking issues) also in the v.3.3.3. , or perhaps it was just a network anomaly on my side that was the root cause. Not sure! I know recreating edge-case issues can be frustrating, so I can understand the elusive nature of identifying issues in code. Good luck there, and keep us updated here if/when possible. Thanks again!