Setting up Twinhan 102g with new release

[ashwincr]

halcut, the nvidia codecs are designed to deregister itself in a debug environment. so you will need to re-register them, or reinstall them.

[halcut]

halcut, the nvidia codecs are designed to deregister itself in a debug environment. so you will need to re-register them, or reinstall them.

So does it mean that I cannot properly run gbpvr in debug mode? Cause i will never get video or audio.

[sub]

halcut, the nvidia codecs are designed to deregister itself in a debug environment. so you will need to re-register them, or reinstall them.

lol - thats annoying. Obviously trying to stop people from finding out their secrets.

So does it mean that I cannot properly run gbpvr in debug mode? Cause i will never get video or audio.

It just means you'll have to use another decoder when perform this test.

[halcut]

It just means you'll have to use another decoder when perform this test.

ok will try with intervideo codecs.

[halcut]

Sub,

Attached is the debug dump files. Actual size of the dump is 800mb but I have rared it to 140. Hope this tells us something.

crash.rar

[sub]

I was hoping it would generate a mini-dump file, which is a whole lot smaller. No worries though, I'm downloading it now.

[sub]

Ok, the memory dump loaded in WinDBG pretty clearly identifies the crash as happening in vplug plugin.

Faulting stack below ---
# ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
00 0a2efe50 0af3c3a2 0eedfade 00000001 00000007 KERNEL32!RaiseException+0x52
01 0a2efeec 0b02bf97 0a2eff00 0b02c04d 0a2eff2c vplug+0xc3a2
02 0a2eff2c 0a1964bc 00000002 000000b8 047372fc vplug!DVBPLGGetInfo+0x1635f
03 0a2eff60 77d51091 0a1965f4 047372f8 77d51042 mdapifilter!DllMain+0x52dd
04 0a2eff64 0a1965f4 047372f8 77d51042 047e3968 USER32!GetMessageA+0x4f
05 0a2eff88 0a193be6 000564a0 000000b6 00127188 mdapifilter!DllMain+0x5415
06 0a2effec 00000000 0a193b90 00000000 00000000 mdapifilter!DllMain+0x2a07

Given the same plugin works for you in other apps, I can only guess that its some of the data being passed to vplug by either Aragwals directshow wrapper, or an incorrect value being passed in by GB-PVR to Aragwals wrapper (in turn passed to vplug). Either way, this data eventually causes vplug to shit itself.

I wonder if Aragwal's wrapper produces any logs?

I'll ask Aragwal for some more info.

[halcut]

wonderful sub.. I will also try to use other plugin if it works with mdapi.

[sub]

I will also try to use other plugin if it works with mdapi.

OK, let us know if you have more success with another one.

I've sent a PM to Aragwal with some details about what is happening, and have asked for some more info. Hopefully he'll get back to us soon. (DVBN site is really slow and barely usable to me recently, but hopefully he is still monitoring it).

[Shaky]

Hi All,

Great work on this so far! Thanks for sharing the info too. I've been reading for a couple days and am just getting around to trying this out myself. Have been using GBPVR on and off for several months now with a PVR-250 and regular cable feed. Its been rock solid so haven't played around much.

Trying a 102g card today and have been having the crashing issue as well this morning.

Just tried the latest Vplug (was on 1.3.8) and have been changing channels non stop for 15 minutes. No crashes. Perhaps try 1.4.0 if you are not using it already and see if that works for you too. I hope I'm not reporting this too early as it could be a fluke...but hopefully not. I'll post back if it fails on me...

-Shaky