Setting up Twinhan 102g with new release

[sub]

I'm currently running on Vista, which installs it's own drivers for twinhan 1020.
Mytheatre is working fine.

So I wanted to try out GBpvr and see how it works. Everything seems to be setup, but I can not get it to scan properly.
When it scans first tp, it's usally what ever the last channel was watched on Mytheatre.
As far as I can tell it doesn't properly change the settings from tp to tp.
It always scans the same channels in.

Driver installed :
DVB-TV 878 Digital Capture Driver
Version 1.2.3.8
Driver Date 3/4/2006

Using LNB Setting from mythreatre of
LNB LOF1 9750
LNB Switch 11700
LNB LOF2 11250
Power (Checked)

BDA Advanced Settings are all default.

Ah, I remember talking to twinhan about this bug about a year ago. Their drivers if no valid signal was present the drivers could continue to return a chunk of old data that was cached in the driver.

I'm not sure if they fixed this or not. You could try the latest drivers if you're not already.

[VSLG]

Yes I have the most current drivers.

In fact like I stated in my first post, this card is working perfectly using these
drivers with Mythreatre.

So I'm thinking it's more a bug in your software.

Nothing personal.

[sub]

I remember the problem very well. It is a Twinhan drivers bug rather than a GB-PVR bug.

The reason that you see this bug in GB-PVR but not in some of the other DVB apps is because to support a wider range of BDA cards GB-PVR ignores the 'signal locked' status when scanning and instead relies on the card delivering valid data to determine if the channels are found at each frequency. This scheme works really well, except in this case where buggy Twinhan drivers can return the last block of valid data it received when their is no signal lock. GB-PVR processes this data, and finds it contains channels etc, so assumes they're for the current frequency.

MyTheatre most likely relies on the 'signal locked' status instead, so never sees the driver problem.

If you look at the bda.ini file you'll notice that a few of the Twinhan device had a special 'ONLY_SCAN_ON_LOCK' setting that other cards dont have. This setting was to work around this exact problem. Unfortunately this setting was only used by some other custom scanning utilities I have, not the config app scanning screen. I'll add that same logic to the config app for the next release.

[VSLG]

Well if your looking for someone to work with, I can surely help ya test it out and get the card working. Shouldn't be to hard.

I remember the problem very well. It is a Twinhan drivers bug rather than a GB-PVR bug.

The reason that you see this bug in GB-PVR but not in some of the other DVB apps is because to support a wider range of BDA cards GB-PVR ignores the 'signal locked' status when scanning and instead relies on the card delivering valid data to determine if the channels are found at each frequency. This scheme works really well, except in this case where buggy Twinhan drivers can return the last block of valid data it received when their is no signal lock. GB-PVR processes this data, and finds it contains channels etc, so assumes they're for the current frequency.

MyTheatre most likely relies on the 'signal locked' status instead, so never sees the driver problem.

If you look at the bda.ini file you'll notice that a few of the Twinhan device had a special 'ONLY_SCAN_ON_LOCK' setting that other cards dont have. This setting was to work around this exact problem. Unfortunately this setting was only used by some other custom scanning utilities I have, not the config app scanning screen. I'll add that same logic to the config app for the next release.

[sub]

You could try the attached patch. You'd also need to add the 'ONLY_SCAN_ON_LOCK=1' line on the card you've got selected in the bda.ini.

If it doesnt work for you, then zip and attach the config.exe.log and config.exe-native.log and I'll take a look.

[VSLG]

Ok. Updated the config.exe file, and also added that to ini file.

This time when it scanned, it gave me "Unknown" for all channels.

[sub]

Ok, here is another attempt at it. The logs indicate I was half way there...

[VSLG]

With this build of config.exe, I didn't even get unknow. Nothing scanned. Here are the logs

Ok, here is another attempt at it. The logs indicate I was half way there...

[sub]

OK - I'll take another look in the morning.

[VSLG]

Any luck? I'm got a few holidays here so would like to try and get this all worked out.

Merry Christmas BTW