CDK Req: Priority alerts

[capone]

I just realized that the priorities work well, but they don't tell you that they are being done. This is only an issue in I just figured out some things weren't recording because CDK does a good job handling it.

I would love to see alerts or messages of some kind that it's doing it's magic, though. At least that way I would know I'm not getting cetains shows, and can track them down or reconsider the priority if the lesser show will not repeat, and the higher show will.

Maybe it can just report them in conflicts, or just highlight schedules that overlap.

[KingArgyle]

Maybe XRecord could display the recordings.log output file. This contains the complete diagnostics of what CDK Scheduler has recorded, and if it didn't record something that information is included as well.

Eventually, I'd like to clean up that report so that it was a bit more user friendly, but just haven't had enough free time to get to it.

If you want it to keep conflicts, you can try changing the Conflicts element from Delete to Keep in the PriorityRecordings.xml file. This should put all conflicts into the Conflict screen, and you can manually resolve them if you want.

[capone]

That's exactly what I was looking for...I didn't realize it was an on/off thing. Perfect.

The more I use CDK, and always using XRecord, I would love to see more coordination w/ the two. It adds a lot more fucntionality now that I know more about how to use it.

[capone]

Is there a guide to the config settings (the four of them)? What they do and vaules?

I found DuplicatesAllowed by searching, and added padding (I assume that is minutes). These I came up dry:

<MissingRecordingPriority>0</MissingRecordingPriority>
<DefaultForce>no</DefaultForce>

[jorm]

I can do an enhancement that in the scheduler screen you hit a color key and it will post a popup with the log

does it work?

[KingArgyle]

What is really needed is a good tutorial on the Wiki on how to use XRecord and CDK Scheduler together. It's really strewen all over the various message boards. I can tell you how CDK internals work, but I'm not as famaliar with the User Interface that XRecord provides, I only wrote the API that Jorm uses to read and write the PriorityRecordings.xml file, and run the scheduler. Jorm provided the code for interfacing into RecTracker, and JRock did a bunch of clean up and optimization.

Ideally, I'd love to see Video Archive provide an interface to CDK Scheduler as well.

I can't live without the ability to schedule recordings based on Priority, especially since I only have one tuner. A combination of CDK Scheduler, Rename Recording, XRecord, and MaxRecordings is a great combination. Provides me with everything that I had with BTV and more.

As for documenation on the individual elements, you can find this on the wiki:

http://gbpvr.com/pmwiki/pmwiki.php/Utility/CDKScheduler

Download and unzip the CDKSchemaDoc.zip file, each element is defined there with how to use it and what values are accepted.

[KingArgyle]

Is there a guide to the config settings (the four of them)? What they do and vaules?

I found DuplicatesAllowed by searching, and added padding (I assume that is minutes). These I came up dry:

<MissingRecordingPriority>0</MissingRecordingPriority>
<DefaultForce>no</DefaultForce>

MissingRecordingPriority controls at what Priority CDK Scheduler will handle Recordings that aren't in the PriorityRecordings.xml file. These could be recordings that were scheduled by the builtin GBPVR scheduler or set up a one time recording through either GBPVR or the Web Admin. 0 means always keep these, or 999 means treat the scheduled items in PriorityRecordings as taking precendence.

DefaultForce determines if the Capture source should be forced. Only necessary if you have more than one Capture source.

[capone]

I don't know why I didn't check wiki.....duh.

I update CDK, now they show up as conflicts, which is good. It did put them in Conflicts, but maybe it would after the EPG. I couldn't find a way to force it otherwise.

I agree about the need for priority. What would be perfect, and I hope this is the case, is if priority and conflict work together. By this I mean, if something has a lower (lesser) priority, and is in conflict, will it be the one not to record, or is it first come (time, pre padding, etc)?

I'd love it if still uses priority in determining the alpha record. I just want to know there is a conflict, but in the case I'm trapped under a piano or something, that it would fall back to my original wishes.

[KingArgyle]

The one that is put into conflict is the lesser of the conflicting recordings. If Recording A and Recording B are in Conflict and Recording A is at a higher Priority, Recording B is put into a Conflict status, and Recording A is scheduled.

So, yeah, it should work the way you want.

[KingArgyle]

Here are the most current Docs. I'll try and get the docs on the wiki updated as well.