Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Enchancing data in the NextPVR XML API's

  1. #1
    Join Date
    May 2006
    Location
    Canada
    Posts
    27,754

    Enchancing data in the NextPVR XML API's

    Currently the data obtained from the http xml interface is not rich compared to the NEWA JSON interface which basically provides as much of the EPG record as it can. I think as a minimum the following changes should be considered

    1) method=channel.listings

    - add season and episode numbers
    - add movie year
    - separate subtitle field I will use this to clean description
    - new indicator <= not even used by Kodi but need to display

    2) method=recording.list

    - include genre
    - include movie year
    - currently I regex the subtitle for S##E## probably need to keep that for new versions.

    Martin
    Last edited by mvallevand; 2019-03-19 at 07:54 PM.

  2. #2
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,201
    Ok - I'll add these for v5.

  3. #3
    Join Date
    May 2006
    Location
    Canada
    Posts
    27,754
    Ok thanks it doesn't have to be version specific as the xml is typically parsed for parameters. By v5 I am hoping to use a JSON interface anyway perhaps that can be the richer version.

    Edit: this will give you an idea of where Kodi will use the data

    https://imgur.com/a/y2CmWF7

    Martin
    Last edited by mvallevand; 2019-03-13 at 07:16 PM.

  4. #4
    Join Date
    May 2006
    Location
    Canada
    Posts
    27,754
    In the meantime what about a quick fix to prepend S##E## to the Subtitleescription logic you have today. Using the Kodi guide for I would like to see this information.

    Martin

  5. #5
    Join Date
    May 2006
    Location
    Canada
    Posts
    27,754
    After trying Kodi for a few days without the S/E data and the new file flag, the Kodi guide kind of sucks so I am back to x-newa. It's a shame really but I guess Kodi users don't know the NextPVR experience.

    Martin

  6. #6
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,201
    I have implemented most of your suggestions for v5. (separate subtitle, season and episode fields etc)

  7. #7
    Join Date
    May 2006
    Location
    Canada
    Posts
    27,754
    Great looking forward to it. I added the first run flag request today since that is the one I miss the most (especially Premier)

    Martin

  8. #8
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,201
    You should already get a firstrun node.

  9. #9
    Join Date
    May 2006
    Location
    Canada
    Posts
    27,754
    Ok I guess that means I need significance too. I guess I was spoiled by UJB's interface that always provided a deserialized EPG record so there was never missing data or naming discrepancy no matter what call provided it.

    Martin

  10. #10
    Join Date
    May 2006
    Location
    Canada
    Posts
    27,754
    Another item for consideration is art download changes with schedules direct especially wrt TV Guide episode art. I hate littering my drive with art from the guide for shows that I likely will never watch let alone record. Rather then the current download and cache approach why not just set the Amazon or SD url and let the client fetch the art themselves if they really need it? Given that the episode oid changes every day I am not sure there is any value to the cache given the look up time.

    Martin
    Last edited by mvallevand; 2019-03-27 at 08:34 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •