Reply to thread

Message

<blockquote data-quote="Berns" data-source="post: 521129" data-attributes="member: 96677">Tourettes,As information from satellites is not comming in OK, checking CRC will often go wrong. I know about the CRC principle, as I've done IT studies, but don't know about the way it is used in sat transmission.In the client, there is a debug function, that users can turn on or off. Turning it on generates unstability, so I turned it off. The client is now rocksolid (am still using 1.0.0.0)For short, I'm not convinced using CRC or other debugging type of approach would be fit for purpose.SO: If I take a distance, could the team not just detect malfunctioning in another way? GIVEN:1) You are able to detect &quot;no signal&quot; or &quot;no graph&quot; upon tuning.2) While using manual streaming in the server, the server configurator continuously shows signal strength and quality. QUESTION: Is it not possible to use that information while timeshift is running (on all the streams, as I'm streaming from 2 receivers, each connected to 4 LNB's)?If that were possible, you could allow the user to set the level of confidence his system needs for both strength and quality. When the tuning would go below the threshold(s) a still image could be displayed on the client saying &quot;signal to weak&quot; or so. This would keep the timeshift stream alive, and prevent TVE3 to crash.WORK AROUND: (that will only work if the server does not take down the client with him):Currently I'm programming two batch processes - for the client that will do a remote net stop of the tvservice on the server, wait and do a tvservice start, to put in the main menu- for the cleint that will do a remote shutdown -r -t00 -f towards the serverIt's an ugly solution but at least my wife will not have to spend half an hour being guided to take remote control of the server in the attic. Next time she might maybe not miss the climax of CSI...</blockquote>

[QUOTE="Berns, post: 521129, member: 96677"] Tourettes, As information from satellites is not comming in OK, checking CRC will often go wrong. I know about the CRC principle, as I've done IT studies, but don't know about the way it is used in sat transmission. In the client, there is a debug function, that users can turn on or off. Turning it on generates unstability, so I turned it off. The client is now rocksolid (am still using 1.0.0.0) For short, I'm not convinced using CRC or other debugging type of approach would be fit for purpose. SO: If I take a distance, could the team not just detect malfunctioning in another way? GIVEN: 1) You are able to detect "no signal" or "no graph" upon tuning. 2) While using manual streaming in the server, the server configurator continuously shows signal strength and quality. QUESTION: Is it not possible to use that information while timeshift is running (on all the streams, as I'm streaming from 2 receivers, each connected to 4 LNB's)? If that were possible, you could allow the user to set the level of confidence his system needs for both strength and quality. When the tuning would go below the threshold(s) a still image could be displayed on the client saying "signal to weak" or so. This would keep the timeshift stream alive, and prevent TVE3 to crash. WORK AROUND: (that will only work if the server does not take down the client with him): Currently I'm programming two batch processes - for the client that will do a remote net stop of the tvservice on the server, wait and do a tvservice start, to put in the main menu - for the cleint that will do a remote shutdown -r -t00 -f towards the server It's an ugly solution but at least my wife will not have to spend half an hour being guided to take remote control of the server in the attic. Next time she might maybe not miss the climax of CSI... [/QUOTE]

Verification