CDK scheduler and CaptureSource attribute

[LilY0da]

Ok, been playing around with this, and whereas it works when I have only 1 or 2 days stored in the EPG, when I store my full 7 days, then CDK scheduler starts moving shows from one capture source to the other.

What I was trying to do was to force all recordings to go to one single capture source, so that I could keep my 2 PVR-500 tuners for FM radio and LiveTV.

http://kragone.free.fr/PriorityRecordings.xml
And http://kragone.free.fr/PriorityRecording.log

I tried with every possible value of CaptureSource (my tuner OIDs are 2, 3 and 4). Can someone let me know if I'm doing something wrong, or if this is a bug/feature?

[jrockintuitive]

In CDK scheduler, capture source is really preferred capture source.
If memory serves me correctly--- If the preferred capture source is used, instead of creating a conflict, CDK will use the other caputre source.

I do not remeber if I extended that logic for back-to-back programs as well.

Maybe capture source could be force capture source.

[KingArgyle]

My original intention for capture source was a Force capture source type functionality. I only have one capture source so I can't do any testing on this.

An option would be to have an optional attribute added to CaptureSource to indicate how the capture source element should be have when used.

[LilY0da]

I'd be willing to ship my PVR-250 to whichever one of you want to test this and maybe develop an update :-)

[KingArgyle]

Actually, we wouldn't need another tuner to do it, just have to make the time to code the changes, and then have you test them out.

Unfortunately, my work schedule doesn't leave me much time right now to take a look at it. If I can get some spare time, I'll take a look and see what I can come up with.

[jorm]

Do you want me to look at making the capture source forced to that number unless there is another attribute set?

[jrockintuitive]

Jorm,

Capturesource is the attribute that should be set.

FYI: I should have given this to you earlier... sorry.
My to-do list for Scheduler-

• Generate a priorityrecording.xml file from the GBPVR recordings table. There would be an option to delete all entries from the GBPVR recordings table. I would imagine that first someone would generate there priority recordings file, then compare, then delete the entries from the recording table.
  Better reporting - I have not defined what "better reporting" is
  

Also, I've scrapped the concept of being able to schedule one recording at a time. I've also scrapped the idea of being able to schedule as many shows as possible - meaning reschedule a show with a higher priority to a different timeslot to allow a lesser priority item have that timeslot.
I felt both of the above concepts were not worth compelling enough to re-work the scheduler.

On a side note, feel free to rename guide2j to xguide.

[jorm]

thanks for the info. I thought about making guide2j part of the xrecord distributable. Since they both have the cdk scheduler and the fastfind plugin.

What do you think xguide (guide2j) and xsearch (fastfind)?

[KingArgyle]

Yeah, I'd add an optional attribute to the Schemas for the CaptureSource element.

So that it looks something like (force the recording to record on capture source 1):
<CaptureSource force="yes">1<CaptureSource>

If it isn't forced you can have it as either (prefered capture source is 1 but can try alternate capture sources:
<CaptureSource>1<CaptureSource>
<CaptureSource force="no">1<CaptureSource>

If no prefered designation is indicated then any available capture source may be used to record the show.

[jrockintuitive]

I like it... xguide and xsearch