View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016780 | MMW 5 | UPnP / DLNA | public | 2020-07-02 22:01 | 2021-11-24 23:02 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | not fixable | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0.2 | Fixed in Version | 5.0.3 | ||
| Summary | 0016780: MediaMonkey shows as 'Default Media Receiver' when Chromecasting | ||||
| Description | When casting from MM5 to a chromecast video device, the screen shows the source as 'Default Media Receiver' instead of 'MediaMonkey'. Note that when casting from MMA, the source is correctly shown as 'MediaMonkey'. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=100035 Ticket # 3007 | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 2523 | ||||
|
|
Raised to 'urgent' since I suspect that this is just a text change. Ludek, please push to 5.0.1 if this isn't trivial. |
|
|
Yes, the framework that MMA uses seems to create own virtual app on the Chromecast (and uses it for playback). MM5 does not use any framework and uses directly the "Default Media Receiver" app on the Chromecast. |
|
|
Reopen This should be reviewed as based on https://developers.google.com/cast/docs/web_receiver and https://developers.google.com/cast/docs/styled_receiver it should not be too hard to implement server side Styled/Custom receiver |
|
|
Fixed in 5.0.3.2600 |
|
|
Merged to 5.0.2.2523 |
|
|
Verified 2523 MediaMonkey is now showed instead of 'Default Media Receiver' |
