Massive (and unusuable) recording files

[bgowland]

I saw a post some time back on this and can't find it now.

To cut a long story short - my new PVR 500 doesn't like AGP graphics cards (PC refuses to boot). I managed to find an old (5+ years) PCI card and got the machine up and running and the 500 installed. A test record of a 30 minute programme, however, produced a 21.9 GB MPEG which was of course unwatchable.

I can't remember what the reason for that was in the other post I saw where someone was seeing the same thing. Can someone remind me please?

Cheers,
Brian

[sub]

Quote[/b] ]To cut a long story short - my new PVR 500 doesn't like AGP graphics cards (PC refuses to boot). I managed to find an old (5+ years) PCI card and got the machine up and running and the 500 installed. A test record of a 30 minute programme, however, produced a 21.9 GB MPEG which was of course unwatchable.

If you've configure a PVR150/PVR500 as a PVR250/250MCE/350, then it'll result in these massive files. This is because its capturing raw video data to a file that is incorrectly called a .mpg file.

Check what device types you selected.

[bgowland]

Quote[/b] (sub @ Jan. 22 2005,11:19)]If you've configure a PVR150/PVR500 as a PVR250/250MCE/350, then it'll result in these massive files.

Thanks - that sounds familiar from what I read in the other post.

I put the 500 in with my 350 still in there then configured two new capture sources in Config.exe both as PVR 500. I don't have enough aerial connections at the moment so decided to unplug the aerial from the 350 to use for the 500 then deleted the EPG for the 350 and set it's capture to be S-Video so GB-PVR wouldn't use it for TV recordings.

It all seemed logical at 5am this morning but obviously not. I'll try again.

Cheers,
Brian

[sub]

I had a PVR350 in my machine configured as capture device #1, then added a PVR500 hundred expecting it to be device #2 and device #3. That wasnt the case. It inserted itself as device #1 and device #2, moving the PVR350 out to device #3. This of course resulted in the existing capture source #1 being configured as a PVR350, meaning I also got these huge files.

[bgowland]

Quote[/b] (sub @ Jan. 22 2005,11:46)]This of course resulted in the existing capture source #1 being configured as a PVR350, meaning I also got these huge files.

I think that is probably what happened in my case too. I'm going to give it another try now.

Thanks,
Brian