View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013165 | MMW v4 | DLNA/UPnP | public | 2016-03-03 21:31 | 2016-04-06 10:04 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | sometimes |
| Status | resolved | Resolution | no change required | ||
| Product Version | 4.1.11 | ||||
| Target Version | 4.1.12 | ||||
| Summary | 0013165: MMW --> MMA --> Chromecast rendering fails | ||||
| Description | From 0011830: Ludek, please, after new MMA build 481 will be created, take a look on case when MMA try to play tracks from MMW library to chromecast, I mean: MMW(as library) -> MMA(as controler) -> Chromecast It seems that issue is on MMW side, because it's working when I use Windows Media Player as library. Working: WMP(as library) -> MMA(as controler) -> Chromecast MMW(as library) -> MMA(as controler) -> UPnP renderer | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I don't have Chromecast to test, but according to Martin's log MMW refuses (denies) the connection because it is connection from a new MAC address. '6C-AD-F8-A8-42-DF', 'Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36 CrKey/1.18.55065' Solution should be to enable [x] Share automatically with all new devices or accept the confirmation on MMW side (which can be easily overlooked). Another question is whether we shouldn't change the default of the [ ] Share automatically with all new devices to checked state. |
|
|
Martin confirmed that it was the access issue (access prompt not approved for the Chromecast device + [ ] Share automatically unchecked by default) The only issue that we found is 0013205 - fixed in 4.1.12 Resolving as "no change required" unless we want to change the default to '[x] Share automatically with all new devices' that was changed in the past. The reasons for the current default were discussed here 0009013:0032804 |
