View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 3 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sat Sep 19, 2015 10:53 am 
Offline
Joined: Wed Aug 18, 2004 7:06 pm
Posts: 21
Please see this ticket on the Kodi tracker:
http://trac.kodi.tv/ticket/14204

This is an issue that originally showed up in v12.1 and was fixed, but regressed for the v15 branch. There is now a fix for it in their git repository. The text from the above issue follows:
Quote:
A change in 12.1 systematically adds a RANGE tag to the video HTTP-GET request which breaks operation with non-seekable (live TV) DLNA DMS devices.

DLNA requires that a DMP (XMBC) *not* send a RANGE request to the DMS if the protocol info does not indicate the stream is seekable. The seekable-ness of the stream is detected by the presence or absence of DLNA.ORG_OP=xx. (If the stream is seekable the OP value will be non-zero. If not seekable the OP tag is absent).

Admittedly this is a brain-dead requirement because HTTP RFCs allow a server that does not support RANGE to ignore it... the problem is that DLNA certification process requires that a DLNA DMS reject any HTTP-GET request containing a RANGE tag when non-seekable content is selected (ie live TV).

So net result - 12.0 works well with the HDHomeRun, 12.1 does not play video, and the HDHomeRun must reject the 12.1 HTTP-GET request in order to maintain DLNA certification.

The fix needed is to detect the DLNA.ORG_OP=xx tag in the CDS protocol info... if OP value is present and non-zero then send a RANGE tag in the HTTP-GET. If the OP value is not present or 00 then do not send RANGE tag in the HTTP-GET and don't allow seeking.

Nick - Silicondust (makers of the HDHomeRun and DLNA member)

(scroll to the bottom of the ticket to see the recent activity)

I created a ticket here: http://linhes.org/issues/998 but I'm not sure if anyone actually reads that.


Top
 Profile  
 
PostPosted: Sat Sep 19, 2015 11:00 am 
Offline
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1995
Location: /dev/null
On my phone so I'm not going to read through the bug report. Is there a patch that can be applied or is this an upstream issue? If it's upstream, not much LH packages can do about it :/

_________________
Retired KM user (R4 - R6.04); friend to LH users.


Top
 Profile  
 
PostPosted: Sat Sep 19, 2015 3:30 pm 
Offline
Joined: Wed Aug 18, 2004 7:06 pm
Posts: 21
brfransen helped me out in irc. There's a patch and it's also in the current Kodi git. There's an updated package in testing right now, it's Kodi-15.1-2.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu