View Issue Details

IDProjectCategoryView StatusLast Update
0014791MMW 5Generalpublic2020-11-02 10:39
Reporterpeke Assigned To 
PriorityhighSeveritytweakReproducibilityunable to reproduce
Status closedResolutionfixed 
Summary0014791: Playback: Network tracks do not resume on wake up from sleep
DescriptionNetwork tracks do not resume playback on wake up from sleep.

Quote from ticket:
"When the track being played is on a local disk it does not skip to the next track on resuming from sleep, but continues to play to the end.

I have also attempted a further experiment: (with a track on the server playing) -> [Pause] -> [Sleep computer] -> (Later) [Resume from Sleep] -> (in Windows Explorer) [open connection to \\[SERVERNAME]\[SHARENAME]\[FOLDERNAME]] -> (in MediaMonkey) [PLAY]. In this experiment the paused track still plays for around 1 minute then skips to the next track in the playlist - even though opening the path in Windows Explorer verifies that the location is available."

This is most likely timeout issue.
Additional InformationOUG-702-14607
TagsNo tags attached.
Fixed in build

Relationships

related to 0014374 closedpeke MMW v4 WiFi-Sync: Incomplete/slow sync when some network files are inaccessible 

Activities

peke

2018-05-02 22:31

developer   ~0050174

User confirmed that it always happen on Network tracks only.

Ludek

2018-05-04 13:05

developer   ~0050194

Last edited: 2018-05-04 13:06

The default network access timeout (5s) probably isn't enough in the user's environment.
Asked him to do some experiments and increase NetworkAccessTimeout in MM.ini

Waiting for reply (OUG-702-14607) ...

Ludek

2018-05-31 13:37

developer   ~0050447

Last edited: 2018-10-01 13:55

Moving target to 4.1.23 (waiting for user's feedback...)

peke

2020-11-02 10:37

developer   ~0060036

Last edited: 2020-11-02 10:38

Verified 2272

In some rare cases when Server is in Sleep mode also and MM tries to access UNC path or Mapped Drive Increasing delay to 15s fixed the issue.

peke

2020-11-02 10:39

developer   ~0060037

Closing.

NetworkAccessTimeout changes fixes the issue and 5s is usually enough even for WiFi