Hi There,
first: This is a new attempt to solve the problem which is also described here: https://forum.team-mediaportal.com/...when-recording-watching-other-channel.129335/
As i've some new insights i created a new thread in order to get things straight. Hopefully this is OK for the mods.
Short: My Problem:
On my HTPC Server i've got the problem on some-channels, that the TV-Playback/Recording stops after 10-70 seconds (approx.). This happens only after a longer time of inactivity (e.g. every evening when the TV(Server) is used firstly. If it happens, it is reproducable on every Tuner (4 Quad Tuner and 1 single DVB-S, see Profile for details).
The channels i'm having this issue with are all on the same frequency, transponder, polarisation, symbol rate. (See Screenshot "Channels")
After the first occurance of the problem, there's no further problem for the rest of the evening (at least for hours) on any of these channels.
Test-Setup:
I'm using the "Manual Control" to investigate this issue. I choose the first of the Tuner in the list, select one of the problematic channel and hit "Start TimeShift". The Signal Level goes to 93 and the Signal Qualitiy to 83. The TS packets processes starts to increase.
After 10-70 Seconds (roughly) the Signal Quality drops from one second to the other to zero and stays there (waited for some 15 Minutes). The log will then be filled with
"[2016-03-01 19:53:47,934] [130f3f10] [a34] - Recorderid 1ff Continuity error... 1 ( prev 7 ) - bad signal?".
I then hit "Stop Timeshifting" and can continue with the other Tuners, all showing the same behaviour. Afterwards, when i Start the Timeshift a second time no matter on which Tuner, the Signal Quality Stays constant and never dropps again (for the evening).
See Screenshots "OK" and "Problem"
Reproducable: (HTPC Server normally runs 24/7)
Other information:
I've had this problem on my HTPC-Server, which was initially a Win7 Operating system (former Gamer-PC). I then switched to Win10 "on the fly". For some reasons i know took the time to do a clean/fresh installation from scratch, again 64 Bit Windows 10 Home on a new SSD HD. The Environment changes, the problem stays.
At least the single Tuner Card was previously used in a single seat HTPC PC (same household). With this setup i didn't hat this problems.
My Question:
I'm completley lost here. I've no idea what might causes such a problem. Would it make sense to try a DVB-S Card of a different Vendor? I've also contacted TBS Support but no answer so far.
As the problem is reproducable (at least after some time of waiting):
Is there anything i can provide which might help to solve the problem? From my naive view some sort of a "Auto-Retune after 5 Bad signal in sequence"-Function would probably do the trick for me. This is what i do manually when the problem arises, but this won't work for scheduled recordings These simply stop and are leaving me with some 50 seconds recording
Thanks:
For reading until here I hope that this problem will be solved in the end.
Logs
I've attached the tswriter.log from one of the attemps, the intersting positions are:
first: This is a new attempt to solve the problem which is also described here: https://forum.team-mediaportal.com/...when-recording-watching-other-channel.129335/
As i've some new insights i created a new thread in order to get things straight. Hopefully this is OK for the mods.
Short: My Problem:
On my HTPC Server i've got the problem on some-channels, that the TV-Playback/Recording stops after 10-70 seconds (approx.). This happens only after a longer time of inactivity (e.g. every evening when the TV(Server) is used firstly. If it happens, it is reproducable on every Tuner (4 Quad Tuner and 1 single DVB-S, see Profile for details).
The channels i'm having this issue with are all on the same frequency, transponder, polarisation, symbol rate. (See Screenshot "Channels")
After the first occurance of the problem, there's no further problem for the rest of the evening (at least for hours) on any of these channels.
Test-Setup:
I'm using the "Manual Control" to investigate this issue. I choose the first of the Tuner in the list, select one of the problematic channel and hit "Start TimeShift". The Signal Level goes to 93 and the Signal Qualitiy to 83. The TS packets processes starts to increase.
After 10-70 Seconds (roughly) the Signal Quality drops from one second to the other to zero and stays there (waited for some 15 Minutes). The log will then be filled with
"[2016-03-01 19:53:47,934] [130f3f10] [a34] - Recorderid 1ff Continuity error... 1 ( prev 7 ) - bad signal?".
I then hit "Stop Timeshifting" and can continue with the other Tuners, all showing the same behaviour. Afterwards, when i Start the Timeshift a second time no matter on which Tuner, the Signal Quality Stays constant and never dropps again (for the evening).
See Screenshots "OK" and "Problem"
Reproducable: (HTPC Server normally runs 24/7)
- Wait some hours (e.g > 12h), Tune one of the channels: Signal Quality Drops after 10-70 Seconds and stays until retuned
- Restart TV Service after initial Problem: No Problem, Signal Quality stays constant
- Reboot Windows: No Problem, Signal Quality stays constant
- Shut down Windows, unplug power for ~10 Minutes: No Problem, Signal Quality stays constant
- Let the TV-Service/HTPC Server Idle for > 30 Minutes: No Problem, Signal Quality stays constant
- Let the TV-Service/HTPC Server Idle for > 2 hours, > 4 hours, > 8 hours: To be checked
Other information:
I've had this problem on my HTPC-Server, which was initially a Win7 Operating system (former Gamer-PC). I then switched to Win10 "on the fly". For some reasons i know took the time to do a clean/fresh installation from scratch, again 64 Bit Windows 10 Home on a new SSD HD. The Environment changes, the problem stays.
At least the single Tuner Card was previously used in a single seat HTPC PC (same household). With this setup i didn't hat this problems.
My Question:
I'm completley lost here. I've no idea what might causes such a problem. Would it make sense to try a DVB-S Card of a different Vendor? I've also contacted TBS Support but no answer so far.
As the problem is reproducable (at least after some time of waiting):
Is there anything i can provide which might help to solve the problem? From my naive view some sort of a "Auto-Retune after 5 Bad signal in sequence"-Function would probably do the trick for me. This is what i do manually when the problem arises, but this won't work for scheduled recordings These simply stop and are leaving me with some 50 seconds recording
Thanks:
For reading until here I hope that this problem will be solved in the end.
Logs
I've attached the tswriter.log from one of the attemps, the intersting positions are:
Code:
[2016-03-01 19:51:43,786] [130f3f10] [1484] - CDiskRecorder::Flush() - Throttle to 32336 bytes (max)
[2016-03-01 19:51:43,792] [130f3f10] [1484] - Recorder: TIMESHIFT start of audio detected
[2016-03-01 19:52:13,698] [130f3f10] [1484] - Recorder:Pid 1ff Continuity error... f ( prev b ) - bad signal?
[2016-03-01 19:53:20,206] [130f3f10] [a34] - CDiskRecorder::Flush() - Throttle to 32336 bytes (max)
[2016-03-01 19:53:47,934] [130f3f10] [a34] - Recorder:Pid 1ff Continuity error... 1 ( prev 7 ) - bad signal?
[2016-03-01 19:54:37,176] [130f3f10] [914] - CDiskRecorder::Flush() - Throttle to 32336 bytes (max)
[2016-03-01 19:55:00,941] [130f3f10] [914] - Recorder:Pid 1ff Continuity error... 5 ( prev b ) - bad signal?