|
|
Martin, I guess this happens just because you are using the cheat from 0007165 by setting port = 4000. This should not be an issue for normal users. I would recommend to not use that cheat while testing. |
|
|
|
Yes, I'm using port 4000 as it's much easier to test certain DLNA issues from behind the PC then to have to run all throughout the house to test on DLNA capable devices. That said, if this cheat is used MM still shouldn't list it's own DLNA server(s). Isn't there enough information to know the server is it's own server? |
|
|
|
This issue is just sub-issue of 0007165, MM shouldn't show it's own server at all in its own interface. That said MM is not expected to run with that cheat when port=4000. |
|
|
|
Despite using the port 4000 cheat (which others seem to be using too as it is very useful for troubleshooting) MediaMonkey should at least warn users when scanning files from its own Media Server if not hide it from the user in the Add/Rescan Files dialog. In the current situation a user could scan in the same file an infinite amount of times. |
|
