GBPVR Records Only First Minute Or Less

[sub]

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?

No, but based on your description, its sounds like something RAID or Windows related.

GB-PVR doesnt know that your G:\ drive is a RAID array, and shouldnt need to. It just opens files and writes to them. Window's and your hardware is supposed to take care of where that data goes.

It does sound like progress though, and good to have narrowed it down to this.

[stustunz]

apply the patches on the survival guide that fixed my tuners doing small recordings

<PreferAlternatingCaptureSources>false</PreferAlternatingCaptureSources>
<TryToHonourPaddingIfPossible>true</TryToHonourPaddingIfPossible>

use these setting in the past i used oposite for the first one

[sub]

That wont be the same problem. I'm sure you're referring to the padding one, which is not the problem here. With that problem, he would have had to have a show scheduled to record immediately after this recording, and he would have had to have a huge amount of pre-padding defined on that second recording for only 1 minute to be recorded of the first show.

It also doesnt show GB-PVR stopping the recording in the logs. GB-PVR is stopping the recording at the requested time, but the file stopped growing long before that. With the padding problem, GB-PVR was clearly stopping the recording in the logs.

[nobody481]

Thanks sub, while I was posting that I knew in the back of my mind that it wasn't likely an issue with GBPVR. I'll keep trying things and if I find a solution I'll post it. In the mean time I can record to c:, and set up a scheduled task to move c:\temp\*.mpg to g:. They'd never let me get away with such a solution at work, but here at home I'm my own boss! :-)

stustunz, I'll definitely try it. Are you talking about the 1.0.16 or 1.1.5 survival guide? And which patch specifically?

Thanks again!
Aaron

[stustunz]

what tuner is it ?

if using 1.1.5 you always only use the patches for that release

also check your windows error logs in adminstrative tools see if some thing is causing an error

as to the tuner fix it probably wont fix it but you never know

[nobody481]

It's a Hauppauge PVR 250.

[mvallevand]

In the mean time I can record to c:, and set up a scheduled task to move c:\temp\*.mpg to g:. They'd never let me get away with such a solution at work, but here at home I'm my own boss!

If you do this you won't you lose the link to the recordings database?

Martin

[nobody481]

I don't know. I don't use the recordings DB anyway. After the recording ends I manually run ShowAnalyzer, take out the commercials with MPEG-VCR, then run mencoder from a perl script to compress to .avi. I need to work on getting that completely automated! :-) But I can't always trust ShowAnalyzer to mark the commercials correctly.

[nobody481]

I was wrong about the C: drive vs G: drive. Recordings started to do the same thing on C:. I'm going to test it with and without the UIRT now, hoping it makes some kind of difference.

[nobody481]

Ok, the problem seems to be with the USB-UIRT. Last night I recorded four 30 minute shows with "No Channel Changer Required". I recorded them to c:\temp\. Those 4 recordings are all around 800 MB, 30 minutes long, but on the wrong channel, of course.

Then I set up the USB-UIRT and set up 4 more recordings to c:\temp\. The USB-UIRT works. I see it correctly changing the channel on the cable box. But all four of those recordings stopped early. One recording got to 300 MB, the second got to 46 MB, and the other 2 got to 350 KB. Yes, KB.

So the USB-UIRT seems to be causing the problem some how. Logs are attached. Any idea how to fix it?

Thanks a lot!
Aaron