Media Browser Integration

[mvallevand]

Yep I gave you a mix of XML and JSON Bottom line is sub uses mainly XML with a little JSON and NEWA uses JSON

Martin

[UncleJohnsBand]

Is there also an api call to get the version of the nextpvr client?

When i went to record 2 programs on the same time, i get an internal server error back.
I have a tv-card with 2 tuners so it's possible.

When i start them with nextpvr itself. There is no problem....

No API at present for NPVR version.... I can create one though.... I will post when added.

As for the recording..... 1st upgrade to the latest NEWA dev build following instructions on wiki

Also.... you need to post the web.log when you have issues so I can see if anything unusual is happening in there... as a tip... you will need to stop the npvr recording service to zip the log since it holds it open.

[mvallevand]

UJB the setting.get method from sub basically returns the XPath into config.xml it is not really a version check but I'd prefer sub's way to dedicated calls for each setting value that sub might add to config.xml

However a JSON call to get NEWA version instead of this XML call http://forums.nextpvr.com/showthread.php...WA-version would be helpful.

Martin

[UncleJohnsBand]

UJB the setting.get method from sub basically returns the XPath into config.xml it is not really a version check but I'd prefer sub's way to dedicated calls for each setting value that sub might add to config.xml

However a JSON call to get NEWA version instead of this XML call http://forums.nextpvr.com/showthread.php...WA-version would be helpful.

Martin

Is the request for the NPVR version, the NEWA version or both?

I was thinking svekke wanted the current NPVR version.... I can do both... just need to make sure I know what people want.

Also... the changelog is also available on the wiki.

[mvallevand]

Ideally I think many developers want a full API that only requires JSON although reven seems satisfied with XML. Right now to get everything both are required. As an example I showed that sub has a api that exposes config.xml valyes NEWA does not have this. It doesn't have a login either Right now NEWA exposes more via JSON so it makes a richer client.

The wiki change log is pointless I read changelog attributes as xml to determine the actual running NEWA's version needed until SOAP is dead.

Martin

[Svekke]

If you can give both, that would be great.

The problem now is that we need to do also the login (salt,sid).
When we only use the newa json calls, we don't need to do some extra stuff.

It would make our code much cleaner.

[Svekke]

Hmm for the LiveStream I still need the login(sid/salt). Not?

[mvallevand]

Hmm for the LiveStream I still need the login(sid/salt). Not?

No that is YANA (Yet Another NextPVR API) Now that JSON has most of XML there is no login required, it is not integrated with the SID login, although I am hoping sub and UJB work something out so we can have safer internet access in the next version. From an MB3 perspective you it probably isn't an issue.

Personally I still use the XML for the Now/Next guide info because the server side is much faster.

Martin

[Svekke]

No that is YANA (Yet Another NextPVR API) Now that JSON has most of XML there is no login required, it is not integrated with the SID login, although I am hoping sub and UJB work something out so we can have safer internet access in the next version. From an MB3 perspective you it probably isn't an issue.

Personally I still use the XML for the Now/Next guide info because the server side is much faster.

Martin

Do you maybe have an example how to call it?
Pointing me in the right direction.

[mvallevand]

There are two

/live?channel=##&client=uniqueid
/live?channeloid=##&client=uniqueid

You are responsible for the uniqueid if &client is not provided only one stream is available via the API.

Martin