[mythtv-commits] Ticket #12284: Latest Trunk DLNA service not working anymore with Samsung TV's

[MythTV]

#12284: Latest Trunk DLNA service not working anymore with Samsung TV's
----------------------------------+-----------------------------
 Reporter:  tomi.orava@…          |          Owner:  dblain
     Type:  Bug Report - General  |         Status:  new
 Priority:  minor                 |      Milestone:  unknown
Component:  MythTV - UPnP         |        Version:  Master Head
 Severity:  medium                |     Resolution:
 Keywords:                        |  Ticket locked:  0
----------------------------------+-----------------------------

Comment (by stuartm):

 I've been doing some searching and it appears to be a well known problem
 with Samsung TVs that they won't play AVI and MKV over UPnP unless you
 tell them the file is actually MPEG*. In other words we can't make these
 files playable without device specific hacks, which I had hoped to avoid
 (we should be so lucky).

 They also seem to require a contentFeatures header despite the DLNA spec
 stating:
 {{{
 7.4.1.3.11.4.3
  Tolerance to unavailable contentFeatures.dlna.org header
 [GUIDELINE] If a Rendering Endpoint sends an HTTP HEAD or GET request
 using generic HTTP
 URLs including a valid getContentFeatures.dlna.org HTTP header, and if the
 response omits the
 contentFeatures.dlna.org HTTP header, then the Rendering Endpoint shall
 accept the response as
 if it included the header.

 [COMMENT]
 a) Some legacy devices have been designed to retrieve res at protocolInfo
 information using the
 contentFeatures.dlna.org header instead of using the available resource
 metadata. Generic
 HTTP URLs could point to servers located in the Internet, which are not
 capable of including
 this header in a response message.
 b) The contentFeatures.dlna.org HTTP header carries the same information
 as the
 res at protocolInfo property, which is always available for a Rendering
 Endpoint.
 }}}

 So only 'legacy' devices should expect to use the header and servers may
 be unable to provide it. That's the case currently for MythTV, our web
 server is decoupled from the upnp, requiring a hack to insert dynamic upnp
 headers into responses. I'm working on just such a hack.

 What stands out in the minidlna log is that it 'supports' a Samsung
 proprietary feature which appears equivalent to, but different in format,
 to the standard UPnP Shortcut feature (which we offer). I can try adding
 this custom Samsung feature and see if that makes a difference.

--
Ticket URL: <https://code.mythtv.org/trac/ticket/12284#comment:13>
MythTV <http://www.mythtv.org>
MythTV Media Center