Estimate Content Length When transcoding

[alanframe 0]

Hi

 

I've been trying to get DLNA to work with my Samsung UE22F5410 Tv. The problem I has is that whenever the movie has to be transcoded it fails to play and the TV displays a message saying to check my network connection.

 

After a few hours of playing about with profiles debug logs and traces in wireshark what I think is causing the problem is that Emby reports a content length of 0 when the TV does a http HEAD of the Stream.

HEAD /videos/b6be59fe490995b01904b5b10385cc2f/stream.ts?Params=a2ed389904dfe4a3272ce8a93b43ed2d;uuid:0b532b80-00be-1000-9438-0c89103337b9;b6be59fe490995b01904b5b10385cc2f;false;h264;ac3;1;;7680000;320000;6;30;1920;1080;0;41;;;;;;;;;b6be59fe490995b01904b5b10385cc2f HTTP/1.0
getcontentFeatures.dlna.org: 1
Host: 192.168.1.3:8096

HTTP/1.1 200 OK
transferMode.dlna.org: Streaming
realTimeInfo.dlna.org: DLNA.ORG_TLAG=*
TimeSeekRange.dlna.org: npt=0-6002.998/6002.998
X-AvailableSeekRange: 1 npt=0-6002.998
contentFeatures.dlna.org: DLNA.ORG_PN=MPEG_PS_NTSC;DLNA.ORG_OP=10;DLNA.ORG_CI=1;DLNA.ORG_FLAGS=01D00000000000000000000000000000
X-UA-Compatible: IE=Edge
Vary: Accept
X-Powered-By: ServiceStack/4.00 Win32NT/.NET
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS
Access-Control-Allow-Headers: Content-Type, Authorization, Range, X-MediaBrowser-Token
Accept-Ranges: none
Content-Type: video/mp2t
Server: Mono-HTTPAPI/1.0
Date: Fri, 08 May 2015 18:38:57 GMT
Content-Length: 0
Connection: close

So looking in the DLNA profiles I found a setting "Estimate Content Length When Transcoding" But Setting this does not seem to have any effect on the content length set by Emby.

 

Does any one have any idea if this is what this setting is intended to do? Or is it for something different. 

 

Or even better does anyone know how to fix this issue with a samsung tv ?

[Luke 42077]

i think actually what we need to do is make sure the content length is ommitted

[alanframe 0]

 Is omitting the content-length something I can configure now or is it something you were thinking of for a future release ?

[Luke 42077]

actually the new release adds the estimate for the head request. i don't think that's ideal and it would be better to have the content length omitted, i just had trouble getting that to happen because the http server always wants to supply one. so for now maybe what i did will help, if not will revisit later.

[crazybbs 24]

I've the exact same problem with content 0 byte and can't play anything who try to transcode on my samsung Un50Hu7000

 

I tried to play with profile for a week but didn't find any solution

 

To test this solution, Do I have to go to dev release? and do I have to set "Estimate Content Length When Transcoding" in profil?

Edited May 13, 2015 by crazybbs

[Luke 42077]

I've the exact same problem with content 0 byte and can't play anything who try to transcode on my samsung Un50Hu7000

 

I tried to play with profile for a week but didn't find any solution

 

To test this solution, Do I have to go to dev release? and do I have to set "Estimate Content Length When Transcoding" in profil?

 

How do you know it's the same problem?

[crazybbs 24]

Because I've the exact same symptom than him, I can't play any video transcoded failing to error on tv about network problem.

 

On emby dnla server,The samsung tv show all video who need to transcode like him format: mp2t lenght: 0 byte.

 

when the tv can direct play the file: I can see format: x-mkv and lenght , x.xGB and the file is playing well

[alanframe 0]

Just gave this a go and while it seems to have improved things I still get an error.

 

I successfully get past the head request and the tv issues a get request for the stream. Emby sends a 200ok and starts the stream but after 20 or so packets the TV resets the tcp connection.

 

The error on the tv says that the file is not supported at this time.

 

 

When comparing this to when it works via direct play Emby responds to the head request with a 206 partial content rather than a 200Ok could this be causing the problem ?

 

I'll try and post a debug log and capture tomorrow but my daughter wants her tv back now!