0014505: Network Playback: Non Accessible tracks block Playback - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0014505	MMW v4	Player	public	2017-10-30 22:11	2023-03-06 19:31

Reporter	peke	Assigned To
Priority	urgent	Severity	block	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	4.1
Target Version	4.1.20	Fixed in Version	4.1.20

Summary	0014505: Network Playback: Non Accessible tracks block Playback
Description	1. If user tries to play track from network location using double click in track browser (Clear List and play selected) that is not available and on Prompt That track is non available User click Ignore playback can't be restarted not track for some time. 2. In some cases when user user clicks on network track and network path is not accessible ATM (WD Live Goes to standby or HDDs on NAS are powered down) MMW Throws Track is not accessible and Ignore needs to be pressed. This is very rare.
Steps To Reproduce	Tracks needs to be on network under Computer name not by IP eg. \\MYNAS\Music\ and that should not be accessible eg. not seen under Windows explorer Network Tree node and warning for non accessible tracks should be enabled in MMW 1. Double click on Inaccessible track 2. Ignore warning 3. Now Playing is locked and you can't add/play tracks even they are on local HDD for some time 4. Quickly try to play other tracks till it finally plays.
Tags	No tags attached.
Attached Files	bug14505.jpg (27,932 bytes) bug14505.jpg (27,932 bytes)

Fixed in build

peke 2017-10-31 10:20 developer ~0049089	Note: Bug 2 only shows once and after user click ignore it plays track and do not show anymore.

Ludek 2017-10-31 10:49 developer ~0049090 Last edited: 2017-10-31 12:01	As debugged offline, Peke tested two inaccessible domains \\QNAPNAS\ and \\192.168.0.250\ while 192.168.0.250 is only temporary inaccessible (for 5 seconds) The only difference is: - in MMW 4.1.17 the play thread was frozen for 5 seconds until the 192.168.0.250 becomes accessible - in MMW 4.1.19 the play thread shows the inaccessible prompt after 2 seconds and played the track on the next try The 4.1.19 behaviour seems better to me, but Peke argues that with the prompt disabled it will skip the track. But IMHO it still seems better than waiting infinetely (in 4.1.17 it could take 15 seconds or more for the domain to become accessible) Peke is suggesting to increase the "accessibility timeout" from 2 seconds to 5 seconds for 4.1.19 and add INI config for it. BUT the same "accessibility timeout" is used for browsing the network shares too (where 2 seconds seems better than 5 seconds), tag reading etc. Because the accessibility check is in many places in MMW code and is hard to decide the access purpose then I would just leave 2 seconds as is now. We can add the INI config for it, but doesn't seem to be so important IMHO.

Ludek 2017-10-31 11:19 developer ~0049091	Added AccessibilityTimeout=2000 INI switch for 4.1.20.1860 and 5.0.0.2082

Ludek 2017-12-19 08:44 developer ~0049433 Last edited: 2017-12-19 08:44	Based on further testing/issues (like 0014594) it seems that adjusting the timeout from 2s to 5s (as previously suggested by Peke) is reasonable. Increased to 5 seconds in build 4.1.20.1860 Also renamed the INI switch to NetworkAccessTimeout=5000 (to force use of the new default)

peke 2017-12-19 13:20 developer ~0049440	Verified 1860