View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016583 | MMW 5 | General | public | 2020-05-07 20:32 | 2020-05-15 03:40 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0016583: More clear setting for manual Add Media Server Dialog | ||||
| Description | 1. Currently according to #13540 we use this template for manual add of media server "http(s)://host:port/path_to_device_description_file.xml" To comply with point 8. of https://www.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/152/23/failure-to-connect-and-or-see-the-mediamonkey-upnpdlna-server I would rather change it to 'http://<DEVICE_NAME_OR_IP>:<DEVICE_PORT>/DeviceDescription.xml" and add tooltip: 'To manually add Media Server, please enter Local Server NAME/IP address and Server Port or Full URL to Media Server Description file. Common addresses are "http(s)://device_name:port/path_to_device_description_file.xml" ' maybe even add some real world examples. 2. As second change I would make is that if input omits "http://" and/or "path_to_device_description_file.xml" MM5 tries automatically tries to fill it and search for DeviceDescription.xml eg. if user enters "QNAPNAS:22222" or "192.168.1.200:22222" or "http://mediamonkey.mydomain.com:22222" MM5 would try to determine if there is an server there by automatically fill/append "/DeviceDescription.xml" in order to check for Device description file. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2248 | ||||
|
|
I agree that this can be improved, but the first step is to update the KB article so that it explains how the user can find the MMW Server IP Address and Port, and what to enter for the 'path to device description file'. I've just done so. As far as additional improvements to reduce the need for the KB article, the suggestions are in the right direction, though I'd tweak them a bit: 1. Both MMA and MM5 currently have the exact same template, so any changes should be made for both: "http(s)://host:port/path_to_device_description_file.xml" --> Option a) Dropdown: http / https Server IP address:port: __XXX.XXX.XXX.XXX:YYYYY__ [Tooltip: For example http://192.168.1.130:55963. You can find this in the server's settings.] Device Description file path: _DeviceDescription.xml_[Tooltip: For example rootDesc.xml. You can find this in the server's settings.] Option b) OR, if keeping it to a single line is preferred due to time constraints we can use the following though it'll continue to result in some questions: Device Destination: _http://<SERVER IP ADDRESS>:<PORT #>/DeviceDescription.xml_ Tooltip: This can usually be found in the server settings. For example: http://192.168.1.130:55963/DeviceDescription.xml or https://192.168.0.120:2865/rootDesc.xml 3. I think that the above reduces the need for other changes, however, it would still be a good idea if the MediaMonkey Media Server better communicated its settings. i.e. Tools > Options > MediaSharing > Server Name would show the full Device Description path. e.g.: instead of a column 'IP', show a column:Device URL and in it show: http://xxx.xxx.xxx.xxx:yyyyyy/DeviceDescription.xml OR If this takes too much space, add the following non-editable to the Server tab: Device URL: http://xxx.xxx.xxx.xxx:yyyyyy/DeviceDescription.xml |
|
|
We can certainly improve this (option 1a sounds good), but I believe that users will still have troubles adding non-MM servers anyway. Every server uses different path to device description file, e.g. WMP/Windows sharing: http://127.0.0.1:2869/upnphost/udhisapi.dll?content=uuid:a45d7878-92ed-11ea-bb37-0242ac130002 Synology NAS: http://192.168.0.16:50001/desc/device.xml Plex: http://192.168.0.10:32469/DeviceDescription.xml It can be seen in MM5 by using the three dots menu > Properties on the particular servers: https://www.dropbox.com/s/j0iq1lmhbltzkgw/screenshot%202020-05-10%2020.42.53.png?dl=0 BTW: There was already the auto-correction implemented, in the cases when user enters a bad link and the DeviceDescription.xml is missing then MM5 auto-adds the DeviceDescription.xml Was implemeted during 0015541 - 2a |
|
|
Implemented option 1a in 2248 |
|
|
Verified 2248 I didn't imagine it like that, but it is intuitive, clear much better than single line. 3. Is handled in 0016582 and related bugs regarding UI, this was more functional bug rather than UI. |
