View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016671 | MMW 5 | Playback | public | 2020-05-28 15:24 | 2022-02-26 16:24 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.1 | Fixed in Version | 5.0.2 | ||
| Summary | 0016671: Chromecast: improved usability in case of unavailable chromecast | ||||
| Description | In 5.0, if a chromecast devices is unplugged during playback 1) Once the CC is unplugged, MM continues to 'Play' to the unplugged Chromecast. Is it possible for MM to 'know' and stop the seekbar / generate an error message? 2) When new tracks start to 'Play', MM attempts to reconnect and generates an error for the track. Then when the user accepts the error, MM initiates playback for the next track over the same problematic connection. A more user-friendly approach might be to: a) Prevent selection of a chromecast device that's unavailable (grey it out) b) Modify the error message that appears so as to stop chromecasting. e.g. The 'xxx player' is turned off or inaccessible. [Try again] [Cancel] Try again: would use the current workflow Cancel: would STOP playback and switch to the internal player | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2500 | ||||
| related to | 0014585 | closed | Ludek | Support playing of YouTube files to Chromecast |
| related to | 0015068 | closed | Ludek | YouTube playback fails whenever user switches to remote player and back |
| related to | 0016611 | closed | Ludek | MM Player can't be used when Chromecast/DLNA device is turned off |
| related to | 0017235 | closed | Ludek | Fallback to internal player (when configured player is inaccessible) may be undesired |
| related to | 0017738 | closed | Ludek | 'DLNA Player is turned off or inaccessible' error appears for each track |
| related to | 0018223 | closed | Ludek | Casting: Failure to re-connect once Chromecast has been turned off |
| related to | 0018860 | closed | Ludek | Ability to auto re-connect during casting (once connection is lost temporarily) |
|
|
Fixed in 2260. i.e. if Chromecast is turned off during the playback then MM5 shows "The 'xxx player' is turned off or inaccessible." within 2 seconds, stops the playback and switches to the internal player. |
|
|
Verified 2260 This is clear expected behavior here playback can be easily continued by pressing play after MM5 switch to Internal. |
|
|
Re-opened: 2 seconds timeout is too low, as in some environments the device has not replied for 4 seconds for some reason and then continued replying: https://www.mediamonkey.com/forum/viewtopic.php?p=472202#p472202 Increasing the timeout to 10 seconds should resolve this. => Fixed in 2266 |
|
|
Verified 2266 Tested using Nexus Player and blocking WiFi Traffic on Router for a few seconds and then allow it again. No switch back to internal. |
|
|
Re-opened as based on ticket [Ticket # 2396] the 10 seconds timeout was still not enough. The user's device SoundShift stops replying for 15 seconds (from time to time) and after 15 seconds it starts to reply again (considered as accessible again). So increased the timeout to 20 seconds in 5.0.2.2500 |
|
|
Verified 2500 No regressions found during testing with Nexus Player. Test note: I blocked WLAN traffic to Nexus Player for 15 Seconds making it non accessible and when enabling it again it worked no timeout. Same process but left it for 25-30sec dialog showed. |
