Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 792914" data-attributes="member: 82144">Hi againThe two problems that you mentioned were:1. Tuning times ==&gt; solved - MSE problem (???).2. Tuning failures.If this is the case, you have to prove that the most recent driver is more unreliable than the older driver with the same hardware setup, software setup, and channels.It is not what I need - it is what TeVii need. At a guess, I would say that you need to run tuning tests on the same set of channels with each driver over a long time (at least 1000 tunes).It may not interfere with the signal reception, however all depends on the type of tuning failure as to whether it could have any effect. We don't provide any support for it and I recommend that you disable it in your testing.There is nothing we can do about this. As I've already said, the most time consuming part of the tuning process in the logs you previously provided seems to be the TeVii custom tuning function.mm</blockquote>

[QUOTE="mm1352000, post: 792914, member: 82144"] Hi again The two problems that you mentioned were: 1. Tuning times ==> solved - MSE problem (???). 2. Tuning failures. If this is the case, you have to prove that the most recent driver is more unreliable than the older driver with the same hardware setup, software setup, and channels. It is not what I need - it is what TeVii need. At a guess, I would say that you need to run tuning tests on the same set of channels with each driver over a long time (at least 1000 tunes). It may not interfere with the signal reception, however all depends on the type of tuning failure as to whether it could have any effect. We don't provide any support for it and I recommend that you disable it in your testing. There is nothing we can do about this. As I've already said, the most time consuming part of the tuning process in the logs you previously provided seems to be the TeVii custom tuning function. mm [/QUOTE]

Verification