Universal Media Server | Forum

From my experience with other applications when wrestling with the headache-inducing labyrinth of frustration that is DLNA, the issue is not on the TV. I have made the mistake of suspecting the TV before, and I always turned out to be wrong - it's always an issue on the computer-side of things (not necessarily UMS). Much to my surprise, the TV is always innocent and generally works perfectly. Even so, here's what I tried on the TV side: Hard reboot, firmware update (it was already the latest version), checked that the network connection is correct, functioning and stable. The TV is also capable of seeing another DLNA device on the network at the time the issue is taking place.

So here we go. UMS. Worked wonderfully on several occasions. Then I had to turn off my computer in order to switch to a new computer case. No other hardware was changed. I turned the computer back on, and now streaming no longer works - it never worked again.

The symptom is as I described in the title - the TV's DLNA client application no longer lists UMS. The TV is a Panasonic Viera 32AS600. In the network its IP address is 192.168.1.68 . According to the logs, it is trying to connect to UMS. UMS will also show the TV under renderers if I wait a long time or restart the DLNA client app on the TV (It's called "media server" in this version).

So what have I tried on the UMS side? I tried turning my computer off and back on again, to begin with. I confirmed again that windows 7's broken built in DLNA server is still turned of. I confirmed that the port (5001) is not in use by another application. Incidentally, here's netstat at the time I write this (UMS is running):
On occasion other sockets are listed in TIME_WAIT status. I also tried changing the port (didn't help). I updated UMS (there was a newer version) and installed with the default settings. Didn't help. I set the Panasonic AS600 renderer as default. I forced the LAN interface on UMS (made no difference).

What else can I try? I'm a software developer and I'm used to debugging issues from incredibly obscure reports, so instead of contemplating suicide as I would please feel free to ask for anything you may need.

For generating the attached logs I followed this procedure:

1. I turned on UMS. The TV is on and the Media Server app is open; there is a connection in the log from 192.168.1.68, but there is no renderer listed in UMS.
2. I changed the log level to TRACE (It doesn't *save* on TRACE, which is kind of a pain if you want to capture the startup?).
3. I clicked restart server. There is still no renderer listed in UMS.
4. I closed and reopened the Media Server app on the TV.
5. Shortly afterwards, UMS detects the renderer, which is visible in the full log but not in the interface log. The renderer is listed in the first tab. The TV still does not see UMS.
6. Packed debug files

meep

Hi protected, thanks for the report.
We have recently changed some detection/connection code. Can you please do the following to test:

1) Download and install this version: http://www.spirton.com/uploads/UMS/UMS-d9dd580.exe
2) Shut down UMS, set this in Panasonic-Viera.conf and restart if no luck, shut down UMS again, change it to this and restart If still no joy, shut down UMS again, set this in UMS.conf and restart Remove the settings afterward if they're not effective, and TRACE logs for each test would be great .

General info: None of the tests was successful on the TV side. All of the tests involved restarting the app on the TV after [main] The server is now available for renderers to find .

I started by installing your version. I used a clean install, then I started the application, added a folder with video in it and ran a scan. Then I tried setting the log level to TRACE in UMS.conf and restarted, but it was still in debug, so for the following tests I used the create trace log button to restart in trace mode. I always waited a few minutes before packing the logs, and the TV never showed up in the first tab.

allow=postpone: allow=false: Then I ran with upnp disabled but it was still enabled according to the logs, which was confusing until the penny dropped and I realized I had to use the UMS.conf in C:\ProgramData\UMS (I discarded this log). From then on I was able to finally start the application in TRACE log level by running it from the shortcut I tried a control run with all the default settings and for which I hard restarted the TV by cutting the power to the surge protector for 10s using the hardware switch.

And finally with upnp disabled in UMS.conf (correct run):
Since at this point I had yet to see the TV in the application at all, which is worse than yesterday, I decided to try setting the default renderer to the Panasonic AS600 and ticking force default renderer. Here is the result for that test:
This time the TV showed in the first tab for the first time today after restarting the app on the TV (but still not listed on the TV).

I then ran the upnp allow tests again, while keeping force default renderer enabled and adding them to Panasonic-VieraAS600E.conf instead.

allow=postpone:

allow=false: (I can also see the TV in the first tab of the application on this final test.)

Any new insights?

(EDITS: Forum inline attachment tags are broken, they insert tags with contents that are ignored and mismatched with the files they actually link to...)

protected wrote:Any new insights?

It's not entirely clear from your descriptions/logs what, if anything, is transpiring/attempted on the panasonic side in each test. I'm assuming UMS is still not visible regardless?

I know it's not explicitly stated in the instructions , but with UpnpAllow=postpone/false and upnp_enable=false, UMS reverts to its old-style 4.x behaviour, i.e. waiting more-or-less passively for the renderer to initiate requests (and the status tab will show nothing until then), and so part of the "test" would be to search for ums on the renderer and (if found) attempt to browse.

Correct, the Panasonic still doesn't see UMS but sees the other DLNA device (router capable of streaming videos from an USB drive). Previously it saw both.

protected wrote:Previously it saw both.

Thx , we have reports of this problem but so far haven't been able to reproduce it ourselves. It would be helpful if you could be a little more precise: "previously" = which version of UMS?

I don't remember which version I had before, but it was downloaded and installed about a month ago. There was no upgrade that caused the issue to start happening - the same version first, worked, then didn't work anymore (after reboot). While trying to fix the problem a couple of days ago I upgraded to the current version using the program interface (there was an upgrade available). I'm sorry to say I didn't write that one down either, but the issues persisted. Right now I have the build you posted in this thread, says build date was today!