View Issue Details

IDProjectCategoryView StatusLast Update
0021876MMAUPnP / Castingpublic2026-10-10 09:19
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status resolvedResolutionfixed 
Product Version2.1.2 
Target Version2.1.4Fixed in Version2.1.4 
Summary0021876: Casting: targets sometimes aren't found / playback fails if found (regression)
DescriptionThere have been reports from some users that casting fails since the update to 2.1.1.1290 (and that it works correctly if reverting to 2.0.5). Two related issues have been reported:
1) Casting targets often aren't detected
2) Even when they are detected, casting fails
Additional Information- Debug log UX72R1X4C7 (associated with review by Harald W in the Play store)
- Other reports of this at https://www.mediamonkey.com/forum/viewtopic.php?t=106051&start=15
TagsNo tags attached.
Fixed in build1335

Relationships

related to 0020861 closedmartin Casting may fail to discover available casting destinations 
related to 0021602 closedmartin MMA does not trigger device discovery on some devices 

Activities

martin

2025-11-28 12:06

developer   ~0080088

Last edited: 2025-11-28 12:09

After version 2.0.5 we switched to jUPnP, which is just a more maintained version of the previous cling UPnP.

The reason for the problem is not clear at the moment.
For some unknown reason the renderer was disconnected, but the main problem seems to be that it had a problem playing the provided MP4 file.
The renderer is a Panasonic TX-65MZ1500E.
I was unable to replicate it using MMW.
More testing is needed, I'm postponing it to version 2.1.2.

martin

2026-10-10 09:18

developer   ~0082929

Last edited: 2026-10-10 09:19

1) Casting targets often aren't detected- fixed by:
Repeated M-SEARCH during device discovery
Active search on dialog reopen
“Server Not Responding” replaces “Access denied”
Faster timeout for unreachable servers
Content reloads when server returns

2) Casting fails
All casting-related issues should be resolved by the fixes in version 2.1.3.

Fixed in build 2.1.4.1335