Config crashes during digital mapping

[gEd]

Sub: Just a reminder that UK DVB-T users have seen this problem since upgrading to the latest version, myself including (though I didn't report it earlier as I thought you have enough examples)

Logs attached.

[sub]

Probably the best way for us to get to the bottom of this is for a UK user to:

1) tweak their ini file from C:\Program Files\devnz\gbpvr\BDA\DVB-T to put the problem frequency first
2) create a c:\temp directory
3) create a HKEY_LOCAL_MACHINE\Software\Devnz\RecordFullTS=1 (DWORD) registry setting
4) try doing a scan
5) ...then zip and attach the c:\temp\full.ts file. If the file is too big, then they'll need to find somewhere to make that file available to me.

[kevinm207]

I don't know if it will help, except to confirm another instance of the this problem. Every time I scan for digital channels, GB-PVR config crashes out. Our cable provider broadcasts 5 HD digital channels unencrypted. I was trying to scan for them, but it crashes every time. I'm running the newest version of GB-PVR and have an ATI TV Wonder HD 650 Combo PCI-Ex.

Also, I have some FTP space on Hostmonster if someone needs the space to upload/download a large file. I'm not sure if I'm familiar enough with the software to be of much help with capturing data for diagnosing the problem. By the way, the program works great for my analog tuning.

[steeb]

Just another reminder,

this isn't just DVB-T but also DVB-S.

Steeb

[sub]

We'd still need to do exactly the same step as mentioned above, but in the DVB-S directory instead of DVB-T.

[steeb]

Sub yes,

but hating to do so as don't have dev machine and that means I loose everything I've got, perhaps my wife too Anyone else out there brave enough to run a scan with v 1.2.13?

Steeb

[martint123]

Sub: Just a reminder that UK DVB-T users have seen this problem since upgrading to the latest version, myself including (though I didn't report it earlier as I thought you have enough examples)

I've been scanning on my test machine quite a lot recently (five times today) and not had one crash. Could it be a transmitter dependant thing? I'm using Belmont.

[garymeds]

i'm using winter hill and got this crash 100% of the time. don't want to upgrade after starting from scratch with 1.2.09 :-$

[herrmannj]

Hey steep, keep you wife

scanning and what I did:

-I did a full scan on astra (0192.ini) and got a crash at transponder 27.
-Now edit the ini to put transponder 27 at first place and, guess what, no crash.
-repeatet some time, no crash.
-reverted the ini change and did a full scan; crash at transponder 27. hmmm....
-change ini to scan transponder 27, then 28, no crash. repeated...
-change ini to scan transponder 26 and then 27, voila, crash at 27. repeated, crash.

conclusion: transponder 27 crashes, bt only if 26 where scanned before.

@sub
will pm you the link to the full.ts of scanning astra 26 and crash on 27 in a few minutes.

joerg

[sub]

Thanks Joerg, but unfortunately I dont seem to be able to reproduce it with this file.