Media Browser Integration

[mvallevand]

thanks, this worked, although it's stime and etime, and not in swagger.

They are documented in /api for me.

Martin

[lukemb3]

Ok. I didn't realize there were two different swagger url's. Which is preferred?

[lukemb3]

In SortedFilteredList, what are the different values for Status ?

[lukemb3]

Also, there are some things I'm a little unclear on. I realize GetSortedFilteredList is the most powerful way to get recordings given all of the params, but sometimes it's nice to spoon-feed developers with overloads for the most common use cases.

For example, I want to get a list of recordings - whether completed or in progress. I did this

var filterOptions = new
{
resultLimit = -1,
All = false,
None = false,
Pending = false,
InProgress = true,
Completed = true,
Failed = true,
Conflict = false,
Recurring = false,
Deleted = false
};

I got back the correct results, but included in them was a single recurring parent. I am not sure why and it's hard to tell if this is a bug or the wrong params, so I filtered it client-side to remove results where schd == null

[lukemb3]

Now I would like to get a list of upcoming recordings, so I did this:
{
"resultLimit": -1,
"All": false,
"None": false,
"Pending": true,
"InProgress": false,
"Completed": false,
"Failed": false,
"Conflict": true,
"Recurring": false,
"Deleted": false
}

All recordings in the future, whether pending or conflicted. This appears to be working, but as with the last example it looks like i have to filter out recurring parents client-side.

[mvallevand]

Now I would like to get a list of upcoming recordings, so I did this:
{
"resultLimit": -1,
"All": false,
"None": false,
"Pending": true,
"InProgress": false,
"Completed": false,
"Failed": false,
"Conflict": true,
"Recurring": false,
"Deleted": false
}

All recordings in the future, whether pending or conflicted. This appears to be working, but as with the last example it looks like i have to filter out recurring parents client-side.

Conflicts aren't supported in NextPVR so it probably isn't worth coding for them until it is defined.

The EPGEvents class is tricky to work with you can get many combinations the 4 epgEventJSONObject classes that it returned depending on what is in the recording list. I always ignore rtn too.

Martin

[mvallevand]

In SortedFilteredList, what are the different values for Status ?

"Pending";
"In-Progress";
"Completed";
"Failed";
"Conflict";
"PlaceHolder";
"Deleted";

These map to the NUtilty.RecordingStatus enum from the NextPVR API.

Martin

[mvallevand]

I got back the correct results, but included in them was a single recurring parent. I am not sure why and it's hard to tell if this is a bug or the wrong params, so I filtered it client-side to remove results where schd == null

Could you upload your db3 file somewhere and I can try to see what is up. If you empty the db3 file it is small enough to compress and post without the epg data. I don't recall this and my database starts with npvr.db3 from the first betas without being rebuilt.

Martin

[UncleJohnsBand]

what's an example of sortFilter for SortedFilteredList?

Here's what I use for good recordings. I get results from c# and python but not swagger

Code:

{
  "resultLimit": -1,
  "datetimeSortSeq": 0,
  "channelSortSeq": 2,
  "titleSortSeq": 1,
  "statusSortSeq": 3,
  "datetimeDecending": false,
  "channelDecending": false,
  "titleDecending": false,
  "statusDecending": false,
  "All": true,
  "None": false,
  "Pending": false,
  "InProgress": true,
  "Completed": true,
  "Failed": false,
  "Conflict": false,
  "Recurring": false,
  "Deleted": false,
  "FilterByName": false,
  "NameFilter": null,
  "NameFilterCaseSensative": false
}

Martin

I have included endpoints to get a default sort filter object.... check the swagger doc at http://localhost/API under manage service....

/public/ManageService/Get/RecordingsSortFilterObj

[UncleJohnsBand]

what's an example of sortFilter for SortedFilteredList?

thanks, this worked, although it's stime and etime, and not in swagger.

Look at http://locahost:8866/API (you may need to clear your browser cache if you are not seeing the methods).

I have now removed the self-generating swagger doc as it didn't provide enough info.... what is at the API location is hand rolled swagger docs using the swagger-core app to present the info.

Let me know if that helps.