Samsung B Series does not display srt subtitles

My Samsung TV is a LE37B650 (a B series) : it is well recognized as is by Serviio (appropriate profile).
This TV can play AVI files with associated SRT files from a USB key. It is also the case through the TVMobili DLNA server (not fully "free" indeed).
However subtitles do not appear with Serviio.
Could fix something in the config for solving this issue ?

Thanks.

[zip]

Subs work with the B series. Can you enable detailed logging (see my signature) and try to play the file, then post the log here.

Sorry for a so long lapse between your answer and my reaction.
I run now Serviio 1.1
I've try to locate the issue :
When I start everything my Samsung TV (B) is well recognized as it is with the correct profile (#2) and srt subtitles are visible.
If 10 minutes later I stop my visioning and choose another movie (or the same) no more subtitles ... because Serviio is now confusing with its IP address and so its profile.
LAN situation:
a) my PC running serviio has a static IP address 192.168.0.1
b) my TV has a static IP address 192.168.0.30
c) both are directly connected by an ethernet cable to my ADSL router which have a preconfigured static address 192.168.27.14 (a freebox V5)
Both TV and servioo are well recognized (see DeviceSpy snapshot).
In fact the TV is correctly identified as 192.168.0.30 Samsung ... for 4 minutes : please look at both Serviio Console captures and you could see that after 4 minutes (more or less) the console does not see anymore 192.168.0.30 but the ADSL router address (192.168.27.14). The current streaming works well (with subtitles) but if a swith to another video it is not OK anymore.
This confusion appears when the serviio server refreshes something as the packets tracer indicates it.
If at this point I act on the address 192.168.27.14 (for example "disabling it" in the serviio console), the current streaming stops (of course) but if I start a new video (before the 4 minutes limit ) the TV is well recognized again under its own actual IP address (192.168.0.30) with subtitles. 4 minutes later this correct state vanishes and the wrong IP address appears again in the serviio console.
So the issue IS NOT ABOUT SUBTITLES but about IP addresses confusion at refresh time (every 4 minutes) assigning a bad generic profile instead of the correct #2 one (Samsung B).
I join:
Device Spy capture;
2 Console Serviio capture with 4 minutes of lapse between them;
The URL where you could download the quite long DEBUG log : however console serviio capture have been done later, so they are not in phase with the DEBUG log (the same issue is still inside). But believe me the story can be repeated as well with exactly the same effects.

https://docs.google.com/file/d/0B-4fLhb ... tJMXc/edit

Sorry to be long and I would appreciate you find a solution, Serviio is a good product ... and free. I would consider the pro licence when that issue will be solved. Do not hesitate to contact me, I will look every day on this post.

Regards.

Daniel Sportes

Just the other attachments.
The log file joint here is shorter as the one available on the URL of the previous post.
Thanks

Daniel

[zip]

why is the router on a different subnet? It obviously gives the TV 2 different IP addresses, one recognizes the right profile, then a second request comes with the same device id but different IP and it updates the IP to this new one. When you request a file on the TV it uses the original IP but it's not found in the list of the devices anymore and thus assigns it the generic profile.

Might also be a setting on the router.

First point : the subnet 192.168.27 is chosen by my provider (the Free company), not letting me any choice on that point.
"Usually", the normal subnet is frequently 192.168.0 and it's why I used it.

But the TV only has a single IP address 192.168.0.30, I never can reach it on a different address. More when I look on the network traffic the TV always send / receive packet on this address (of course).
DeviceSpy doesnt confuse them. A media server as TVMobili does not confuse them either.
So the question is : why Servio makes a confusion between the router and the TV ?

Is there a way to fix in the configuration that the IP address 192.168.0.30 is attached to the profile #2 (Samsung TV) ?

I just will try to assign a different address to the TV on the router subnet (192.168.27.30 for example), just for validating your suggestion.

Result in few minutes.

Thanks.

My ADSL router does not leave me to use the subnet 192.168.27
So I cannot install the TV on the same subnet as the Freebox but on the net nobody does that (of course) neither tried it.

The problem remains: why Serviio, ONLY AFTER FEW MINUTES, is replacing the TV address 192.168.0.30 by the router address as it appears in the Serviio console.
This confusion IS ONLY PARTIAL : Serviio perfectly manages video streams, routing them on the actual TV address in any cases. So the issue is only concerning the confusion about IP addresses for selecting the appropriate model (#2) and not at beginning (or few minutes after disabling manually the bad (router) address in the Serviio console).

No solution for the moment ?

Regards

Daniel

I examined a bit deeper the serviio log I sent you.
Just have a look on the extract I join here:
uuid=d77fcf8a-4085-016d-9875-c100b108b138 is the ID of the Samsung TV : line 3 it is found for the IP 192.168.0.30 (at 11:55:15,795)
Between lines 103 and 109 it allocates successively to 192.168.27.14 and 192.168.0.30 and remains to the 27.14 (unfortunately) (11:55:46,550 so 90 seconds later).
But the router (192.168.27.14) does not know this uuid (generated for the TV).
I could be supposed a bug when extracting the origin IP in the recognition sequence, taking the router address for the origin address.

Well it could easier to find out what happened in 10 lines ou log rather than in 1mo

Happy new year !

[zip]

could you capture packets coming from 192.168.27.14 to your Serviio PC on port 8895 with Wireshark? It's happening what I explained earlier, not sure what this request from the router IP is.

Hi,
I'm not really comfortable with WireShark but finally ...
I captured both IP addresses (router or tv):
Filter : host 192.168.27.14 or host 192.168.0.30

Scenario:
Serviio console running serviio server stopped
Start the WireShark capture
Start the serviio server
First Servioo console capture : TV recognized as 192.168.0.30
After this initial phase nothing move on the LAN
Then around 4 minutes later, packets are exchanged
Serviio console refresh
Second Servioo console capture : TV recognized as 192.168.27.14
When nothing move, stop the WireShark capture

URL of the WireShark pcapng : https://docs.google.com/open?id=0B-4fLh ... lhsblZaeDQ
If you need more traces, just say to me, but when video is exchanged the traffic becomes huge.

Thanks

Daniel

[zip]

I can't open the attachement in Wireshark (empty window). Does that work for you? try to zip it up and attach here

EDIT: I managed to open it, but it only shows traffic between 192.168.0.1 ( I assume your Serviio PC) and .30. Don't see any incoming traffic from the other IP. Did you have some filtering on?

I just restarted a Wireshark capture.

The TV was running : the uuid of the DLNA service is d77fcf8a ...

Just have a look on the two following screen captures of Wireshark:
1) a SSDP packet is sent from 192.168.0.30 (the TV) giving the uuid of its service
2) just after you see the same packet resent by the router 192.168.27.14. Of course inside the packet the "LOCATION" field is correctly giving the owner of the service ...
But let's suppose (it's just a supposition) that rather than using this LOCATION parameter for identifying the sender you used the Src info, then rather than attributing the service to the TV you attribute it to ... the router.
Of course on LAN without router this issue cannot appear. However such "boxes" are frequent on users LAN.
Do you have a different packet routing policy with other ADSL routers ?

I join her the two snapshot and I try in the next post to send the pcapng file in a ZIP.

The Wireshark capture file (a pcapng inside a ZIP).

[zip]

Thanks for this, it's useful.

Yes, this will be the problem. I also have a router (as most of people at home), but am not getting this behaviour (no incoming requests with the router IP). Perhaps it's a setting on the router, or a part of some network service on it?

The "router" is in fact a "Freebox" provided by the Free company with around 5,000,000 of customers.
The setting capabilty of this box is very limited: we may define redirection for port numbers, range of local IP DHCP addresses, and very few other very simple options but nothing advanced as defining policies for SSDP packets.
So nothing can be done at this level (unfortunately). It would be nice if you could fix that on your side and this will be useful for millions of users in France being so able to use Serviio.
I'm of course ready for testing a future fix on my network, (I suppose it's not easy on your side).
Regards.

Daniel