Mdapi support in Vista

[sub]

In that current case, its not able to load the multidec filter - most likely because it is unable to resolve its dependencies (probably to do with ffdecsa.dll or the slight different dll name used in later versions of mdapifilter.ax).

Try going back to this very old version: http://www.gbpvr.com/mdapi.zip, then reproduce the problem, then zip and attach those logs again.

[7ore]

OK. Heres a new set of logs.
The first time I tried, the mdapifilter never got active - on the other hand I got a psi.log!

But something happened then and gbpvr took a long time to start and everything got slow. So I reregistred the dlls again, no effect. But after I uninstalled and reinstalled everything works as before (ie, no coded channels).

But now I got the state I needed to get (i hope) useful logs.

But again, note that pi.log is from an earlier run where mdapi worked even less.

[sub]

2008-05-16 06:50:37.865 VERBOSE FindFilterByName failed to locate filter: GB-PVR PSI Parser

Without this filter, multidec support will definitely not work. Start a command prompt with 'run as administrator', change to the gbpvr directory, and run the ReRegisterFilters.bat file, then try again.

[7ore]

OK, re-ran it again and now I can't find that row on the other hand there is a simlar row:

Code:

2008-05-16 08:49:28.150    VERBOSE    FindFilterByName failed to locate filter: Agarwal's MDAPI filter
2008-05-16 08:49:28.180    VERBOSE    Using original MDAPI filter
2008-05-16 08:49:28.181    INFO    itr=0 @4.2
2008-05-16 08:49:28.181    VERBOSE    New MDAPI Filter instance created
2008-05-16 08:49:28.181    VERBOSE    Adding MDAPI Filter to graph

Btw it seems to work to run re-registerfilters.bat by rightcklick on it and "Run as administrator"

[sub]

You can ignore that bit of log you quoted. There is two different names for the mdapifilter. This code is just saying it couldnt find a filter with the new name, but managed to success find the old name. No problems there.

Reproduce the problem, then zip and attach the those logs again plus the psi.log and I'll take a look.

[7ore]

In this one I have two sets of logs. first one where I first use a free channel hat works, takes the + to go to the next channel that does not work). This action do not start the mdapi filter. I go back to the tv guide and start the same channel. Now mdapi filter do start.
This is the first set of logs.

Next I start and go through the guide, starting tcm. Let it go for a while and end it. I added "tcm" to this logs. the psi.log in this case is really uninteresting as it is zero bytes, but added it anyway....


btw, to stop the psi logging it should be enough to set the value to = 0, right?

[sub]

Unfortunately the log I was most interested in was zero bytes long in your logs so you'll have to try again.

I want the pvxr2.exe.log/pvrx2.exe-native.log/psi.log from starting live tv on an encrypted channel.

[sub]

btw, to stop the psi logging it should be enough to set the value to = 0, right?

Yes.

[7ore]

Unfortunately the log I was most interested in was zero bytes long in your logs so you'll have to try again.

I suspected that.
I only get psi.log big when selecting free channels. I tried a lot of different channels, but this is the best result so far, three rows.

[sub]

Sorry, I have no idea. Its like the device is delivering no data for these channels.