Plugin: DVB Decrypter & Card Client

[routerunner]

This thread is about keeping track of your feedback during all stages of THIS project, so please post your comments here.

[Oddity]

Installation instructions - only one item to note: Remember when running the regsvr32 command you will need to have a command prompt with administrator rights.

Testing - No issues so far - Excellent ( but only a couple of hours testing ).

There also appears to be no affect on system or tuning performance.

Testing with TBS6984.

can't wait for the next installment.

[routerunner]

Originally Posted by Oddity

Installation instructions - only one item to note: Remember when running the regsvr32 command you will need to have a command prompt with administrator rights.

Amended, thanks.

Can you also please state the OS version and whether is 32/64 bits.

Cheers
Eddy

[Oddity]

Windows 7 64 bit

[routerunner]

Originally Posted by Oddity

Windows 7 64 bit

Excellent news, I was a little bit nervous about Windows 7 64bit combo.

Can you please also confirm that in at least one of the tuner's log file you can see something like this?

**********************************************************
* SageTV - DVB Decrypter & Card Client DirectShow Filter *
**********************************************************

27-02-2013 23:41:21 [Logger] Start
28-02-2013 13:49:31 [Decrypter::CheckInputType] Entry
28-02-2013 13:49:31 [Decrypter::CheckInputType] Exit
28-02-2013 13:49:31 [Decrypter::CheckTransform] Entry
28-02-2013 13:49:31 [Decrypter::CheckTransform] Exit
28-02-2013 13:49:31 [Decrypter::DecideBufferSize] Entry
28-02-2013 13:49:31 [Decrypter::DecideBufferSize] Exit

Eddy

[starfire]

Just tried this out, got it working (sort of).

I get 8 log files created although only have 6 tuners actually configured in Sage (guess it is picking up other ones I had).

It worked OK for DVB-T channels.

I then tried tuning via a Client to BBC1/ITV via my Nova-S2 but Sage crashed and terminated on my server - "SageTVService.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

Server=watson.microsoft.com
UI LCID=1033
Flags=1672018
Brand=WINDOWS
TitleName=SageTVService.exe
DigPidRegPath=HKLM\Software\Microsoft\Windows NT\CurrentVersion\DigitalProductId
ErrorText=If you were in the middle of something, the information you were working on might be lost.
Stage1URL=
Stage1URL=/StageOne/SageTVService_exe/6_0_13_1/msvcr100_dll/10_0_30319_415/00010b8b.htm
Stage2URL=
Stage2URL=/dw/stagetwo.asp?szAppName=SageTVService.exe&szAppVer=6.0.13.1&szModName=msvcr100.dll&szModVer=10.0.30319.415&offset=00010b8b


Nothing obvious in the log file when it crashes:
**********************************************************
* SageTV - DVB Decrypter & Card Client DirectShow Filter *
**********************************************************

28-02-2013 23:00:15 [Logger] Start
28-02-2013 23:00:15 [DllMain] Attach DLL
28-02-2013 23:07:15 [DllMain] Detach DLL via termination call
28-02-2013 23:07:15 [Logger] End

**********************************************************
* SageTV - DVB Decrypter & Card Client DirectShow Filter *
**********************************************************

28-02-2013 23:08:55 [Logger] Start
28-02-2013 23:08:55 [DllMain] Attach DLL
28-02-2013 23:14:58 [DllMain] Detach DLL via termination call
28-02-2013 23:14:58 [Logger] End

nor indeed in the sage debug log.

If I remove the PrePlugin entry in the registry everything is back to OK.

[routerunner]

Originally Posted by starfire

Just tried this out, got it working (sort of).

I get 8 log files created although only have 6 tuners actually configured in Sage (guess it is picking up other ones I had).

It worked OK for DVB-T channels.

I then tried tuning via a Client to BBC1/ITV via my Nova-S2 but Sage crashed and terminated on my server - "SageTVService.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

Server=watson.microsoft.com
UI LCID=1033
Flags=1672018
Brand=WINDOWS
TitleName=SageTVService.exe
DigPidRegPath=HKLM\Software\Microsoft\Windows NT\CurrentVersion\DigitalProductId
ErrorText=If you were in the middle of something, the information you were working on might be lost.
Stage1URL=
Stage1URL=/StageOne/SageTVService_exe/6_0_13_1/msvcr100_dll/10_0_30319_415/00010b8b.htm
Stage2URL=
Stage2URL=/dw/stagetwo.asp?szAppName=SageTVService.exe&szAppVer=6.0.13.1&szModName=msvcr100.dll&szModVer=10.0.30319.415&offset=00010b8b


Nothing obvious in the log file when it crashes:
**********************************************************
* SageTV - DVB Decrypter & Card Client DirectShow Filter *
**********************************************************

28-02-2013 23:00:15 [Logger] Start
28-02-2013 23:00:15 [DllMain] Attach DLL
28-02-2013 23:07:15 [DllMain] Detach DLL via termination call
28-02-2013 23:07:15 [Logger] End

**********************************************************
* SageTV - DVB Decrypter & Card Client DirectShow Filter *
**********************************************************

28-02-2013 23:08:55 [Logger] Start
28-02-2013 23:08:55 [DllMain] Attach DLL
28-02-2013 23:14:58 [DllMain] Detach DLL via termination call
28-02-2013 23:14:58 [Logger] End

nor indeed in the sage debug log.

If I remove the PrePlugin entry in the registry everything is back to OK.

Can you please send me the zip with all the "DVBDCC-Tuners-x.log" please? I don't expect to see any error in the DVBDCC.log, but in the others yes.

Cheers
Eddy

[starfire]

See attached.

[routerunner]

Originally Posted by starfire

See attached.

According to the log, the media type is fine, but the subtype is not supported. I need to find the exact value match to see alternatives.

Eddy

[routerunner]

Originally Posted by starfire

See attached.

I've just replaced the filter zip file with another version that is more verbose. Hopefully I can figure out better whether I can safely ignore the subtype in your case.

So it was the Hauppauge DVB-S2 NOVA-HD?

Eddy

[starfire]

Originally Posted by routerunner

So it was the Hauppauge DVB-S2 NOVA-HD?

Eddy

That caused the crash, yes when I tuned using that.

Just had a go with the new filter - on all my tuners I now get no signal reported but Sage no longer terminates on the server.

I shutdown Sage, replaced the filter and restarted - should I unregister/re-register the filter when it's replaced?

[routerunner]

Originally Posted by starfire

That caused the crash, yes when I tuned using that.

Just had a go with the new filter - on all my tuners I now get no signal reported but Sage no longer terminates on the server.

I shutdown Sage, replaced the filter and restarted - should I unregister/re-register the filter when it's replaced?

Yes, you should, shut down sage, unregister, copy, register, start sage, this is mainly to reset the tuner counter. You'll probably now have more logs than tuners as some extra information I was looking for are missing.

I know why the other tuners doesn't work, my fault, so please look for v1.0.0.2 when posted.

There are some issues with the Hauppauge NOVA S2 I discovered in a forum, basically it depends on how the tuner card presents itself to the graph that is different from the others, so the extra info might help to understand whether I can introduce a special case (hate doing this BTW).

Eddy

[Oddity]

Routerunner, I forgot to say on 64 bit the registry entry should be
\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\Frey Technologies\Common\AdditionalCaptureSetups\PluginFilter\PrePlugin="DVBDCC Transform Filter (SageTV)"

After all the mdapi testing I just pasted in the value rather than looking at the full path.

Also regarding the log file
I get lots of the entry and exit lines. I presume there is one each time the tuner tunes a channel.

I did lots of start / stop recordings.

[routerunner]

Originally Posted by Oddity

Routerunner, I forgot to say on 64 bit the registry entry should be
\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\Frey Technologies\Common\AdditionalCaptureSetups\PluginFilter\PrePlugin="DVBDCC Transform Filter (SageTV)"

After all the mdapi testing I just pasted in the value rather than looking at the full path.

Also regarding the log file
I get lots of the entry and exit lines. I presume there is one each time the tuner tunes a channel.

I did lots of start / stop recordings.

I've amended the instruction section accordingly, thank you.

Yes, is normal for the time being as I want to keep track of the method's entry/exit point, however on my system (Win XP 32) it doesn't do the entry/exit every time I record, but just once and it works flawlessly, so I would like to have a look at the log any way if you don't mind, maybe on 64bit the graph needs to be generated every time? Also, are you always using the same TBS6984? Can you confirm that the other MDAPI plugin are unregistered? It is very important to perform these tests without the possible intereference of other related plugins and in native mode only.

Cheers
Eddy

[Oddity]

Routerunner, appologies I'm not getting multiple entries as stated before each time I record. I had restarted sage a few times and this of course created the extra entries.

Yes all other filters unregistered and testing natiively with sage ( no dvbe4sage ) and using the TBS6984 card.

[routerunner]

Originally Posted by Oddity

Routerunner, appologies I'm not getting multiple entries as stated before each time I record. I had restarted sage a few times and this of course created the extra entries.

Yes all other filters unregistered and testing natiively with sage ( no dvbe4sage ) and using the TBS6984 card.

No need to apologise at all, I just wanted to make sure the testing condition are the same. Do you have, by any chance, other cards you can test this on? Like DVB-C or DVB-T tuners for instance.

Thanks for your terrific support BTW, I wish I could have more people involved. This is not UK or European specific as DVB-T is gradually growing in the USA and it will supersede ATSC in few years.

Eddy

[Oddity]

It has not affected my dvb-t tuners. i have two kworld dual tuners.

I do have a blackgold tuner but it does not work with sage natively

[routerunner]

Originally Posted by Oddity

It has not affected my dvb-t tuners. i have two kworld dual tuners.

I do have a blackgold tuner but it does not work with sage natively

Excellent news!

There is a new version to try. After installing the new version, can you please let me know the sample size message in the logs related to the DVB-T tuners?

Also, about your blackgold not being supported natively on SageTV, I don't know whether you noticed, but in the SageTV logs when it tunes on one of the TBS6984 tuners there is a message that says "This is a blackgold device"....

Cheers
Eddy

[routerunner]

Originally Posted by Oddity

It has not affected my dvb-t tuners. i have two kworld dual tuners.

What did you mean by that? Is the filter not being loaded for those tuners? Please clarify.

Cheers
Eddy

[Oddity]

Log files attached whilst using version 0.04.
Two tuners tested DVB-T and DVB-S

Hope this helps.