Xrecord v.38

[LilY0da]

Hey Jorm, I noticed that Xguide goes a bit crazy if you keep going down with the PageDown button. When it reaches the end, instead of cycling back to the first channel, it starts cycling between the last 2 pages displayed.

Also, pressing the "Play" button or Ctrl+P doesn't play the channel, and there's no "Watch" option when you select a currently running show. Kinda annoying to have to memorize the channel number, go to Live TV and then switch channels.

[jorm]

You are running the latest xguide? There should be a watch on a current show.

[Richard]

Hi Jorm,

I am trying to record two shows:
First show runs 19:00-19:32
Second show runs 19:30 - 20:00

I have set them up in Scheduler. I then went to PriorityRecordings.xml and changed the start time of show 2 to 19:32.

Unfortunately, there appears to be a problem with the program recognizing both shows. even though I changed the start time to 19:32 it still shows as 19:30 in the RecStatus printout and show 1 will not record. I also tried changing the start time to 19:33 to no avail.

Any suggestions how I can get this to work?

Wish list request: to be able to record a period of time not based on the hour / 1/2 hour time. i.e. If I want to record 15 minutes of a show I could setup a record time of say 11:10-11:25.

[LilY0da]

I thought I was... Will try updating again and adv.

[KingArgyle]

Hi Jorm,

I am trying to record two shows:
First show runs 19:00-19:32
Second show runs 19:30 - 20:00

I have set them up in Scheduler. I then went to PriorityRecordings.xml and changed the start time of show 2 to 19:32.

Unfortunately, there appears to be a problem with the program recognizing both shows. even though I changed the start time to 19:32 it still shows as 19:30 in the RecStatus printout and show 1 will not record. I also tried changing the start time to 19:33 to no avail.

Any suggestions how I can get this to work?

Richard, how are you changing the start time for your second show. For that particular recording you should be using something like:

Code:

<Padding>
        <AdjustStartTime>3</AdjustStartTime>
   </Padding>

What that should do is when comparing the two ovelapping shows, it should add 3 minutes to the second show so that it's new start time is actually 19:33 instead of 19:30.

[Richard]

Thank you for the help. I was acutally changing the time.

However, when I add the line and run PostUPdatedEPG.bat I receive a runtime debugging error:

"Application has generated an exception that could not be handled"

Process id=0xd3c (3388), Thread id=0x9b4 (2484)

[Richard]

If I go to GBPVR XRecord I get the following error when I open it:

Error: The element 'Padding' has invalid child element 'AdjustStartTime'.
Expected 'PrePadding'. An error occurred at file:///C:/Program Files/devnz/gbpvr/PriorityRecordings.xml, (95,8).

[KingArgyle]

You also need to include the PrePadding and PostPadding elements as well. The order should look something like:

Code:

<Padding>
    <PrePadding>0</PrePadding>
    <PostPadding>0</PostPadding>
    <AdjustStartTime>3</AdjustStartTime>
</Padding>

The PrePading an PostPadding elements are required elements. If you don't want any pre or post padding to your recordings, then just set them to 0.

[Richard]

Thank you, the addition of the pre and post padding did away with the errors. However, the first program was still not recording.

I found a small problem in the logic... in order for the first show to record, it must be set to a higher priority than the second show. The program appears to say, I have show 2 that starts at 19:30 that has a higher priority than show 1 show ends at 19:32, therefore I will not record program 1 eventhough show 2 has the 3 minute adjustment to the AdjustStartTime.

Can you or Jorm change the logic for the program to look at the AdjustStartTime when deciding to record a show where there appears to be a conflict?

[KingArgyle]

I'll take a look at the logic. It may not get to it before this week though. I'm not surprised that it's a priority scheduling conflict. I'll post a message in the Plugin Support when we've gotten it fixed.