2012-10-09, 10:11 PM
It might be cosmetic http://forums.nextpvr.com/showthread.php...-incorrect but it seems related. Anyway I will update the epg and see what happens.
Martin
Martin
2012-10-09, 10:11 PM
It might be cosmetic http://forums.nextpvr.com/showthread.php...-incorrect but it seems related. Anyway I will update the epg and see what happens.
Martin
2012-10-09, 10:40 PM
The sql seems right and the rules seem to be what I want (I am not using the new user field yet), the channel is ok the time range for the two hours I want to test seems wrong.
Martin
2012-10-09, 11:10 PM
I guessing there is nothing wrong with those times since the APIs for creating yjpse scheduling recordings haven't changed for a long time, and they're being successfully used by both NextPVR and NEWA. Are you sure you supplied UTC times to the call?
2012-10-09, 11:21 PM
Don't you use the time in the Rules?
Code: <Rules> Martin
2012-10-09, 11:30 PM
From memory, these StartTime/EndTime attributes are not used when you specify advanced rules (these are not TimeslotStart/TimeslotEnd attributes). It will use the day mask though, which you've set to Sunday. So it'll schedule any shows return from the SQL that are on a Sunday.
2012-10-09, 11:39 PM
(This post was last modified: 2012-10-10, 01:28 AM by mvallevand.)
Ok good to know, but odd that it accepts all the other filters except the start/end time
Martin
2012-10-10, 01:28 AM
So the start/end time are not used at all with advancedRules but they are used when there are none?
Martin
2012-10-10, 01:35 AM
From memory, yes that's the case. The start/end times of the created scheduled recordings will come from te start/end times of the EPG events.
2012-10-10, 10:12 PM
You must be doing a bit of date parsing if you limit day of the week. Could you extend that logic to use he configured time for advancedRules? It really is a nuisance adding the start and end times, because I only can use the hour to because I can't hard-code a date, I have to use localtime to adjust for DST and then when the show is in prime time it typically spans days here I end up with 4 conditions on time.
Martin
2012-10-10, 10:19 PM
It's not parsing these StartTime/EndTime attributes for this type of recording. The daymask is separate, and passed in as a separate parameter to the schedule recording API call. It results in the <Days>SUNDAY</Days> in the xml.
|
|