Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 1094111" data-attributes="member: 82144">Hello againIt sounds like failure to select (or hold the selection of) the correct DiSEqC port.Port A is usually the default port for switches, which is probably why you have the most success with port A.This patch is not a driver. It communicates with the driver, but it is not the driver itself. The driver is what you download and install from TBS's website to get Windows (or Linux) to recognise the tuner.There is nothing in the patch that would induce the behaviour. The patch tells the tuner driver to send the requested DiSEqC command; it expects the tuner driver to send the command and the switch to obey the command. As such, if the switch isn't reliable... well it isn't really within our control. About the only thing we could do is try to send the DiSEqC command multiple times. However that slows down tuning/zapping, so no such function has been implemented.When recordings stop after 30 seconds it is because the tuner stops delivering the stream not because TV Server actively kills the recording. TV Server doesn't actively check that the tuner is streaming or have any mechanism for attempting to retune if the tuner does stop streaming. In other words, when your recordings are failing TV Server is sitting there thinking it is recording successfully... but actually it is not.The recording restart that you observe when you "happen to shut down TV Server while it's recording" is a behaviour of the scheduler, which is completely independent to the tuner handling. Every 15 seconds the scheduler checks what recordings should be running and whether they're running or not. It will restart any recordings that stop due to TV Server restart because it can detect the recording is not occurring when it should be. However, the scheduler will not know if the tuner stops streaming.Regards,mm</blockquote>

Verification