pinnacle pctv 400e usb

[frazer]

Hello,

I'm trying to use this DVB-S device with GBPVR, but so far have not been able to capture any channels. I have searched on one transponder I know is reasonably strong (and which works with other software), but though the search briefly shows a high signal strength and quality, it fails to find any channels.

I had to add this device to the BDA list myself, having done the filter check on my computer, so I have attached the filter check results and my adjusted BDA file just in case I have configured it wrongly.

Thanks for any advice,

Frazer

[sub]

Can you do the scan again, then zip and attach the config.exe.log and config.exe-native.log?

[frazer]

Thanks for the quick reply; unfortunately I've not got time now (and the HTPC is switched off) but I'll try again later and post the logs.

Thanks again!

Frazer

[frazer]

I did a new scan of a whole satellite (hotbird), and there was a mix of good strength and quality, and some no strength and full quality, but still no channels found. I tried the same thing with other software and found over 1000 channels in the first half of the search, but then nothing in the second, which suggests there is some problem with the higher frequencies (but this may be due to my lnb set up).

One point I noticed was that the other software recognized the tuner as "Pinnacle PCTV 4XXe Tuner (2)", so I tried adding the (2) to my BDA file but then GBPVR couldn't find the tuner at all. Incidentally, GBPVR doesn't recognize the Pinnacle if I tick only show detected devices in the configuration, but does "detect" a Skystar 1 card, which I don't have.

Anyway, here are the logs from the hotbird search.

Thanks again,

Frazer

[sub]

2007-07-30 17:42:01.375 VERBOSE Graph contains the following filters:
2007-07-30 17:42:01.375 VERBOSE - Video Renderer
2007-07-30 17:42:01.375 VERBOSE - BDA MPEG2 Transport Information Filter
2007-07-30 17:42:01.375 VERBOSE - MPEG-2 Sections and Tables
2007-07-30 17:42:01.375 VERBOSE - GB-PVR DVB Subtitles
2007-07-30 17:42:01.375 VERBOSE - GB-PVR PSI Parser
2007-07-30 17:42:01.375 VERBOSE - VMR9
2007-07-30 17:42:01.375 VERBOSE - Sigma Designs MPEG-2 hardware decoder
2007-07-30 17:42:01.375 VERBOSE - MPEG-2 Demultiplexer
2007-07-30 17:42:01.375 VERBOSE - Pinnacle PCTV 4XXe Capture
2007-07-30 17:42:01.375 VERBOSE - Pinnacle PCTV 4XXe Tuner
2007-07-30 17:42:01.375 VERBOSE - Microsoft DVBS Network Provider

I'm wondering if the filter highlighted above is somehow getting in the way. I think is with an XCard? Is there any chance you could use the filter manager software that is usually installed with the xcard software to temporarily disable this filter to see if it helps?

[sub]

Are you trying to use a diseqc switch?

[frazer]

well, there was a diseqc switch involved in the log I sent previously, but it was set to "none" in the configuration, and the satellite searched was connected to the first input; which usually works as the default connection (and I have tried successfully this with my set top box).

however, my initial failed attempts were without the switch involved at all, and I have tried this again (same single strong transponder) with the Xcard disabled as you suggested, and the result is the same. I have attached the new logs.

Thanks!

[sub]

I'm not really sure - there is no sign of any errors in the logs.

You could try creating the following registry key, then try again.

HKEY_LOCAL_MACHINE\Software\Devnz\LogPSIProcessing=2 (DWORD)

After the scan completes, zip and attach the c:\psi.log. If that file doesnt exist, create a c:\temp directory, repeat the process then zip and attach the c:\temp\psi.log file.

[frazer]

OK, here is the PSI log file.

Thanks for stickiong with me- I've not had much luck with USB DVB-s devices and GBPVR, as I already have an original version Twinhan Starbox I bought specifically to use with GBPVR just before Twinhan decided the BDA drivers only worked with the Starbox2 (despite what the driver release said)!

Frazer

[sub]

I'm going to have to blame either the device's drivers on the mux you're trying to tune in. According to the logs, the device successfully manages to lock onto a signal at that frequency, but the data delivered from the device only contains padding packets and no real data.