2013-08-29, 09:28 AM
Want to play with something, where is teh class file that is used when making the live call. I'd like to try changing to Content-Length to Content-length.
NextPVR Forums
Public
NextPVR Other Clients
Old Stuff (legacy)
NextPVR Enhanced Web Admin (NEWA)
NEWA Web Services
NEWA Web Services
|
2013-08-29, 05:15 PM
Only NEWA source is available. The server-side XBMC and http interfaces from sub are closed source but I expect you could make that change with a binary editor.
Martin
2013-08-29, 05:46 PM
Yeah, unfortunately that stuff all in the core application so the source isn't available.
If you're running the current pre-release, I can provide a patch for you to see if it helps. It is already using the "Content-Length" though, which is the standard header name for HTTP. Code: // send HTTP response header
string responseHeader = "HTTP/1.1 200 OK\r\n" +
"Server: NextPVR\r\n" +
"Connection: Close\r\n" +
"Content-Length: " + contentLength + "\r\n" +
"Content-Type: video/MP2T\r\n\r\n";
2013-08-29, 06:47 PM
Yes nextpvr is using Content-Length. I'm trying to find out if plex is after that or if its a case varian of that Content-length for example
I tried the transcode and was getting the same problem. And I can't call the local file with plex either. Kinda painful.
2013-08-29, 11:34 PM
psycik Wrote:Yes nextpvr is using Content-Length. I'm trying to find out if plex is after that or if its a case varian of that Content-length for exampleIf Plex isn't using case-insensitive matching on header fields then it's broken. HTTP header fields are case-insensitive.
2013-08-29, 11:42 PM
bgowland Wrote:If Plex isn't using case-insensitive matching on header fields then it's broken. HTTP header fields are case-insensitive. thats my uneducated guess. All I know is plex is reporting invalid content length - but also I seems to be going the wrong place. I've got someone looking at it there as well.
2013-08-30, 01:57 AM
So I've had some success finally:
http://forums.plexapp.com/index.php/topi...ntry454849 Is there an equivalent call to the http://<ip>:8866/live&recording=<oid> for live tv, ie activating a tuner? Its not supposed ot work but I may as well give it a try.
2013-08-30, 01:59 AM
Oh and martin, I may need to pick your brains regarding dealing with the web services for listing recordings....my python is pretty limited.
2013-08-30, 02:38 AM
psycik Wrote:Is there an equivalent call to the http://<ip>:8866/live&recording=<oid> for live tv, ie activating a tuner?Yes, http://<server>:8866/live?channel=2
2013-08-30, 02:38 AM
The python source in x-newa should show you everything you need. The raw interface is easier and I'm moving some calls to it
Code: import xml.etree.ElementTree as ET
import datetime
url = "http://ip:8866/services?method=recording.list&filter=Ready&sid=xnewa"
import urllib2
request = urllib2.Request(url, headers={"Accept" : "application/xml"})
u = urllib2.urlopen(request)
tree = ET.parse(u)
root = tree.getroot()
for recording in root.find('recordings'):
print recording.find('id').text
print recording.find('epg_event_oid').text
print recording.find('name').text.encode('utf-8')
print recording.find('status').text.encode('utf-8')
print datetime.datetime.fromtimestamp(float(recording.find('start_time_ticks').text))Martin |
|
|
