View Issue Details

IDProjectCategoryView StatusLast Update
0017234MMW 5Playbackpublic2023-05-17 22:50
ReporterLudek Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version5.0 
Target Version5.1Fixed in Version5.1 
Summary0017234: Improve error messaging re failed casting
DescriptionCurrently if user plays a file to DLNA renderer or Chromecast and the device has an issue with playling the file then MM just show toast message:
"Playback failed: fileXXX.FLAC cannot be decoded"

MM should rather show the standard error message box and:
1) include name of the remote player in the error text and port number that need to be opened in the firewall settings, e.g.
Player <PlayerXXX> has an issue playing or accessing the fileXXX.flac.
Ensure that the port number <NNNN> is opened in your firewall settings and that the file format is supported by <PlayerXXX>

2) include [Help] button referencing KB article with casting issues (e.g. the firewall issue to be covered in KB article -- issue 0017232 )
Additional Informationhttps://www.mediamonkey.com/forum/viewtopic.php?p=475688#p475688
TagsNo tags attached.
Fixed in build2804

Relationships

related to 0017232 closedlowlander Add KB article for casting issues 
related to 0017766 closedLudek Casting: Failed playback on a remote device should have a clearer error 

Activities

Ludek

2020-12-16 15:36

developer   ~0060807

Assigned to Rusty to review the wording/messaging post 5.0 release and once the KB article is created ( 0017232 )

Ludek

2021-05-23 19:03

developer   ~0063402

Last edited: 2021-05-23 19:05

Part of this has been already improved in 0017766 , i.e. the item 1) to include name of the remote player (having trouble to play the file)


As for the item 2)
Maybe we could show just add the [Help] button within the toast message from 0017766 referencing the KB article from 0017232 (which currently seems https://www.mediamonkey.com/support/knowledge-base/mediamonkey-upnp-dlna/mediamonkey-upnp-server-inaccessible/ )

Ludek

2023-05-04 18:11

developer   ~0071728

2) fixed in 5.1.0.2804

peke

2023-05-17 22:50

developer   ~0071938

Verified 2 in 2804