[mythtv-commits] Ticket #12767: Issues with DLNA clients

[MythTV]

#12767: Issues with DLNA clients
-------------------------------------+------------------------
 Reporter:  Dylan Walkden <dylan@…>  |          Owner:  dblain
     Type:  Bug Report - General     |         Status:  new
 Priority:  minor                    |      Milestone:  0.28.2
Component:  MythTV - UPnP            |        Version:  0.28.0
 Severity:  medium                   |     Resolution:
 Keywords:  dnla upnp                |  Ticket locked:  0
-------------------------------------+------------------------

Comment (by Steve LeBlanc <sj.leblanc@…>):

 Thanks for the extended testing and feedback.

 The 'us' patch was actually the previous patch suggested in this ticket
 (which I had applied). Agree that the comparisons for the other countries
 should probably be treated the same.

 Regarding the 'static thumbnails' and the 'format' - this is probably due
 to the 'protocolInfo "fourth field"' that I had to remove to allow my
 older devices to operate. Looking at the spec - I'm not sure if there is a
 version indicator or something that could be parsed from the request to
 indicate weather to include the 'fourth field' or not. One approach to
 addressing this might be to add a upnp 'settings' parameter - indicating
 to include the 'fourth field' or not. Any thoughts?

 I was actually thinking that the same approach may make sense for
 combining the title/subtitle in the 'title' displayed for 'recorded' upnp
 items. Right now - the recording title for a recorded item is just the
 series name. One might argue that for a recorded item - actually combining
 them makes sense. The patch I included only combines them if the client
 has not requested the 'subtitle' field. If using a setting parameter - I'd
 actually combine the values in 'upnpcdstv.cpp' - so the combined title
 would show up everywhere. Thoughts?

 One other change I've tested locally allows VLC on Android and Windows 10
 to see myth as a upnp device and play recordings. The change just allows
 entries in the serviceList to include the leading URL separator. I've
 looked at what a number of other servers pass for this field - some have
 complete URL's, some have a leading slash - some nothing. Is the UPNP spec
 that hard and fast? Lots of examples actually have this leading slash!
 Thoughts?

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