NextPVR web API for scheduling - DayMask

[sub]

Perhaps you could not prepend "KEYWORD: " if the parameter starts with "title like '"

Ok - I've made a change like this for the next v5 build.

[mvallevand]

Ok - I've made a change like this for the next v5 build.

Great thanks I will include this in Kodi v5 specific changes.

Martin

[mvallevand]

If the keyword parameter includes a single quote should I send the sqlite escape which is two single quotes or is that something you can fix on the server?

Martin

[mvallevand]

1: // Record Season (NEW episodes on this channel)
2: // Record Season (All episodes on this channel)

Sub for those two recording type are those timeslot recordings or are they any day?

Martin

[sub]

Those are not timeslot recordings. The episodes can be found any time, any day.

[mvallevand]

Thanks I was just confirming since the EPG times are there. Working on the Emby update can I change one of these types to a timeslot recording?

Martin

[sub]

You should be able to. Just pass whatever parameters you want to use for the recurring, and the existing recurring id.

[mvallevand]

I was hoping I could just pass a changed type &recurring_id=xx&timeslot=true&recurring_type=3 and NextPVR would treat the stored event field from the recurring record like a loaded event.

Right now I don't see Emby giving me back an end time and it doesn't have a duration even though it can change the start time but maybe I will pick up more info as I work it out.

I won't allow changing "All Channels All Episodes" to a structured recording, too much hassle.

Martin

[sub]

The API doesn't currently work that way. It expects you to pass all the parameters you want to set on that recurring.

I'll modify this one for v5 to allow it to use the existing settings for anything not supplied though.

[mvallevand]

Sub, does a timeslot recording care of the name changes?

Martin