View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020750 | MMW 5 | Casting (Google Cast / UPnP) | public | 2024-03-22 00:53 | 2024-03-25 20:02 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Product Version | 5.1 | ||||
| Target Version | 5.1 | ||||
| Summary | 0020750: First time casting opens escalation window | ||||
| Description | When running MMW and attempting to cast to a Google Cast device for the first time, MMW pops up the rights escalation window! Is this intentional? It's a bit unexpected--especially on MMW portable. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I guess this hapens only when: - Media Sharing was disabled (and no server configured) during the install Wizard - '[x] Add Windows Firewall Exception' is checked (by default) Then when casting MediaMonkey founds that no server is running and it needs to run a server from which the local files can be served to the remote renderer/player, that's the reason for the firewall prompt.. Can you confirm this is the case? EDIT: Debug log would confirm this... |
|
|
I can confirm, when I installed MM 2024 and imported the DB from another install of MMW: - if the installation had no shared library, this situation would occur (since importing the existing DB causes the wizard to be skipped) - if the installation had a shared library, then the situation wouldn't occur (MM would prompt escalation right after the library was imported). So, the current behavior seems OK, _except_: why does MM have to run the server in order to cast?! |
|
|
>> except_: why does MM have to run the server in order to cast?!<< Yes, MM needs to run server in order to cast for local files, so that files like 'C:\Music\My.mp3' can be served as 'http://IP:Port/1.mp3' to the renderer |
