TBS 6921 it takes 10 seconds to switch between HD channels!

[lujo]

It takes at least 5 seconds before I got the message Signal is Locked.

Sat is Astra 23,5E and I am switching between Nederland 1 HD, Nederland 2 HD and Nederland 3 HD.

Nederland 1 HD = 11856.00 V 27500 5/6
Nederland 2 HD = 11739.00 V 27500 5/6
Nederland 3 HD = 12129.00 V 27500 5/6

If I look DebugView log file it seems that it takes 5 seconds to lock (Status: Locked).
Is this the problem of TBS 6921 driver? I have used 2.0.0.4 and i am now using 2.0.0.5 driver.

I don't have such problems with SD channels. With SD channels I get "Locked" in 1 second.

I have attached DebugView on WHS.LOG and DVBLinkServer.log
I can't upload those files in .zip format: "Could not upload attachment to ./files/738_e90ecef6e969c78bbf3cb4913ce9e4e6."

2011-Mar-26 08:03:19: Info. CTVSStreamSource::SelectLNB. Request for the currently selected LNB. No diseqc command will be sent
2011-Mar-26 08:03:24: Info. CTVSStreamSource::AddPID. Requesting PID 0

[edit]
Attachment is uploaded.
Cody or steven can you look at it and say what is the problem?
[/edit]

DebugView and DVBLinkServer.zip

(12.88 KiB) Downloaded 427 times

[steven]

Hi lujo
would mind to tell you what about the other player like DVBDream or progdvb,DVBView .

[lujo]

I have tryied DVBViewer with DVBViewer Recording Service so that I can stream over the network. For encrypted channels I use ACamd 0.6.20

This is the result when I am at the same satellite and I switch between two HD channels:

Log is from ACamd 0.6.20


Ned 1 HD -- Ned 2 HD

12:46:56.202: Ch: 2535 - NED1 HD
12:46:56.202: Programm crc: A5BEA354
12:46:56.203: PMT: chcache.ini, 09E7,1B7B,0100,0000006A,070E,00B7,NED1 HD
12:46:56.203: 0x09E7 0x1B7B 0x0100 0x0000006A 0x070E 0x00B7 01011110
12:46:56.266: CCcamN 0: Current Share 00000064, CAID 0100, Hops 0, NodeID D21A9635DC178A30
12:46:56.581: CCcamN 0: ECM [070E][0100/0000006A] Pro (0.315)
12:46:56.581: [00] SendDCW Odd: :E6A1F980B502CB82
12:46:56.581: [00] SendDCW Even: 640449B15B9ABFB4:
12:47:00.360:
12:47:00.360: Ch: 2480 - NED2 HD
12:47:00.360: Programm crc: E99857A3
12:47:00.361: PMT: chcache.ini, 09B0,17C0,0100,0000006A,0716,00B7,NED2 HD
12:47:00.361: 0x09B0 0x17C0 0x0100 0x0000006A 0x0716 0x00B7 01011110
12:47:00.371: CCcamN 0: Current Share 00000064, CAID 0100, Hops 0, NodeID D21A9635DC178A30
12:47:00.682: CCcamN 0: ECM [0716][0100/0000006A] Pro (0.310)
12:47:00.682: [00] SendDCW Odd: :780C038776410FC6

Ned1 (19,2E) -- Ned2 HD (23,5E)

12:39:15.281: Ch: 2111 - NED1
12:39:15.281: Programm crc: A8DB7616
12:39:15.282: PMT: chcache.ini, 083F,0FAB,0100,0000006A,070B,00B7,NED1
12:39:15.282: 0x083F 0x0FAB 0x0100 0x0000006A 0x070B 0x00B7 01011110
12:39:15.377: CCcamN 0: Current Share 00000064, CAID 0100, Hops 0, NodeID D21A9635DC178A30
12:39:15.382: CCcamN 0: ECM [070B][0100/0000006A] Pro (0.005)
12:39:15.382: [00] SendDCW Odd: :A69297CFDC2F7B86
12:39:15.382: [00] SendDCW Even: CE1D03EEBC99EF44:
12:39:17.881:
12:39:17.881: Ch: 2480 - NED2 HD
12:39:17.881: Programm crc: E99857A3
12:39:17.882: PMT: chcache.ini, 09B0,17C0,0100,0000006A,0716,00B7,NED2 HD
12:39:17.882: 0x09B0 0x17C0 0x0100 0x0000006A 0x0716 0x00B7 01011110
12:39:30.155: CCcamN 0: Current Share 00000064, CAID 0100, Hops 0, NodeID D21A9635DC178A30
12:39:30.473: CCcamN 0: ECM [0716][0100/0000006A] Pro (0.318)
12:39:30.473: [00] SendDCW Odd: :8FA7A9DF0A16A7C7


What can you tell me looking at this log?

[edit]
I also have tried Hadu 0.125 and it seems that it takes to long before i get PMT. It says: "No PMT... Looking for PMT" That takes long time.
Is "No PMT" problem of driver 2.0.0.4 and driver 2.0.0.5?
[/edit]

[lujo]

What I wrote above is issue what I have when changing between satellites with Diseqc 1.2

I have tried DVBViewer on the same hardware with Recordings Services (client-server).

When switching between Ned 1 HD, Ned 2 HD, Ned 3 HD with DVBViewer it takes max. 4 seconds. So it seems that this is the problem of DVBLogic/TVSource? Steven are you agree with me that when it is "working" with DVBViewer in 4 seconds than it shouldn't takes 10 secondst to work with TVSource?

I think developer of TVSource has send you or your company question about that. Can you please answer him what is the reason that I experience such slow changing times between HD channels.

With DVBViewer i have also issues (it workd but it takes much time) when switching between satellites but i will make another post about that.

[luchy]

hi lujo,
thanks for your feedback.
generally speaking,there are two problems about tbs6921.
the first, it takes about 4 seconds to lock HD channel.about this,DVBViewer and DVBLink are the same with each other.because this time is spent in the driver.detailed that is the driver don't know which you want to lock, HD or SD? therefore,it will first lock SD,and then lock HD every time.thus,when we lock HD channel, it will first try to lock SD for several times,of course it won't lock it,then it turn to lock HD. so locking HD channel will take more time than SD channel.
maybe 4 second is a little too long to accept.we just make sure the card can work well on every available channel.

the second,when switching encrypted program,it will take about 5 seconds under DVBLink.as you guessed that it takes this time to get PMT table.because DVBViewer don't do decryption work,so it won't wait to PMT table and won't waste this time.for DVBLink,spending this time is neccessary.after locked,it need to wait PMT table and do some request to server then parsed...at last, get the key to decrypt program. all of these,getting PMT table will take the most time. depending on the different programes,it will take one second to ten second.

[vasvi]

hi lujo,
thanks for your feedback.
detailed that is the driver don't know which you want to lock, HD or SD? therefore,it will first lock SD,and then lock HD every time.

Why don't TBS driver memorize type of certain transponder (S/S2) at the first time and then switch to exact type (SD or HD)?

[luchy]

Why don't TBS driver memorize type of certain transponder (S/S2) at the first time and then switch to exact type (SD or HD)?

actually,the type of transponder(s/s2) should be memorized by application.you can see there are frequency,polarity,symbrate,FEC and so on informations in transponders of satellite.
the driver only deal with according to the type what application pass it.
there are three cases in driver:
ap pass dvbs to it,the driver will only try to lock SD.
ap pass dvbs2 to it,the driver will only try to lock HD.
ap pass auto or nothing to it,the driver will automatically lock,first SD then HD.

[vasvi]

actually,the type of transponder(s/s2) should be memorized by application.you can see there are frequency,polarity,symbrate,FEC and so on informations in transponders of satellite.
the driver only deal with according to the type what application pass it.
there are three cases in driver:
ap pass dvbs to it,the driver will only try to lock SD.
ap pass dvbs2 to it,the driver will only try to lock HD.
ap pass auto or nothing to it,the driver will automatically lock,first SD then HD.

So this is issue for DVBlink?
DVBlink does not provide information to the driver about type (S/S2) of transponder during channel switching?

[lujo]

hi lujo,
thanks for your feedback.
generally speaking,there are two problems about tbs6921.
the first, it takes about 4 seconds to lock HD channel.about this,DVBViewer and DVBLink are the same with each other.because this time is spent in the driver.detailed that is the driver don't know which you want to lock, HD or SD? therefore,it will first lock SD,and then lock HD every time.thus,when we lock HD channel, it will first try to lock SD for several times,of course it won't lock it,then it turn to lock HD. so locking HD channel will take more time than SD channel.
maybe 4 second is a little too long to accept.we just make sure the card can work well on every available channel.

Hi Luchy, first thank you for the explanation how TBS 6921 works.
But is this "problem" only for TBS 6921? Or does this also apply for example TBS 8921?
Just simply thoughts: Is it not possible to "tell the driver" lock one time on SD and if it not work do it one time on HD? Or should we with this method get much more "NO LOCK" on SD channels?

the second,when switching encrypted program,it will take about 5 seconds under DVBLink.as you guessed that it takes this time to get PMT table.because DVBViewer don't do decryption work,so it won't wait to PMT table and won't waste this time.for DVBLink,spending this time is neccessary.after locked,it need to wait PMT table and do some request to server then parsed...at last, get the key to decrypt program. all of these,getting PMT table will take the most time. depending on the different programes,it will take one second to ten second.

Can you explain to me why it is needed/neccessary for DVBLink to get PMT table and DVBViewer don't need PMT table?


[edit]
It seems that developer from DVBLink (TVSource) don't agree:
"It does. TVSource remembers all information that is needed to tune the channel, including modulation. Based on the modulation value the channel type is set for TBS driver." http://www.dvblogic.com/phpBB3/viewtopic.php?f=43&t=12111&start=15#p39534
"They definitely should know it because we use the DVBDream driver file that they have written themselves."

I now don't know what is true and can you please explain to me where is the problem?

[vasvi]

Luchi, please read last answers of DVBlogic representative:
http://dvblogic.com/phpBB3/viewtopic.php?f=43&t=12111&p=39536#p39536
He sad that TVsourse send all required information (including S/S2 type) about transponder to TBS card driver.
So why it takes almost 4 seconds to lock on transponder?