View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014712 | MMA | UPnP / Casting | public | 2018-04-04 15:17 | 2018-05-25 23:39 |
| Reporter | rusty | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.3.2 | ||||
| Target Version | 1.3.2 | Fixed in Version | 1.3.2 | ||
| Summary | 0014712: Chromecasting fails on certain files | ||||
| Description | On certain files (I noticed this with an MP3 file by the red hot chili peppers), chromecasting fails as follows: For tracks A, B, C where B is the problematic track - track A plays - at the conclusion of track A, track B appears but fails to play - track B remains displayed and sometimes track C starts to play (but playback controls fail to get the correct track to display) other times playback stops (and attempts to play/pause/advance sometimes work and sometimes don't). Assuming that the failure of Track B to play is a problem with the track, MMA should still deal gracefully with that situation--i.e. it should just skip the track and none of these secondary issues should occur. Log ID: CMDYDSDZBM Description: Chromecast playback doesn't work Sample problem file posted to the ftp server. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 816 | ||||
|
|
Resolving, because the issue is not on MMA side. I have tested the track with Chromecast 1 and Chromecast 2 Ultra. No issue on my devices, the track is playable. From your debug log, we are not able to fix issues like this, when chromecast stops responding. MMA is still connected to chromecast, but chromecast does not accept any command. User has to reconnect manually(It's hard to recoginise this situation and workaround it and Workarounds causes new issues). Never happened to me with chromecast 2, time to time with chromecast 1 during testing. I guess new firmware can fix it. |
|
|
I tested this with chromecast audio devices (g2 devices) running the latest 1.30 firmware and the bug consistently occurs. However, it doesn't occur with chromecast video (g2) running 1.29 firmware. Furthermore the bug occurs with BubbleUPnP in exactly the same manner. All this to say that it definitely looks like a chromecast bug. That said, it would be great if MMA could detect the occurrence of such issues and re-initiate playback on 'good' tracks. Alternatively, if MMA could at least explain to the user what happened, then the user could know that the track in question is causing a problem for the chromecast device. e.g. "The Chromecast device is not responding. This may have been caused by the track 'xxxxxx.yyy'. Please disconnect and reconnect to the chromecast device to resume playback on a different track." |
|
|
I have added improvements and I hope MMA skip invalid track before Chromecast freeze, otherwise, detection is too complicated and risky to regression. Fixed in build 1.3.2.816 |
|
|
Verified 816 No regressions on Nexus Player. |
