TVEngine3 Snapshot: 02-03-2008 05-08h Revision 17267 (2 Viewers)

[bigflause]

I have tried some weeks ago to get the new tt bda api working.

There is an error when calling the api functions, like this result:

03-02-2008 11:13:19.921 Technotrend: initalized id:3d8f80, driver version:230.135.34.5

After this, tvservice crashes. It looks like some incompatible pointer handling or something like this.

I found out that I had to change the function definitions in technotrend.cpp (removing the FAR PASCAL and _stdcall).
Then it

03-02-2008 11:45:32.515 Technotrend: initalized id:17, driver version:5.0.0.18

and the access violation is gone.

Could you please check my "fix" and maybe apply it to the code?

Current release is completely unsuable for tt cards....

where did you get driver 5.0.0.18?

this makes interesting reading. I found it on a different site.

SW: TT BDA-API 1.0.1.8

What's new:
[*] full protocol implementation for CI (S2-3650)
[*] interface for PC wake-up with IR code over USB
[*] interface for _b_link__ing LED's


Problem however is that CI still does not work properly with this new API. Modules are properly detected and initialized. Also CI menu works with 3rd party applications like DVBViewer. No decryption takes place however.

With Mascom modules a channel is decrypted within a 3rd party after being set within TT-Media Center. Mascom modules most likely save a state that is afterwards being reused within the 3rd party application.

So decryption still only works with TT-Media Center in combination with the S2-3650 (besides the mentioned trick which is not very usable).

 

[N.Spieard]

The new svn build is working fine for me, fast channel switching.

The downside is that I can't watch 1 channel and record the other on the same transponder, or live tv stops (no picture and sound but still timeshifting) or the recording stops (no picture & sound but still recording).
I checked the TVserver / manual control and noticed that for the problem channel it displays channel scrambled =yes

No errors in log files.

I use a Twinhan DVB-C CI card (2031) driver version 1.2.3.8 and Twinhan Mantis (2033) DVB-C CI, they both act the same.
OS = Vista Home Premium

I have this problem for a long time now, has anyone any idea what can be wrong?

With DVBViewer it works fine I can record 6 streams on the same transponder without any problem.

 

[morpheus_xx]

where did you get driver 5.0.0.18?

this makes interesting reading. I found it on a different site.

I only downloaded the 5.0.0.12 driver from tt homepage, nothing else. I don't know why this version is shown...

 

[The Doctor]

The new svn build is working fine for me, fast channel switching.

The downside is that I can't watch 1 channel and record the other on the same transponder, or live tv stops (no picture and sound but still timeshifting) or the recording stops (no picture & sound but still recording).
I checked the TVserver / manual control and noticed that for the problem channel it displays channel scrambled =yes

No errors in log files.

Same to me, I use a floppy DTV S2 card from Digital Everywhere.

 

[gemx]

The new svn build is working fine for me, fast channel switching.

The downside is that I can't watch 1 channel and record the other on the same transponder, or live tv stops (no picture and sound but still timeshifting) or the recording stops (no picture & sound but still recording).
I checked the TVserver / manual control and noticed that for the problem channel it displays channel scrambled =yes

No errors in log files.

Same to me, I use a floppy DTV S2 card from Digital Everywhere.

Have you ever tried incrementing the value for "decryptLimit" in table "Card" in the TvLibrary database?
That should solve your problem

 

[N.Spieard]

Have you ever tried incrementing the value for "decryptLimit" in table "Card" in the TvLibrary database?
That should solve your problem

Yes the decryptlimit is set to 8 for each card that doesn't fix it for me.
Also the settings on the alphacrypt cam are set to multi.

Any other ideas?



Niels

 

[The Doctor]

Yes I did, by the way I use canaldigital cam.

It did work perfectly a couple of versions back. I'll check when it started to go wrong tomorrow.