On 09.06.2012 11:24, Reinhard Nissl wrote:
Hi,
Am 09.06.2012 08:40, schrieb Wolfgang Rohdewald:
in vdr-1.7.28 without patches
while browsing the log I found
Jun 9 05:28:08 server vdr: [13569] frontend 1/0 timed out while tuning to channel 1877, tp 212713 Jun 9 05:28:40 server vdr: [13569] frontend 1/0 regained lock on channel 14, tp 110743
so frontend 1 regained a lock it never had. That seems like a consequence of the fact that LostLock is only a local variable in cDvbTuner::Action, so it cannot be reset when the channel changes
Looks like LostLock should also be reset in case tsSet.
I guess that's a matter of philosophy. In normal operation the frontend doesn't report any such messages,so everything is fine. When the frontend loses the lock for any reason, I think it make sense to have it report back whenever it has regained the lock. If, in the meantime, the channel has been changed, well, then regaining the lock just so happens on a different channel.
Resetting LostLock in case tsSet could lead to logs where a frontend reports that it has lost the lock, but never reports when it has regained it.
Klaus