View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021365 | MMW 5 | Casting (Google Cast / UPnP) | public | 2024-11-18 20:49 | 2025-12-15 21:14 |
| Reporter | Ludek | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | not fixable | ||
| Product Version | 5.0 | ||||
| Target Version | 2026 | ||||
| Summary | 0021365: MediaMonkey lists also Google cast speakers that are part of a pair | ||||
| Description | If you pair two speakers to be Left&Right to a pair using Google Home app then they appear only once in the list as a "pair" in Google Chrome, but in MediaMonkey they appear both as "pair" and "left" and "right", i.e. you can still cast separatelly to each speaker.. One can argue that this is an advantage and other might want to filter them out (like in Chrome).. Anyhow we haven't found a way how to detect this over mDNS, to be found... | ||||
| Additional Information | [Ticket # 7899] | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Crucially: There is no mDNS field that explicitly says “this device is part of a stereo pair” There is no parent/child relationship, group ID, or pairing flag exposed via mDNS Left/right role information is not exposed in a machine-readable way Why Chrome can hide them: Chrome does not rely solely on mDNS. It also: Uses Google Cast cloud APIs Has access to device topology and grouping metadata stored in the user’s Google account That pairing metadata lives outside of mDNS, which is intentionally lightweight and local-only. |
