"Recordings That Failed to Schedule" error ?

[jksmurf]

Sub,
As per the image in this post, I get a "Recordings That Failed to Schedule" error when trying to record from Episode Search in EWA. UncleJohnsBand (of EWA fame) says it is a GBPVR thing, not an EWA thing.

Has the recordings conflict behaviour changed in the last version? I just noticed that there was a recording already scheduled at the same time, but the old behaviour (IIRC) was to allow recording of both shows, with a yellow "conflict" flag appearing on the manage recordings page.

However this new behaviour just says it (scheduling) failed, and not that there was a conflict. Both recordings (old behaviour) would be good IMO, despite the conflict status, as this can be overidden by those those using priority recordings e.g.

I used to remember it (would this have anything to do with the (sticky thread) patch for not being able delete recordings, I sort of remember this started after that), but it may be completely un-related.

UncleJohnsBand's reply

I don't know.....I didn't change anything.....The EWA simply calls the record show API that is provided with GBPVR....all the conflict determiniation is done in the GBPVR API code......

The message you see displayed about it failing was added back in build 36.....prior to that no message was displayed at all in EWA should a recording not schedule.

The check (as I think I mentioned before) is a simple check:
All shows to record are sent through the scheduling API.
Then a list of all record shows is pulled via the API.
The list of shows that were selected to record is checked against the list of recorded shows returned from the API.
If a show is not found then it is listed at the top of the grid like you are seeing.

To my knowlege nothing has changed in the schedulerecording API that would prevent a show from scheduling in a conflict state....but only sub could answer that for sure.....

k.

[sub]

Has the recordings conflict behaviour changed in the last version? I just noticed that there was a recording already scheduled at the same time, but the old behaviour (IIRC) was to allow recording of both shows, with a yellow "conflict" flag appearing on the manage recordings page.

No the behaviour has not changed.

I cant talk for the web admin behaviour, because I dont use it myself, and not at all familiar with it.

If you were to do this in GB-PVR's TV Guide screen, you get the same behaviour as any release in last year or so: If you try to schedule a recording, and it knows at that time that its not possible, GB-PVR will not schedule the recording. Instead, it will popup the conflict window to tell you what the conflict is, and giving you chance to cancel the conflicting show(s). If you chose to cancel the conflicting shows, then your newly requested recording will be scheduled at that time.

The only recordings that will be allowed to be scheduled with the conflict status are those that are automatically added as part of season or reoccuring recordings (added after EPG update).

[jksmurf]

The only recordings that will be allowed to be scheduled with the conflict status are those that are automatically added as part of season or reoccuring recordings (added after EPG update).

Ahhh.... maybe that's what I saw in yellow then. :o Thanks sub.

k.