GBPVR Records Only First Minute Or Less

[nobody481]

Hello Everyone!

I just got my cable box and UIRT set up last night. I set up a few recordings overnight. When I got up this morning, the recordings are all one minute long or less. The programs I was recording were all at least a half an hour. I restarted a few minutes ago and tried to record something else, and it did the same thing.

I'm running GBPVR 1.0.16. I don't have any additional plugins installed. My logs are attached. Can anyone direct me to what the problem may be?

Thanks a lot!
Aaron

[sub]

Unfortunately the logs are cut short and dont show the important stuff. Can you enable log flushing in the config app, and repost the logs if the error reoccurs.

[Graham]

I had this problem and it went away when I installed the patches from the Survival Guide (even though they don't mention these exact symtoms).

Graham

[nobody481]

Sorry it's taken me so long to get back to you. There was a big football game on yesterday and our team won. We partied the rest of the day/night. Go Bucks!

I enabled the "Flush Log Messages To Disk" option and tried to record something else and the same thing happened. I've attached the logs.

Graham, are you talking about the patches in the 1.0.16 or 1.1.5 survival guide?

Thanks for your help!
Aaron

[sub]

In the logs it looks like you started recording Match Game aty 11:21, then cancelled the recording at 11:23, so the app recording service stopped the recording.

[nobody481]

That is true, but I canceled the recording after I saw the file size of the recording had stopped increasing. Right now I have around 15 .mpg files in my recording directory, all 50 MB or less because the recording stopped on all of them. So I figured since the file size stopped increasing when I refreshed the listing, the recording had stopped again.

I've started recording something else and I will let it go and not cancel anything. I'll repost those logs when the program is over.

Thanks!
Aaron

[sub]

If an analog card stops delivering data mid recording, its never a good thing. GB-PVR tells the recording to start, and later to stop. Everything in between the two points is up to the device.

I seem to remember some users have had this in the past when the machine was sharing IRQs between devices, which could cause the device to stop producing data, so you could look into that. Otherwise I dont know.

[nobody481]

I've attached more logs of failed recordings if it helps at all.

I'm not sure what's going on. I've recently moved. My PC hardware setup is the same as it was before, but I have a different cable company now. At my old place you didn't have to have a cable box to get all the cable channels, but here you do. I had to get the UIRT for it. So nothing with my computer has changed, but the cable box situation has.

I'm going to try version 1.1.5 to see if that makes any difference. If that doesn't help I'll start trying previous versions. I'll post the results.

Thanks for your help!
Aaron

[sub]

There is no sign of any errors in those either, but the only time you'd see an error in the logs is if something failed during the stage when the recording is set up, or during the stopping of the recording. GB-PVR doesnt play any active role in events between these two points, so wouldnt be aware of any problem occurring there.

I cant see the USB-UIRT causing this. If you remove it, does the problem go away?

[nobody481]

Well I've gotten a little closer to the problem. I installed the latest version, 1.1.5. The problem occurs when I have the recordings directory set to my RAID. I have a 600 GB RAID set up as the G: drive, I think it's across 4 200 GB hard drives. When I try to record to that drive, that's when the recording fails. But I can record to c:\temp and it records fine. I got around 500 MB a bit ago on c:, and I'm recording something right now where it's at around 270 MB on c:.

Any idea what might be causing this or how to fix it? Before I moved the only drive I recorded to was this RAID G: drive, so I'm not sure what could be the problem now.

Logs attached again.

Thanks for your help!
Aaron