TVSERVER: running recordings will be interrupted - "Discontinuity header bit set!" (1 Viewer)

rue

MP Donator
  • Premium Supporter
  • January 1, 2009
    113
    12
    Home Country
    Germany Germany
    Hi I additionally have to come back to this issue.

    Meanwhile I am using MP 1.7 RC since a while and I have this issue "up and running".

    Today I had the chance to collect something - might be it helps to get for an answer or bugfix.

    As reported I currently use two different kind of adapters: TBS6928 (which is a PCIe one) and Pinnacle 460e (which is an USB one) together on the sam PC. The USB device will be powered off by Win 8.1 (measured it) completely to prevent from stick based side effects.

    For today I had 2 recording on different programs scheduled - one 1:15 pm (13:15) on "Disney Channel/Pocahontas II", which is 576i/p@MPEG2|@ASTRA and the second one, which was "Independence Day" on SAT.1 (576i/p@MPEG2@ASTRA).

    Situation based Disney Channel has a different transponder than SAT.1 .. for this the first recording came up on TBS 6928 and was running fine up to the moment the second recording was started. For the second recording at 2:05pm (14:05) the Pinnacle 460e was used.

    So far ... everything fine ... just with the beginning of the second recording the continuity check errors on both streams came up. Before at the time only the TBS will be used - there was no problem.

    As a result the TSWriter is not able to write any significant (and snesefull) data to the disc. The number of discontiunations seems to be so high that now valid stream can be exist jumping over that time frame. In this case you will find on the disc for the first (good starting record) a perfect file up to the point "on damage" and after this only fragments. For "ID4" it results to a file of about 200 MB.

    I send you the logfiles as an attachment, please be gentle and verify it - just tell me where I am wrong, or give me an idea for a next step. TVService.log and TSWriter.log will have the appropriate informations.

    best regards and thanks in advance

    RUE
     

    Owlsroost

    Retired Team Member
  • Premium Supporter
  • October 28, 2008
    5,540
    5,038
    Cambridge
    Home Country
    United Kingdom United Kingdom
    I can't tell what is causing the continuity errors, but they are happening every 3-4 seconds and only on the second (460e) tuner - there are no errors in the TsWriter log for the first (TBS) tuner. The two tuners are being handled by separate instances of TsWriter, so it's unlikely to be direct TsWriter - TsWriter interaction.

    Have you got any software running that might be doing something every few seconds on USB (or causing CPU spikes etc.) ?

    Code:
    [2014-03-23 14:05:14,805] [5941398] [95c] - Recorder: RECORD    start of audio detected
    [2014-03-23 14:11:08,670] [5941398] [95c] - Recorder:Pid ff Continuity error... 7 ( prev 2 ) - bad signal?
    [2014-03-23 14:11:08,670] [5941398] [95c] - Recorder:Pid 103 Continuity error... c ( prev a ) - bad signal?
    [2014-03-23 14:11:08,670] [5941398] [95c] - Recorder:Pid 20 Continuity error... 3 ( prev c ) - bad signal?
    [2014-03-23 14:11:08,670] [5941398] [95c] - Recorder:Pid 100 Continuity error... 8 ( prev 6 ) - bad signal?
    [2014-03-23 14:11:14,190] [5941398] [95c] - Recorder:Pid ff Continuity error... 9 ( prev 5 ) - bad signal?
    [2014-03-23 14:11:14,190] [5941398] [95c] - Recorder:Pid 100 Continuity error... 1 ( prev f ) - bad signal?
    [2014-03-23 14:11:14,190] [5941398] [95c] - Recorder:Pid 103 Continuity error... 7 ( prev 5 ) - bad signal?
    [2014-03-23 14:11:14,198] [5941398] [95c] - Recorder:Pid 20 Continuity error... a ( prev 8 ) - bad signal?
    [2014-03-23 14:11:18,814] [5941398] [95c] - Recorder:Pid 103 Continuity error... 5 ( prev 5 ) - bad signal?
    [2014-03-23 14:11:18,830] [5941398] [95c] - Recorder:Pid 100 Continuity error... 4 ( prev b ) - bad signal?
    [2014-03-23 14:11:23,422] [5941398] [95c] - Recorder:Pid ff Continuity error... 6 ( prev a ) - bad signal?
    [2014-03-23 14:11:23,422] [5941398] [95c] - Recorder:Pid 103 Continuity error... c ( prev 0 ) - bad signal?
    [2014-03-23 14:11:23,422] [5941398] [95c] - Recorder:Pid 100 Continuity error... 2 ( prev 3 ) - bad signal?
    [2014-03-23 14:11:23,422] [5941398] [95c] - Recorder:Pid 20 Continuity error... 8 ( prev a ) - bad signal?
    [2014-03-23 14:11:28,646] [5941398] [95c] - Recorder:Pid ff Continuity error... d ( prev 1 ) - bad signal?
    [2014-03-23 14:11:28,646] [5941398] [95c] - Recorder:Pid 100 Continuity error... 3 ( prev f ) - bad signal?
    [2014-03-23 14:11:28,646] [5941398] [95c] - Recorder:Pid 103 Continuity error... 7 ( prev 1 ) - bad signal?
    [2014-03-23 14:11:28,646] [5941398] [95c] - Recorder:Pid 20 Continuity error... 9 ( prev 5 ) - bad signal?
    [2014-03-23 14:11:32,566] [5941398] [95c] - Recorder:Pid ff Continuity error... d ( prev a ) - bad signal?
    [2014-03-23 14:11:32,566] [5941398] [95c] - Recorder:Pid 20 Continuity error... 9 ( prev a ) - bad signal?
    [2014-03-23 14:11:32,566] [5941398] [95c] - Recorder:Pid 103 Continuity error... f ( prev 0 ) - bad signal?
    [2014-03-23 14:11:32,566] [5941398] [95c] - Recorder:Pid 100 Continuity error... a ( prev a ) - bad signal?
    [2014-03-23 14:11:32,662] [5941398] [95c] - Recorder: RECORD    Info : Program clock reference forward jump ( 36984 ).
    [2014-03-23 14:11:34,142] [5941398] [95c] - Recorder:Pid ff Continuity error... 7 ( prev 7 ) - bad signal?
    [2014-03-23 14:11:34,142] [5941398] [95c] - Recorder:Pid 103 Continuity error... c ( prev 9 ) - bad signal?
    [2014-03-23 14:11:34,158] [5941398] [95c] - Recorder:Pid 20 Continuity error... e ( prev a ) - bad signal?
    [2014-03-23 14:11:34,158] [5941398] [95c] - Recorder:Pid 100 Continuity error... a ( prev 7 ) - bad signal?
    [2014-03-23 14:11:34,158] [5941398] [95c] - Recorder:Pid 103 Continuity error... 0 ( prev d ) - bad signal?
    [2014-03-23 14:11:34,166] [5941398] [95c] - Recorder:Pid 100 Continuity error... c ( prev a ) - bad signal?
    [2014-03-23 14:11:37,342] [5941398] [95c] - Recorder:Pid 103 Continuity error... 1 ( prev 8 ) - bad signal?
    [2014-03-23 14:11:37,342] [5941398] [95c] - Recorder:Pid 20 Continuity error... b ( prev 0 ) - bad signal?
    [2014-03-23 14:11:37,342] [5941398] [95c] - Recorder:Pid 20 Continuity error... d ( prev b ) - bad signal?
    [2014-03-23 14:11:37,342] [5941398] [95c] - Recorder:Pid ff Continuity error... e ( prev e ) - bad signal?
    [2014-03-23 14:11:37,350] [5941398] [95c] - Recorder:Pid 103 Continuity error... 4 ( prev 1 ) - bad signal?
    [2014-03-23 14:11:37,350] [5941398] [95c] - Recorder:Pid 100 Continuity error... 0 ( prev 1 ) - bad signal?
    [2014-03-23 14:11:40,798] [5941398] [95c] - Recorder:Pid ff Continuity error... 4 ( prev 0 ) - bad signal?
    [2014-03-23 14:11:40,798] [5941398] [95c] - Recorder:Pid 20 Continuity error... 9 ( prev 9 ) - bad signal?
    [2014-03-23 14:11:40,798] [5941398] [95c] - Recorder:Pid 100 Continuity error... 8 ( prev 3 ) - bad signal?
    [2014-03-23 14:11:40,798] [5941398] [95c] - Recorder:Pid 103 Continuity error... 0 ( prev 8 ) - bad signal?
    [2014-03-23 14:11:44,406] [5941398] [95c] - Recorder:Pid ff Continuity error... 9 ( prev 7 ) - bad signal?
    [2014-03-23 14:11:44,406] [5941398] [95c] - Recorder:Pid 103 Continuity error... 2 ( prev 6 ) - bad signal?
    [2014-03-23 14:11:44,414] [5941398] [95c] - Recorder:Pid 20 Continuity error... 1 ( prev 4 ) - bad signal?
    [2014-03-23 14:11:44,414] [5941398] [95c] - Recorder:Pid 100 Continuity error... 4 ( prev 5 ) - bad signal?
    [2014-03-23 14:11:48,006] [5941398] [95c] - Recorder:Pid ff Continuity error... 0 ( prev 6 ) - bad signal?
    [2014-03-23 14:11:48,006] [5941398] [95c] - Recorder:Pid 20 Continuity error... 6 ( prev 0 ) - bad signal?
    [2014-03-23 14:11:48,006] [5941398] [95c] - Recorder:Pid 103 Continuity error... 3 ( prev 9 ) - bad signal?
    [2014-03-23 14:11:48,014] [5941398] [95c] - Recorder:Pid 100 Continuity error... f ( prev 1 ) - bad signal?
    [2014-03-23 14:11:50,070] [5941398] [95c] - Recorder:Pid ff Continuity error... d ( prev 5 ) - bad signal?
    [2014-03-23 14:11:50,070] [5941398] [95c] - Recorder:Pid 103 Continuity error... 1 ( prev a ) - bad signal?
    [2014-03-23 14:11:50,070] [5941398] [95c] - Recorder:Pid 100 Continuity error... f ( prev b ) - bad signal?
    [2014-03-23 14:11:53,606] [5941398] [95c] - Recorder:Pid ff Continuity error... a ( prev 7 ) - bad signal?
    [2014-03-23 14:11:53,606] [5941398] [95c] - Recorder:Pid 100 Continuity error... 1 ( prev 8 ) - bad signal?
    [2014-03-23 14:11:53,606] [5941398] [95c] - Recorder:Pid 20 Continuity error... a ( prev f ) - bad signal?
    [2014-03-23 14:11:53,606] [5941398] [95c] - Recorder:Pid 103 Continuity error... 1 ( prev f ) - bad signal?
    [2014-03-23 14:11:55,230] [5941398] [95c] - Recorder:Pid ff Continuity error... a ( prev e ) - bad signal?
    [2014-03-23 14:11:55,230] [5941398] [95c] - Recorder:Pid 20 Continuity error... 6 ( prev b ) - bad signal?
    [2014-03-23 14:11:55,230] [5941398] [95c] - Recorder:Pid 100 Continuity error... 7 ( prev a ) - bad signal?
    [2014-03-23 14:11:55,230] [5941398] [95c] - Recorder:Pid 103 Continuity error... a ( prev 2 ) - bad signal?
    [2014-03-23 14:11:58,830] [5941398] [95c] - Recorder:Pid ff Continuity error... a ( prev 1 ) - bad signal?
    [2014-03-23 14:11:58,830] [5941398] [95c] - Recorder:Pid 100 Continuity error... 3 ( prev 9 ) - bad signal?
    [2014-03-23 14:11:58,830] [5941398] [95c] - Recorder:Pid 103 Continuity error... d ( prev a ) - bad signal?
    [2014-03-23 14:11:58,846] [5941398] [95c] - Recorder:Pid 20 Continuity error... e ( prev 0 ) - bad signal?
    [2014-03-23 14:25:07,096] [5941398] [10e0] - debug: AddChannel()
    [2014-03-23 14:25:07,096] [5941398] [10e0] - analyzer: reset
     

    rue

    MP Donator
  • Premium Supporter
  • January 1, 2009
    113
    12
    Home Country
    Germany Germany
    Hi again!

    No - I don't have - and I have the newest one drivers from Pinnacle installed.

    The problem is you can see it the other way round, too - if the pinnacle is recording everything is running fine.

    In the moment a second recording on the TBS ist starting I am running in the same nice feature, but seen from the other side of the edge.

    I wonder what happens if I place a dual channel TBS inside the system .... but hae currently no one.

    The only problematic thing I know is the chipset and the board itself - this is a '77 chipset (DH77DF) from Intel.
    With this I have troubles initializing the PCIe slot/TV cards, but this is a "start-up" problem of the chipset or BIOS. Once the card is recognized it will run.

    So in the past I had lesser problems with the USBs on this board .. that I was was going with the Pinnacle USB grabbers.

    Thanks and best regards

    RUE
     

    rue

    MP Donator
  • Premium Supporter
  • January 1, 2009
    113
    12
    Home Country
    Germany Germany
    Hi and good morning!

    Yesterday I received the new card TBS 6991 SE (double tuner, new release).

    For the first impression everything seem work fine, but later on the sam problem came up again - but it will not longer be necessary to have multiple log-on's to the card.

    [2014-03-25 21:30:14,314] [66dcac0] [be0] - Logging format: [Date Time] [InstanceID] [ThreadID] Message....
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - ===================================================================
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - ---------------------- v3.0.28.0 --------------------------------
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - -- async logging, v4 deadlock, 0x46 scan, packetSync and PCR_hunt_v3 mods --
    [2014-03-25 21:30:14,314] [66dcac0] [be0] -
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - CMpTsFilterPin::ctor
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - CMpOobSiFilterPin::ctor
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - PatParser::Reset
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - NIT:Reset
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - PatParser::Reset done
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - AtscNitParser: reset
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - AtscNitParser: reset done
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - LvctParser: reset
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - LvctParser: reset done
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - LvctParser: reset
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - LvctParser: reset done
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - NttParser: reset
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - NttParser: reset done
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - SvctParser: reset
    [2014-03-25 21:30:14,314] [66dcac0] [be0] - SvctParser: reset done
    [2014-03-25 21:30:14,315] [66dcac0] [be0] - LvctParser: reset
    [2014-03-25 21:30:14,315] [66dcac0] [be0] - LvctParser: reset done
    [2014-03-25 21:30:14,315] [66dcac0] [be0] - epg:ResetEPG()
    [2014-03-25 21:30:14,315] [66dcac0] [be0] - mhw ctor
    [2014-03-25 21:30:14,806] [66dcac0] [be0] - debug: AddChannel()
    [2014-03-25 21:30:14,806] [66dcac0] [be0] - analyzer: reset
    [2014-03-25 21:30:14,806] [66dcac0] [be0] - PatParser::Reset
    [2014-03-25 21:30:14,806] [66dcac0] [be0] - NIT:Reset
    [2014-03-25 21:30:14,806] [66dcac0] [be0] - PatParser::Reset done
    [2014-03-25 21:30:14,806] [66dcac0] [be0] - cagrabber: reset
    [2014-03-25 21:30:14,806] [66dcac0] [be0] - debug: done AddChannel()
    [2014-03-25 21:30:15,055] [66dcac0] [be0] - epg: reset
    [2014-03-25 21:30:15,055] [66dcac0] [be0] - epg:ResetEPG()
    [2014-03-25 21:30:15,055] [66dcac0] [be0] - mhw reset
    [2014-03-25 21:30:15,063] [66dcac0] [be0] - CMpTsFilter::pause()
    [2014-03-25 21:30:15,063] [66dcac0] [be0] - Pause filter...
    [2014-03-25 21:30:15,063] [66dcac0] [be0] - HRESULT = 0x0
    [2014-03-25 21:30:15,324] [66dcac0] [be0] - CMpTsFilter::Run()
    [2014-03-25 21:30:15,324] [66dcac0] [be0] - Run filter...
    [2014-03-25 21:30:15,324] [66dcac0] [be0] - HRESULT = 0x0
    [2014-03-25 21:30:15,358] [66dcac0] [be0] - pmtgrabber: set callback:600ff98
    [2014-03-25 21:30:15,358] [66dcac0] [be0] - pmtgrabber: grab pmt:189c sid:2b7a
    [2014-03-25 21:30:15,401] [66dcac0] [e78] - pmtgrabber: got pmt 189c sid:2b7a
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - pmtgrabber: PMT pids changed from:
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - pcr pid: 0
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - pmt pid: 0
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - pmtgrabber: PMT pids changed to:
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - pcr pid: 18a6
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - pmt pid: 189c
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - video pid: 18a6 type: H264
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - audio pid: 18b0 language: deu type: MPEG1 - audio
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - audio pid: 18b1 language: mis type: MPEG1 - audio
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - audio pid: 18b3 language: mul type: MPEG1 - audio
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - audio pid: 18b2 language: deu type: AC3
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - pmtgrabber: got new pmt version:4 ffffffff, service_id:2b7a
    [2014-03-25 21:30:15,402] [66dcac0] [e78] - pmtgrabber: do callback pid 189c
    [2014-03-25 21:30:15,413] [66dcac0] [be0] - analyzer: set video pid:18a6
    [2014-03-25 21:30:15,413] [66dcac0] [be0] - analyzer: reset
    [2014-03-25 21:30:15,413] [66dcac0] [be0] - analyzer: set audio pid:18b0
    [2014-03-25 21:30:15,413] [66dcac0] [be0] - analyzer: reset
    [2014-03-25 21:30:15,415] [66dcac0] [be0] - analyzer: set audio pid:18b2
    [2014-03-25 21:30:15,415] [66dcac0] [be0] - analyzer: reset
    [2014-03-25 21:30:15,789] [66dcac0] [be0] - Recorder: RECORD set filename:E:\recorder\Death in Paradise\Der Fluch des Piraten.ts
    [2014-03-25 21:30:15,790] [66dcac0] [be0] - Recorder: RECORD Received from TvService: pmt pid:0x189c serviceId: 0x2b7a pmtlength:120
    [2014-03-25 21:30:15,790] [66dcac0] [be0] - Recorder: RECORD Old pids cleared
    [2014-03-25 21:30:15,790] [66dcac0] [be0] - Recorder: RECORD got pmt - tableid: 0x2 section_length: 117 sid: 0x2b7a
    [2014-03-25 21:30:15,790] [66dcac0] [be0] - Recorder: RECORD PMT parsed - Pid 0x189c ServiceId 0x2b7a stream count: 7
    [2014-03-25 21:30:15,790] [66dcac0] [be0] - Recorder: RECORD pcr pid:0x18a6
    [2014-03-25 21:30:15,790] [66dcac0] [be0] - Recorder: RECORD SetPcrPid clear old PIDs
    [2014-03-25 21:30:15,791] [66dcac0] [be0] - Recorder: RECORD add video stream pid: 0x18a6 fake pid: 0x30 stream type: 0x1b logical type: 0x1b descriptor length: 3
    [2014-03-25 21:30:15,791] [66dcac0] [be0] - Recorder: RECORD add audio stream pid: 0x18b0 fake pid: 0x40 stream type: 0x3 logical type: 0x3 descriptor length: 9
    [2014-03-25 21:30:15,791] [66dcac0] [be0] - Recorder: RECORD add audio stream pid: 0x18b1 fake pid: 0x41 stream type: 0x3 logical type: 0x3 descriptor length: 16
    [2014-03-25 21:30:15,791] [66dcac0] [be0] - Recorder: RECORD add audio stream pid: 0x18b3 fake pid: 0x42 stream type: 0x3 logical type: 0x3 descriptor length: 9
    [2014-03-25 21:30:15,791] [66dcac0] [be0] - Recorder: RECORD add audio stream pid: 0x18b2 fake pid: 0x43 stream type: 0x6 logical type: 0x81 descriptor length: 14
    [2014-03-25 21:30:15,791] [66dcac0] [be0] - Recorder: RECORD add teletext stream pid: 0x18ba fake pid: 0x6e stream type: 0x6 logical type: 0x56 descriptor length: 10
    [2014-03-25 21:30:15,791] [66dcac0] [be0] - Recorder: RECORD stream rejected - pid: 0x181a stream type: 0x5 logical type: 0x5 descriptor length: 8
    [2014-03-25 21:30:15,791] [66dcac0] [be0] - Recorder: RECORD SetVideoAudioObserver observer ok
    [2014-03-25 21:30:15,792] [66dcac0] [be0] - Recorder: RECORD Start 'E:\recorder\Death in Paradise\Der Fluch des Piraten.ts'
    [2014-03-25 21:30:15,792] [66dcac0] [e78] - Recorder: RECORD start of audio detected
    [2014-03-25 21:30:15,798] [66dcac0] [e78] - Recorder: RECORD start of video detected
    [2014-03-25 21:30:15,828] [66dcac0] [e78] - Recorder: RECORD clear TS packet queue
    [2014-03-25 21:30:15,829] [66dcac0] [e78] - CDiskRecorder::WriteToRecording() - Reset write buffer throttle
    [2014-03-25 21:30:15,829] [66dcac0] [e78] - Recorder: RECORD Info : Next broadcaster program clock reference rollover : 0 days 00:14:24 0
    [2014-03-25 21:30:15,835] [66dcac0] [e78] - Recorder: RECORD start of audio detected
    [2014-03-25 21:30:15,872] [66dcac0] [e78] - Recorder: RECORD start of audio detected
    [2014-03-25 21:30:15,892] [66dcac0] [e78] - Recorder: RECORD start of audio detected
    [2014-03-25 21:31:32,794] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 9 ( prev 1 ) - bad signal?
    [2014-03-25 21:31:32,800] [66dcac0] [e78] - Recorder:pid 18b3 Continuity error... e ( prev c ) - bad signal?
    [2014-03-25 21:31:32,863] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 4 ( prev b ) - bad signal?
    [2014-03-25 21:31:32,870] [66dcac0] [e78] - Recorder:pid 18ba Continuity error... d ( prev b ) - bad signal?
    [2014-03-25 21:31:33,071] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... f ( prev 4 ) - bad signal?
    [2014-03-25 21:31:33,077] [66dcac0] [e78] - Recorder:pid 18b0 Continuity error... 5 ( prev 3 ) - bad signal?
    [2014-03-25 21:31:34,328] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... d ( prev 4 ) - bad signal?
    [2014-03-25 21:31:34,328] [66dcac0] [e78] - Recorder:pid 18ba Continuity error... 1 ( prev f ) - bad signal?
    [2014-03-25 21:31:34,328] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... c ( prev a ) - bad signal?
    [2014-03-25 21:31:34,900] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 5 ( prev b ) - bad signal?
    [2014-03-25 21:31:35,000] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 3 ( prev b ) - bad signal?
    [2014-03-25 21:31:36,112] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 8 ( prev 0 ) - bad signal?
    [2014-03-25 21:31:36,458] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 1 ( prev 9 ) - bad signal?
    [2014-03-25 21:31:36,458] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... 9 ( prev 7 ) - bad signal?
    [2014-03-25 21:31:37,319] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 7 ( prev 0 ) - bad signal?
    [2014-03-25 21:31:37,501] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 4 ( prev c ) - bad signal?
    [2014-03-25 21:31:37,564] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 5 ( prev d ) - bad signal?
    [2014-03-25 21:31:37,570] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... c ( prev a ) - bad signal?
    [2014-03-25 21:31:37,570] [66dcac0] [e78] - Recorder:pid 18ba Continuity error... d ( prev b ) - bad signal?
    [2014-03-25 21:31:37,639] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... f ( prev 7 ) - bad signal?
    [2014-03-25 21:31:37,639] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... 2 ( prev 0 ) - bad signal?
    [2014-03-25 21:31:37,664] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 4 ( prev d ) - bad signal?
    [2014-03-25 21:31:37,670] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... b ( prev 9 ) - bad signal?
    [2014-03-25 21:31:37,670] [66dcac0] [e78] - Recorder:pid 18b0 Continuity error... 9 ( prev 7 ) - bad signal?
    [2014-03-25 21:31:37,670] [66dcac0] [e78] - Recorder:pid 18b1 Continuity error... 8 ( prev 6 ) - bad signal?
    [2014-03-25 21:31:37,834] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 7 ( prev f ) - bad signal?
    [2014-03-25 21:31:37,834] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... d ( prev b ) - bad signal?
    [2014-03-25 21:31:37,834] [66dcac0] [e78] - Recorder:pid 18ba Continuity error... 2 ( prev 0 ) - bad signal?
    [2014-03-25 21:31:38,272] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... d ( prev 5 ) - bad signal?
    [2014-03-25 21:31:38,279] [66dcac0] [e78] - Recorder:pid 18b0 Continuity error... 3 ( prev 1 ) - bad signal?
    [2014-03-25 21:31:38,298] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... b ( prev 3 ) - bad signal?
    [2014-03-25 21:31:38,411] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 8 ( prev 0 ) - bad signal?
    [2014-03-25 21:31:38,858] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 6 ( prev e ) - bad signal?
    [2014-03-25 21:31:38,883] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... b ( prev c ) - bad signal?
    [2014-03-25 21:31:38,890] [66dcac0] [e78] - Recorder:pid 18b0 Continuity error... e ( prev c ) - bad signal?
    [2014-03-25 21:31:38,890] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... 0 ( prev e ) - bad signal?
    [2014-03-25 21:31:38,996] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... d ( prev 5 ) - bad signal?
    [2014-03-25 21:31:39,002] [66dcac0] [e78] - Recorder:pid 18b3 Continuity error... 9 ( prev 7 ) - bad signal?
    [2014-03-25 21:31:39,014] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... e ( prev 0 ) - bad signal?
    [2014-03-25 21:31:39,014] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... 7 ( prev 5 ) - bad signal?
    [2014-03-25 21:31:39,260] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... c ( prev 5 ) - bad signal?
    [2014-03-25 21:31:39,266] [66dcac0] [e78] - Recorder:pid 18b3 Continuity error... c ( prev a ) - bad signal?
    [2014-03-25 21:31:39,373] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 5 ( prev d ) - bad signal?
    [2014-03-25 21:31:39,373] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... 4 ( prev 2 ) - bad signal?
    [2014-03-25 21:31:39,373] [66dcac0] [e78] - Recorder:pid 18ba Continuity error... 5 ( prev 3 ) - bad signal?
    [2014-03-25 21:31:39,599] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 8 ( prev 0 ) - bad signal?
    [2014-03-25 21:31:39,863] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... a ( prev 3 ) - bad signal?
    [2014-03-25 21:31:40,127] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... b ( prev 4 ) - bad signal?
    [2014-03-25 21:31:40,127] [66dcac0] [e78] - Recorder:pid 18ba Continuity error... 7 ( prev 5 ) - bad signal?
    [2014-03-25 21:31:40,259] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 1 ( prev 9 ) - bad signal?
    [2014-03-25 21:31:40,460] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 5 ( prev d ) - bad signal?
    [2014-03-25 21:31:40,466] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... 3 ( prev 1 ) - bad signal?
    [2014-03-25 21:31:40,473] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 4 ( prev c ) - bad signal?
    [2014-03-25 21:31:40,523] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 5 ( prev d ) - bad signal?
    [2014-03-25 21:31:40,529] [66dcac0] [e78] - Recorder:pid 18ba Continuity error... 9 ( prev 7 ) - bad signal?
    [2014-03-25 21:31:40,542] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 4 ( prev d ) - bad signal?
    [2014-03-25 21:31:40,661] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... a ( prev 2 ) - bad signal?
    [2014-03-25 21:31:40,661] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... f ( prev d ) - bad signal?
    [2014-03-25 21:31:40,667] [66dcac0] [e78] - Recorder:pid 18b1 Continuity error... 7 ( prev 5 ) - bad signal?
    [2014-03-25 21:31:40,730] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... b ( prev 3 ) - bad signal?
    [2014-03-25 21:31:40,737] [66dcac0] [e78] - Recorder:pid 18b2 Continuity error... 6 ( prev 4 ) - bad signal?
    [2014-03-25 21:31:40,743] [66dcac0] [e78] - Recorder:pid 18b1 Continuity error... 1 ( prev f ) - bad signal?
    [2014-03-25 21:31:40,818] [66dcac0] [e78] - Recorder:pid 18a6 Continuity error... 1 ( prev 9 ) - bad signal?

    The signal itself was fine at this time - I viewed the program using my normal TV on a different SAT line.

    This all is very strange - can it be TSWriter is a bit extreme critical, now?

    I can't remember having those problem with 1.3 ... but I can be wrong.

    Meanwhile I removed all parasitic "APPS" from Win 8.1 and go on this way.

    If you have an idea what I can check in addition - let me know.

    For the moment I can say: it is not depending on the receiver card.

    best regards

    RUE
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Hello again Ruediger

    You said that the problem does not exist with MP 1.5 PR, but it exists with MP 1.5 final. Are you very sure about that...(?)... because the changes in TV Server between 1.5 PR and final are minimal. It would be much more likely that we introduced a problem in the PR (Tony, this was the TsWriter deadlock fix release)... but even then I'm not yet convinced this is a software problem.

    You asked for suggestions. A good test would be to see if the problem also occurs in other software.

    Aside from that, I can only go back to the basics.

    Causes of these sorts of problems are most commonly signal strength/quality related. Remember signal can be too strong as well as too weak. Are you 100% certain your signal quality is good? Have you tried taking out the multiswitch?

    If not signal then then HDD stress is the next most common.

    If not that, the cause could be much more exotic - overheating, OS/hardware power saving technologies, power supply in general, DPC latency (bad drivers)... things of that nature.

    One other thing to note:
    I viewed the program using my normal TV on a different SAT line.

    This does not mean that the signal will be okay for your PC tuners. Tuners have different specifications and characteristics. One tuner might be okay while another is really not "happy".

    mm
     

    Owlsroost

    Retired Team Member
  • Premium Supporter
  • October 28, 2008
    5,540
    5,038
    Cambridge
    Home Country
    United Kingdom United Kingdom
    It would be much more likely that we introduced a problem in the PR (Tony, this was the TsWriter deadlock fix release)...

    Yes, I had mused on that, but if there was a general problem we would have been snowed under with bug reports months ago....:)

    power saving technologies

    Good thought - we have had a few users report problems in the past (not always with TV Server) where dynamic power saving 'switching' has caused issues - might be worth taking a look at Windows power settings (but I wouldn't put this at the top of the list of things to try).
     

    Users who are viewing this thread

    Top Bottom