DTV2000DS Plus Works for a while then requires fresh install of OS (1 Viewer)

[Jason Broadhurst]

Hi all!

I have myself a fairly capable system including;
E8400 3Gig Core 2 Duo
HD5000 series Radeon(12.1 also tried latest)
4Gig of ram
DTV2000DS Plus dual capture card
Windows 8 x64 Pro


I have tried multiple times to get it working correctly and every time it starts out perfectly. I am able to record, watch and multi channel whatever I want. Both front end TV clients and back end work really well....

Then, a day will pass or the system will be idle for 4-24 hours and then the TV aspect is ruined. I can not watch a program without it skipping beyond recognition. It is like I have no aerial or signal at all. A restart fixed it a few times, but now restarting can not solve the problem. The TV aspect of MP is completely broken. I have tied a few different TV servers (nextPVR and winfast) and the same problems happens.

I have tried uninstalling drivers, programs, dot.net, directx and nothing fixes it until a fresh install of windows.

Has anyone got any ideas as to what may be happening? Any help would be appreciated, because if the lady friend misses another episode of home and away, I'll for certain be killed in my sleep and it made to look like an accident.

Cheers, Jase

 

[mm1352000]

Hello and welcome Jason

Could you please provide log files so we can try to analyse the cause/source of the problem?
1. Open TV Server configuration.
2. Click "open log directory" in the top left corner.
3. Zip up all the files you find there and post/attach the zip file here.

mm

 

[Jason Broadhurst]

Happily. BRB[DOUBLEPOST=1374066400][/DOUBLEPOST]There are some 84MB files.

Can I nuke them and start fresh and then upload the latest failed?

 

[mm1352000]

Sure.

 

[Jason Broadhurst]

Well that restart, nuking of the log files, stopping the service and restarting the service seemed to make everything ok.

Attached is the working log files.

I programmed my PC to reboot at 8:45 and recording of Home and Away started at 8:55.

The failed logs had TsWriter-2013-7-15, 16 and 17 at 50-80MB long. I can't upload them obviously, but they contained a recurring text simlar to this; This is common in all 3 days logs. I can assure you that there is suitable signal, as it works after a reboot some times and on the TV and LG DVR all the time.

17-07-2013 07:19:08.774 CMpTsFilter:ause()
17-07-2013 07:19:08.774 CMpTsFilter:top()
17-07-2013 08:55:08.628 CMpTs::ctor()
17-07-2013 08:55:08.628 --------------- BUG-3782 fix v2 -------------------
17-07-2013 08:55:08.628 CMpTsFilterPin:ctor
17-07-2013 08:55:08.628 PatParser:Reset(0)
17-07-2013 08:55:08.628 NIT:Reset
17-07-2013 08:55:08.628 PatParser::Reset done
17-07-2013 08:55:08.628 epg:ResetEPG()
17-07-2013 08:55:08.628 mhw ctor
17-07-2013 08:55:08.858 analyzer: reset
17-07-2013 08:55:08.858 PatParser:Reset(0)
17-07-2013 08:55:08.858 NIT:Reset
17-07-2013 08:55:08.858 PatParser::Reset done
17-07-2013 08:55:08.858 cagrabber: reset
17-07-2013 08:55:08.863 epg: reset
17-07-2013 08:55:08.863 epg:ResetEPG()
17-07-2013 08:55:08.863 mhw reset
17-07-2013 08:55:08.888 CMpTsFilter:ause()
17-07-2013 08:55:11.963 CMpTsFilter::Run()
17-07-2013 08:55:11.998 pmtgrabber: set callback:3c80038
17-07-2013 08:55:11.998 pmtgrabber: grab pmt:420 sid:542
17-07-2013 08:55:13.283 pmtgrabber: got pmt 420 sid:542
17-07-2013 08:55:13.283 pmtgrabber: PMT pids changed from:
17-07-2013 08:55:13.283 pcr pid: 0
17-07-2013 08:55:13.283 pmt pid: 0
17-07-2013 08:55:13.283 pmtgrabber: PMT pids changed to:
17-07-2013 08:55:13.283 pcr pid: 421
17-07-2013 08:55:13.283 pmt pid: 420
17-07-2013 08:55:13.283 video pid: 421 type: M
17-07-2013 08:55:13.283 audio pid: 422 language: eng type: M
17-07-2013 08:55:13.283 pmtgrabber: got new pmt version:6 ffffffff, service_id:542
17-07-2013 08:55:13.283 pmtgrabber: do callback pid 420
17-07-2013 08:55:13.303 analyzer: set video pid:421
17-07-2013 08:55:13.303 analyzer: reset
17-07-2013 08:55:13.303 analyzer: set audio pid:422
17-07-2013 08:55:13.303 analyzer: reset
17-07-2013 08:55:13.378 Recorder: RECORD set filename:C:\Users\Jason\Videos\Home and Away - The Early Years\Home and Away - The Early Years - 2013-07-17.ts
17-07-2013 08:55:13.378 Recorder: RECORD Received from TvService: pmt pid:0x420 serviceId: 0x542 pmtlength:72
17-07-2013 08:55:13.378 Recorder: RECORD Old pids cleared
17-07-2013 08:55:13.378 Recorder: RECORD got pmt - tableid: 0x2 section_length: 69 sid: 0x542
17-07-2013 08:55:13.378 Recorder: RECORD PMT parsed - Pid 0x420 ServiceId 0x542 stream count: 4
17-07-2013 08:55:13.378 Recorder: RECORD pcr pid:0x421
17-07-2013 08:55:13.378 Recorder: RECORD SetPcrPid clear old PIDs
17-07-2013 08:55:13.378 Recorder: RECORD add video stream pid: 0x421 fake pid: 0x30 stream type: 0x2 logical type: 0x2 descriptor length: 5
17-07-2013 08:55:13.378 Recorder: RECORD add audio stream pid: 0x422 fake pid: 0x40 stream type: 0x3 logical type: 0x3 descriptor length: 6
17-07-2013 08:55:13.378 Recorder: RECORD add teletext stream pid: 0x424 fake pid: 0x60 stream type: 0x6 logical type: 0x56 descriptor length: 7
17-07-2013 08:55:13.378 Recorder: RECORD stream rejected - pid: 0x499 stream type: 0xb logical type: 0xb descriptor length: 18
17-07-2013 08:55:13.378 Recorder: RECORD SetVideoAudioObserver observer ok
17-07-2013 08:55:13.378 Recorder: RECORD Start 'C:\Users\Jason\Videos\Home and Away - The Early Years\Home and Away - The Early Years - 2013-07-17.ts'
17-07-2013 08:55:13.413 Recorderid 421 Continuity error... 2 ( prev c ) - bad signal?
17-07-2013 08:55:13.413 Recorderid 422 Continuity error... 4 ( prev 2 ) - bad signal?
17-07-2013 08:55:13.413 Recorderid 421 Continuity error... 8 ( prev 1 ) - bad signal?
17-07-2013 08:55:13.413 Recorderid 422 Continuity error... 7 ( prev 5 ) - bad signal?
17-07-2013 08:55:13.413 Recorderid 421 Continuity error... 0 ( prev 9 ) - bad signal?
17-07-2013 08:55:13.413 Recorderid 421 Continuity error... d ( prev 0 ) - bad signal?
17-07-2013 08:55:13.413 Recorderid 422 Continuity error... 9 ( prev 7 ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 421 Continuity error... 2 ( prev b ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 421 Continuity error... c ( prev 3 ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 422 Continuity error... c ( prev a ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 421 Continuity error... a ( prev 7 ) - bad signal?
17-07-2013 08:55:13.418 Recorder: RECORD start of video detected
17-07-2013 08:55:13.418 Recorderid 422 Continuity error... f ( prev d ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 422 Continuity error... 1 ( prev f ) - bad signal?
17-07-2013 08:55:13.418 Recorder: RECORD clear TS packet queue
17-07-2013 08:55:13.418 CDiskRecorder::WriteToRecording() - Reset write buffer throttle
17-07-2013 08:55:13.418 Recorder: RECORD Info : Next broadcaster program clock reference rollover : 0 days 20:29:56 0
17-07-2013 08:55:13.418 Recorderid 421 Continuity error... c ( prev 4 ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 421 Continuity error... a ( prev c ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 422 Continuity error... 4 ( prev 2 ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 421 Continuity error... e ( prev 6 ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 421 Continuity error... d ( prev e ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 422 Continuity error... 7 ( prev 4 ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 424 Continuity error... e ( prev c ) - bad signal?
17-07-2013 08:55:13.418 Recorderid 421 Continuity error... 4 ( prev d ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 422 Continuity error... 9 ( prev 7 ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... f ( prev 9 ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... 8 ( prev 6 ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... a ( prev f ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 422 Continuity error... c ( prev 9 ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... 5 ( prev f ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... 9 ( prev 7 ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... c ( prev 9 ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 422 Continuity error... e ( prev c ) - bad signal?
17-07-2013 08:55:13.558 Recorder: RECORD start of audio detected
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... b ( prev 9 ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... c ( prev 6 ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... d ( prev d ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 422 Continuity error... 1 ( prev f ) - bad signal?
17-07-2013 08:55:13.558 Recorderid 421 Continuity error... f ( prev 4 ) - bad signal?

 

[mm1352000]

Well that restart, nuking of the log files, stopping the service and restarting the service seemed to make everything ok.

Heh, its funny how that happens sometimes.


The continuity error messages that you have shown in the excerpt of the TsWriter log usually indicate one of three things:

1. Signal strength/quality issues.
2. Timeshift/record HDD load issues.
3. Overheating hardware.

You've said that you're convinced the first problem doesn't apply. I note that the readings of 55 strength and 100 quality in the log files and your reference to the other devices. Now, I'm not saying you're wrong... however, I would caution you to consider that sensitivity, susceptibility to noise/interference, ideal operating signal and many other factors can and do vary from device to device. Just because signal is adequate for one device does not mean it will be adequate for others, and that particularly applies when comparing PC tuners with other TV receivers. Again, I'm not saying that your signal is no good - just saying don't dismiss it as a possibility out of hand based on the evidence you quoted to me.

Re. the second point: check that your HDD is not working like a mad thing when you try and watch or record TV. If the HDD is working hard, ensure that any virus and spyware scanners that you've installed are not scanning the MediaPortal program, setting, timeshift or record folders. MS Security Essentials seems to be very adept at causing havok with MP.

The third possibility (overheating) is less common. Nevertheless, it pays to consider whether your PC case has enough airflow.

Hope that helps,
mm

 

[Jason Broadhurst]

Thanks for the sanity check. Perhaps getting on the roof and ensuring my aerial is pointing as best it can may help.

HDD usage should be fairly small. I run no virus scanner, bitdeffender and all the other MS bloatware is turned off. Taskmanager shows low HDD usage during recoding, good or bad.

Overheating - due to my continual dramas, the PC is as much disassembled as it could get, and isn't working on 18 degree well ventilated days. I saw a spike of 58 degree HDD and max 47 CPU or GPU

I will check the aerial ASAP.[DOUBLEPOST=1374069112][/DOUBLEPOST]If it helps, the DTV2000DS Plus is a dual USB tuner card, attached to a VIA USB/PCI bridge. meaning, it is a bit of a hack job as it runs through an onboard pci/usb adapter to get to the tuner cards. Just a bit of background.

 

[Owlsroost]

I have tied a few different TV servers (nextPVR and winfast) and the same problems happens.

I think I'd buy a cheap USB DVB-T tuner dongle and try that - the ones based around the AF9015/AF9013 chipset are generally very reliable and cheap. The IT9135/IT9137 appears to be a more modern (replacement ?) chipset from the same supplier, but I've no personal experience with it. If you want to find out what chipset is inside, here is a good start - http://www.linuxtv.org/wiki/index.php/DVB-T_Devices (the DTV2000DS Plus uses an RTL2832 chipset, according to that).