Solved Issue with playback from NAS using Folders tab in Sense

[DanCollier]

We’ve had a user report an issue when playing music from their NAS specifically using the Folders tab in Sense. When selecting an album, only the first track plays before stopping. The user then has to press play again for the remaining tracks to continue.

This has been replicated and has been added to the backlog.

 

[Fitman-NJ]

We’ve had a user report an issue when playing music from their NAS using the Folder view in Sense. When selecting an album, only the first track plays before stopping. The user then has to press play again for the remaining tracks to continue.

This has been replicated and has been added to the backlog.

Dan, I don't know if a recent issue I've seen when using Sense is related, but In the last several days, Sense appears to play two songs in the Queue, then stops. If I'm diagnosing this correctly, the first of the two songs plays normally, but when the second begins, the time tracker at the bottom of the Queue screen remains at the far right (end of the song) and the pointer indicating which song is playing remains on cut #1.

At the end of the second song (which seems to sound audibly normal), Sense doesn't advance to cut #3 unless I click on that song, which allows the music to continue, but with the same behavior of the timer indicator stopping at the end of song #3, song #4 playing with the pointer still directed at cut#3, and the Queue pausing at the end of song#4.

This just began toward the middle/end of last week. Of course, I don't know if this is a "one-off" issue or if other users may be encountering the same behavior. I'm using Sense version 3.2.2. with an original Statement. This refers to music files stored on my internal hard drive (not Internet streamed). Thanks.

 

[rarebot6]

Dan, I don't know if a recent issue I've seen when using Sense is related, but In the last several days, Sense appears to play two songs in the Queue, then stops. If I'm diagnosing this correctly, the first of the two songs plays normally, but when the second begins, the time tracker at the bottom of the Queue screen remains at the far right (end of the song) and the pointer indicating which song is playing remains on cut #1.

At the end of the second song (which seems to sound audibly normal), Sense doesn't advance to cut #3 unless I click on that song, which allows the music to continue, but with the same behavior of the timer indicator stopping at the end of song #3, song #4 playing with the pointer still directed at cut#3, and the Queue pausing at the end of song#4.

This just began toward the middle/end of last week. Of course, I don't know if this is a "one-off" issue or if other users may be encountering the same behavior. I'm using Sense version 3.2.2. with an original Statement. This refers to music files stored on my internal hard drive (not Internet streamed). Thanks.

Interesting. This is remarkably similar to the problems I've been having trying to play from my Zenith Mk3 to my PC using squeeze-lx since the 3.2 version of Sense.

 

[Stephen Healy]

Dan, I don't know if a recent issue I've seen when using Sense is related, but In the last several days, Sense appears to play two songs in the Queue, then stops. If I'm diagnosing this correctly, the first of the two songs plays normally, but when the second begins, the time tracker at the bottom of the Queue screen remains at the far right (end of the song) and the pointer indicating which song is playing remains on cut #1.

At the end of the second song (which seems to sound audibly normal), Sense doesn't advance to cut #3 unless I click on that song, which allows the music to continue, but with the same behavior of the timer indicator stopping at the end of song #3, song #4 playing with the pointer still directed at cut#3, and the Queue pausing at the end of song#4.

This just began toward the middle/end of last week. Of course, I don't know if this is a "one-off" issue or if other users may be encountering the same behavior. I'm using Sense version 3.2.2. with an original Statement. This refers to music files stored on my internal hard drive (not Internet streamed). Thanks.

Can i check if this is playing straight out by USB to a DAC, or is this over SenseUPnP?

 

[Fitman-NJ]

Can i check if this is playing straight out by USB to a DAC, or is this over SenseUPnP?

What I'm seeing, Stephen, is from play straight out by USB to a DAC (RME ADI-2 DAC FS). After watching carefully yesterday while playing music, there's even more "unexpected behavior" than I described before. It's hard to say for sure what the pattern is to this behavior, if any. For instance, I added cuts from one album to the Queue. I then added cuts from a different album; IIRC, Sense repositioned the last cut of the first album after the first cut of the second album. When I left the Queue to edit the album I was playing, then returned, the time indicator seemed to resume proper operation and the pointer acknowledged the correct cut being played...until it reached the end of the song, at which point it stopped moving. The next cut would play under this specific condition (i.e., having left the Queue and then returned), but the playback would then stop after that song, requiring me to click on the following song to get it to play...resuming the "two song then pause" cycle. Puzzling...

I can't recall...did the most recent Sense update occur last week (I know there's a thread you have that announces new updates, but I don't want to lose this long note)? I backed-up my database last night, and have a second recent update in case the more recent one is corrupted. Is it possible to delete, then reload a fresh copy of Sense? I'm not sure exactly how I might try that since I don't believe Sense is downloadable from the Apple App Store. I do updates to Sense from within Sense itself.

Thanks!

 

[Stephen Healy]

What I'm seeing, Stephen, is from play straight out by USB to a DAC (RME ADI-2 DAC FS). After watching carefully yesterday while playing music, there's even more "unexpected behavior" than I described before. It's hard to say for sure what the pattern is to this behavior, if any. For instance, I added cuts from one album to the Queue. I then added cuts from a different album; IIRC, Sense repositioned the last cut of the first album after the first cut of the second album. When I left the Queue to edit the album I was playing, then returned, the time indicator seemed to resume proper operation and the pointer acknowledged the correct cut being played...until it reached the end of the song, at which point it stopped moving. The next cut would play under this specific condition (i.e., having left the Queue and then returned), but the playback would then stop after that song, requiring me to click on the following song to get it to play...resuming the "two song then pause" cycle. Puzzling...

I can't recall...did the most recent Sense update occur last week (I know there's a thread you have that announces new updates, but I don't want to lose this long note)? I backed-up my database last night, and have a second recent update in case the more recent one is corrupted. Is it possible to delete, then reload a fresh copy of Sense? I'm not sure exactly how I might try that since I don't believe Sense is downloadable from the Apple App Store. I do updates to Sense from within Sense itself.

Thanks!

Okay, this is different from what is outlined in the Known Issue above so please feel free to submit this over in a new post on the Help section - any screenshots/videos of this behaviour would be very helpful, thank you!

 

[Fitman-NJ]

Okay, this is different from what is outlined in the Known Issue above so please feel free to submit this over in a new post on the Help section - any screenshots/videos of this behaviour would be very helpful, thank you!

Ok, I will resubmit this in the Help section, but would it be useful to try to load a fresh copy of Sense in case it's been corrupted in some way? If so, how would I do this?

 

[Stephen Healy]

Ok, I will resubmit this in the Help section, but would it be useful to try to load a fresh copy of Sense in case it's been corrupted in some way? If so, how would I do this?

This is not something that you can do - and if turns out to be a bug on a wider OS level then it would not solve the issue either, so would be best if we take a closer look at your specific situation first and take it from there.
Update 3.2 came our around Feb 12th and the latest hotfix was back at the beginning of March, so am not sure if the symptoms you encounter correlate around this. Anyway, we can continue this on the Help section!