NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public Add-ons (3rd party plugins, utilities and skins) Old Stuff (Legacy) GB-PVR Support (legacy) v
« Previous 1 … 571 572 573 574 575 … 1231 Next »
screwed up recordings

 
  • 0 Vote(s) - 0 Average
screwed up recordings
stefan
Offline

Posting Freak

Posts: 3,116
Threads: 81
Joined: Oct 2004
#1
2007-03-25, 08:10 PM (This post was last modified: 2007-03-25, 08:17 PM by stefan.)
Sometimes I get really screwed up recordings from my dvb-t tuner. The recordings are virtually unwatchable. The weird part is that the sound is usually ok. It's the image that is studdering really bad. Maybe something like 1 frame per second, like still images going by. But the sound is ok, like I said. GBPVR is logging "checking signal status on..." If it were a signal issue, would gbpvr indicate that in the logs?

From recordingservice.exe.log for one of those bad recordings:
Code:
2007-03-23 22:24:00.169 INFO [5] Found new programme requiring recording: Let's dance 2007-03-23 22:24:00.184 VERBOSE [5] Changing to channel (GBPVR.Backend.Common.NullTunerController): 3 2007-03-23 22:24:00.184 VERBOSE [5] Requesting IRecordingSource to start recording: C:\inspelat\Lets dance\Lets dance_20070323_22252240.mpg 2007-03-23 22:24:00.184 VERBOSE [5] BDARecordingSource about to start recording oid:1 channel:T:C45,666000,0,0,8~NID:12660~ONID:8945~TSID:1022~P:6110~V:1049~A:1048~L:000~PMT:6110~LCN:4~TXT:1046~N:>TV4 Stockholm 2007-03-23 22:24:02.497 VERBOSE [5] Programme is now recording 2007-03-23 22:24:02.497 VERBOSE [5] RecordingFactory.save() 2007-03-23 22:24:02.684 VERBOSE [5] Save(): Updated existing scheduled recording 2007-03-23 22:24:02.684 VERBOSE [5] Adding C:\inspelat\Lets dance\Lets dance_20070323_22252240.mpg to parallel processing queue 2007-03-23 22:24:02.684 VERBOSE [5] RecordingFactory.getExtrasForGroup(36) 2007-03-23 22:24:32.575 VERBOSE [5] Checking signal status on Hauppauge Nova-T USB2:1 2007-03-23 22:25:02.763 VERBOSE [5] Checking signal status on Hauppauge Nova-T USB2:1[snip] 2007-03-23 22:42:07.966 VERBOSE [5] Checking signal status on Hauppauge Nova-T USB2:1 2007-03-23 22:42:38.153 VERBOSE [5] Checking signal status on Hauppauge Nova-T USB2:1 2007-03-23 22:43:00.028 VERBOSE [5] Recording has passed endtime+padding. Stopping. 2007-03-23 22:43:00.028 VERBOSE [5] Stopping recording oid:1 2007-03-23 22:43:00.309 VERBOSE [5] Adding C:\inspelat\Lets dance\Lets dance_20070323_22252240.mpg to commercial detection queue 2007-03-23 22:43:00.309 VERBOSE [5] Not adding C:\inspelat\Lets dance\Lets dance_20070323_22252240.mpg to conversion detection queue. Conversions are currently disabled. 2007-03-23 22:43:00.309 VERBOSE [5] RecordingStatus is now RecordingStatus.RECORDING_COMPETED 2007-03-23 22:43:00.309 VERBOSE [5] RecordingFactory.save() 2007-03-23 22:43:00.403 VERBOSE [5] Save(): Updated existing scheduled recording

This is the corresponding part in recordingservice-native log:
Code:
22:24:00.015 VERBOSE getSetting(BDADisableStatusChecks) 22:24:00.015 INFO BDARecorder:::StartRecording(Hauppauge Nova-T USB2, 1, C:\inspelat\Lets dance\Lets dance_20070316_22252240.mpg, T:C45,666000,0,0,8~NID:12660~ONID:8945~TSID:1022~P:6110~V:1049~A:1048~L:000~PMT:6110~LCN:4~TXT:1046~N:>TV4 Stockholm) 22:24:00.046 INFO Initializing DVB-T tuning request. 22:24:00.046 INFO tuning@1 22:24:00.046 INFO tuning@2 22:24:00.046 INFO tuning@3 22:24:00.046 INFO tuning@4 22:24:00.046 INFO tuning@5 22:24:00.046 INFO tuning@8 22:24:00.046 VERBOSE SubmitTuningRequest(T:C45,666000,0,0,8~NID:12660~ONID:8945~TSID:1022~P:6110~V:1049~A:1048~L:000~PMT:6110~LCN:4~TXT:1046~N:>TV4 Stockholm) 22:24:00.046 INFO Submit-DVBT@T1 22:24:00.046 VERBOSE Preparing Tuning Request 22:24:00.046 INFO Submit-DVBT@T2 22:24:00.046 INFO Submit-DVBT@T3 22:24:00.046 INFO Submit-DVBT@T4 22:24:00.046 VERBOSE New tuning request submitted... 22:24:00.046 INFO Submit-DVBT@T5 22:24:00.046 VERBOSE Getting current tuning request... 22:24:00.546 VERBOSE Current CarrierFrequency=666000 22:24:00.546 VERBOSE ServiceID: 6110, PMT PID: 6110, VPID: 1049, APID: 1048 22:24:00.546 VERBOSE SubmitTuningRequest() complete 22:24:00.546 VERBOSE ServiceID: 6110, PMT PID: 6110, VPID: 1049, APID: 1048 22:24:00.546 VERBOSE getSetting(BDAMultiplexer) 22:24:00.546 VERBOSE Preferred BDA Multiplexer: CyberLink 22:24:00.546 VERBOSE getSetting(BDAEnabledMDPlugins) 22:24:00.546 VERBOSE Enabling MDAPI 22:24:00.703 VERBOSE reusing MDAPI Filter 22:24:00.703 VERBOSE Demux filter has the following default output pins: 22:24:00.703 VERBOSE - 1: has media type: {455F176C-4B06-47CE-9AEF-8CAEF73DF7B5} {E9DD31A3-221D-4ADB-8532-9AF309C1A408} 22:24:00.703 VERBOSE - 2: has media type: {73646976-0000-0010-8000-00AA00389B71} {E06D8026-DB46-11CF-B4D1-00805F6CBBEA} (VIDEO) 22:24:00.703 VERBOSE - 3: has media type: {73647561-0000-0010-8000-00AA00389B71} {E06D802B-DB46-11CF-B4D1-00805F6CBBEA} (AUDIO) 22:24:00.703 VERBOSE - 4: has media type: {455F176C-4B06-47CE-9AEF-8CAEF73DF7B5} {E436EB8E-524F-11CE-9F53-0020AF0BA770} 22:24:00.703 VERBOSE - 5: has media type: {455F176C-4B06-47CE-9AEF-8CAEF73DF7B5} {C892E55B-252D-42B5-A316-D997E7A5D995} 22:24:00.703 VERBOSE getSetting(BDAUsePsiParser) 22:24:00.703 VERBOSE getSetting(BDAEnableDvbSubtitles) 22:24:00.703 VERBOSE getSetting(EPGProcessingMode) 22:24:00.812 VERBOSE getSetting(BDAAutoMapPids) 22:24:00.828 VERBOSE FindFilterByName failed to locate filter: GB-PVR DVB Subtitles 22:24:00.828 VERBOSE Creating MPEG-2 Video pin mapped to PID 1049 22:24:00.828 VERBOSE ConnectPins: 'Video' to 'Input' 22:24:00.828 VERBOSE Creating Audio pin mapped to PID 1048 (MPEG1 Layer 2) 22:24:00.828 VERBOSE getSetting(EnableTeleText) 22:24:00.828 VERBOSE Mapping Teletext PID 1046 22:24:00.828 VERBOSE FindFilterByName failed to locate filter: GB-PVR WST SRT Digital 22:24:00.828 VERBOSE hwnd = NULL 22:24:00.828 VERBOSE previewMode = false 22:24:00.828 VERBOSE About to connect recording graph to mux 22:24:00.843 VERBOSE Setting IID_IMpgMuxer 22:24:00.843 VERBOSE Initialzing Cyberlink mux for MPEG2 program stream 22:24:00.843 VERBOSE Setting IID_IMpgMuxer3 22:24:00.843 VERBOSE Setting IID_IMpgMuxerInfo 22:24:00.843 VERBOSE Finished initialzing Cyberlink mux 22:24:00.843 VERBOSE ConnectPins: 'Output' to 'Video In' 22:24:00.843 VERBOSE ConnectPins: 'Audio' to 'Audio In' 22:24:00.843 VERBOSE ConnectPins: 'Output' to 'Input' 22:24:00.843 VERBOSE getSetting(BDAAlwaysAddTIFAndSections) 22:24:00.875 VERBOSE getSetting(BDASubmitTuningRequestTwiceOnRecord) 22:24:00.875 INFO Starting graph... 22:24:02.140 VERBOSE locked=1 present=1 strength=21 quality=60 22:24:02.140 VERBOSE getSetting(ListGraphFilters) 22:24:02.140 VERBOSE Graph contains the following filters: 22:24:02.140 VERBOSE - BDA MPEG2 Transport Information Filter 22:24:02.140 VERBOSE - MPEG-2 Sections and Tables 22:24:02.140 VERBOSE - GB-PVR Writer 22:24:02.140 VERBOSE - GB-PVR PSI Parser 22:24:02.156 VERBOSE - CyberLink MPEG Muxer 22:24:02.156 VERBOSE - GB-PVR Flow Status 22:24:02.156 VERBOSE - MPEG-2 Demultiplexer 22:24:02.156 VERBOSE - MDAPI Filter 22:24:02.156 VERBOSE - Hauppauge Nova USB2 DVB-T TV Receiver 22:24:02.156 VERBOSE - Microsoft DVBT Network Provider 22:24:02.156 VERBOSE getSetting(SaveGraphFiles) 22:24:02.250 VERBOSE Demux filter has the following default output pins: 22:24:02.250 VERBOSE - 1: has media type: {455F176C-4B06-47CE-9AEF-8CAEF73DF7B5} {E9DD31A3-221D-4ADB-8532-9AF309C1A408} 22:24:02.250 VERBOSE PID: 0 (0) 22:24:02.250 VERBOSE PID: 16 (10) 22:24:02.250 VERBOSE PID: 17 (11) 22:24:02.250 VERBOSE PID: 18 (12) 22:24:02.250 VERBOSE PID: 19 (13) 22:24:02.250 VERBOSE PID: 20 (14) 22:24:02.250 VERBOSE PID: 1070 (42E) 22:24:02.250 VERBOSE PID: 1130 (46A) 22:24:02.250 VERBOSE PID: 1140 (474) 22:24:02.250 VERBOSE PID: 1150 (47E) 22:24:02.250 VERBOSE PID: 1160 (488) 22:24:02.250 VERBOSE PID: 1220 (4C4) 22:24:02.250 VERBOSE PID: 1810 (712) 22:24:02.250 VERBOSE PID: 6110 (17DE) 22:24:02.250 VERBOSE - 5: has media type: {455F176C-4B06-47CE-9AEF-8CAEF73DF7B5} {C892E55B-252D-42B5-A316-D997E7A5D995} 22:24:02.250 VERBOSE - Audio: has media type: {73647561-0000-0010-8000-00AA00389B71} {00000050-0000-0010-8000-00AA00389B71} (AUDIO) 22:24:02.250 VERBOSE PID: 1048 (418) 22:24:02.250 VERBOSE - DVBTeletext: has media type: {455F176C-4B06-47CE-9AEF-8CAEF73DF7B5} {00000000-0000-0000-0000-000000000000} 22:24:02.250 VERBOSE PID: 1046 (416) 22:24:02.250 VERBOSE - PSI: has media type: {455F176C-4B06-47CE-9AEF-8CAEF73DF7B5} {00000000-0000-0000-0000-000000000000} 22:24:02.250 VERBOSE PID: 0 (0) 22:24:02.250 VERBOSE PID: 1 (1) 22:24:02.250 VERBOSE PID: 16 (10) 22:24:02.250 VERBOSE PID: 17 (11) 22:24:02.250 VERBOSE PID: 18 (12) 22:24:02.250 VERBOSE PID: 6110 (17DE) 22:24:02.250 VERBOSE - Video: has media type: {73646976-0000-0010-8000-00AA00389B71} {E06D8026-DB46-11CF-B4D1-00805F6CBBEA} (VIDEO) 22:24:02.250 VERBOSE PID: 1049 (419) 22:24:02.250 VERBOSE BDARecorder::StartRecording() finished 22:24:32.281 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:25:02.453 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:25:32.500 VERBOSE checking signal stats took total: 0ms (1,1,21,100).....(,0,0,0) [snip] 22:42:36.875 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:43:00.109 VERBOSE BDARecorder::StopRecording() 22:43:00.343 VERBOSE BDARecorder::StopRecording() finished

I tried switching to dvr-ms mux, but that made no difference. I still get these recordings from time to time. Usually it's the entire recording that goes bad, or the entire recording is just fine. Occasionally, however, it goes bad somewhere in the middle of it. I have never seen one being bad in the beginning, and then becoming good in the end.

Any ideas? By the way, I was not using the computer for anything else at the moment, and I don't think it was doing anything special. But I'm not sure.
I'm not always right
GB-PVR 1.2.9
Accent HT-400 Case, AMD Athlon 64 3800+ 1024MB, 1TB+300GB+180GB, WinXP Pro-SP2, NVidia 7600GT
Nova-T USB2, PVR-350 recording from Dilog 355 DVB-T box, USB-UIRT (receiving & transmitting)
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 108,494
Threads: 784
Joined: Nov 2003
#2
2007-03-25, 08:19 PM
Did the checking signal (1,1,21,100) numbers change during the recording?

Unfortunately all the manufacturers use their own differing scales for measuring signal strength/quality, so I cant really tell if this is a good or poor signal.
stefan
Offline

Posting Freak

Posts: 3,116
Threads: 81
Joined: Oct 2004
#3
2007-03-25, 08:22 PM
A little. Is the last number percentage?

Code:
22:24:32.281 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:25:02.453 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:25:32.500 VERBOSE checking signal stats took total: 0ms (1,1,21,100).....(,0,0,0) 22:26:02.671 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:26:32.843 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:27:02.906 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:27:33.062 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:28:03.125 VERBOSE checking signal stats took total: 16ms (1,1,21,80).....(,0,0,0) 22:28:33.281 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:29:03.453 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:29:33.515 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:30:03.687 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:30:33.843 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:31:03.906 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:31:34.078 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:32:04.250 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:32:34.312 VERBOSE checking signal stats took total: 15ms (1,1,21,80).....(,0,0,0) 22:33:04.484 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:33:34.640 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:34:04.703 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:34:34.859 VERBOSE checking signal stats took total: 0ms (1,1,21,100).....(,0,0,0) 22:35:04.937 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:35:35.078 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:36:05.234 VERBOSE checking signal stats took total: 16ms (1,1,21,90).....(,0,0,0) 22:36:35.296 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:37:05.468 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:37:35.515 VERBOSE checking signal stats took total: 0ms (1,1,21,100).....(,0,0,0) 22:38:05.671 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:38:35.859 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:39:06.046 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:39:36.109 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:40:06.265 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:40:36.437 VERBOSE checking signal stats took total: 15ms (1,1,21,100).....(,0,0,0) 22:41:06.500 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:41:36.656 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0) 22:42:06.718 VERBOSE checking signal stats took total: 15ms (1,1,21,90).....(,0,0,0) 22:42:36.875 VERBOSE checking signal stats took total: 16ms (1,1,21,100).....(,0,0,0)
I'm not always right
GB-PVR 1.2.9
Accent HT-400 Case, AMD Athlon 64 3800+ 1024MB, 1TB+300GB+180GB, WinXP Pro-SP2, NVidia 7600GT
Nova-T USB2, PVR-350 recording from Dilog 355 DVB-T box, USB-UIRT (receiving & transmitting)
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 108,494
Threads: 784
Joined: Nov 2003
#4
2007-03-25, 08:25 PM
Quote:Is the last number percentage?
Maybe.

'21' is the signal strength, but I can tell you what it represents.
stefan
Offline

Posting Freak

Posts: 3,116
Threads: 81
Joined: Oct 2004
#5
2007-03-25, 08:28 PM
But still, 80 percent of full reception should be ok. And the entire recording is screwed up, even when it was 100 in the beginning. Leads me to believe it's something in my computer (hardware or software) rather than signal issue...
I'm not always right
GB-PVR 1.2.9
Accent HT-400 Case, AMD Athlon 64 3800+ 1024MB, 1TB+300GB+180GB, WinXP Pro-SP2, NVidia 7600GT
Nova-T USB2, PVR-350 recording from Dilog 355 DVB-T box, USB-UIRT (receiving & transmitting)
stefan
Offline

Posting Freak

Posts: 3,116
Threads: 81
Joined: Oct 2004
#6
2007-03-25, 08:32 PM
sub Wrote:Maybe.

'21' is the signal strength, but I can tell you what it represents.
Ah, ok. Higher being better, I'd assume? I got this for the recording just before it, which was fine all the way through:
Code:
20:29:32.403 VERBOSE checking signal stats took total: 16ms (1,1,18,80).....(,0,0,0) 20:30:02.575 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 20:30:32.638 VERBOSE checking signal stats took total: 15ms (1,1,19,60).....(,0,0,0) 20:31:02.809 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 20:31:32.966 VERBOSE checking signal stats took total: 15ms (1,1,18,60).....(,0,0,0) 20:32:03.028 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:32:33.200 VERBOSE checking signal stats took total: 16ms (1,1,18,80).....(,0,0,0) 20:33:03.356 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 20:33:33.419 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 20:34:03.575 VERBOSE checking signal stats took total: 0ms (1,1,19,60).....(,0,0,0) 20:34:33.653 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 20:35:03.809 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 20:35:33.966 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 20:36:04.028 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:36:34.200 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 20:37:04.372 VERBOSE checking signal stats took total: 32ms (1,1,19,80).....(,0,0,0) 20:37:34.434 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:38:04.591 VERBOSE checking signal stats took total: 15ms (1,1,18,60).....(,0,0,0) 20:38:34.669 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 20:39:04.809 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:39:34.966 VERBOSE checking signal stats took total: 0ms (1,1,19,60).....(,0,0,0) 20:40:05.028 VERBOSE checking signal stats took total: 0ms (1,1,19,60).....(,0,0,0) 20:40:35.200 VERBOSE checking signal stats took total: 16ms (1,1,18,60).....(,0,0,0) 20:41:05.372 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:41:35.419 VERBOSE checking signal stats took total: 0ms (1,1,19,60).....(,0,0,0) 20:42:05.591 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 20:42:35.747 VERBOSE checking signal stats took total: 16ms (1,1,18,60).....(,0,0,0) 20:43:05.809 VERBOSE checking signal stats took total: 0ms (1,1,19,100).....(,0,0,0) 20:43:35.981 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 20:44:06.044 VERBOSE checking signal stats took total: 15ms (1,1,19,90).....(,0,0,0) 20:44:36.200 VERBOSE checking signal stats took total: 16ms (1,1,18,60).....(,0,0,0) 20:45:06.372 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:45:36.434 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:46:06.606 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 20:46:36.778 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:47:06.825 VERBOSE checking signal stats took total: 0ms (1,1,19,80).....(,0,0,0) 20:47:36.997 VERBOSE checking signal stats took total: 16ms (1,1,18,60).....(,0,0,0) 20:48:07.153 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:48:37.231 VERBOSE checking signal stats took total: 16ms (1,1,18,60).....(,0,0,0) 20:49:07.388 VERBOSE checking signal stats took total: 0ms (1,1,19,100).....(,0,0,0) 20:49:37.559 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:50:07.622 VERBOSE checking signal stats took total: 16ms (1,1,18,60).....(,0,0,0) 20:50:37.778 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:51:07.841 VERBOSE checking signal stats took total: 15ms (1,1,19,60).....(,0,0,0) 20:51:38.013 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 20:52:08.169 VERBOSE checking signal stats took total: 0ms (1,1,19,80).....(,0,0,0) 20:52:38.231 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:53:08.403 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:53:38.559 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:54:08.622 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:54:38.794 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 20:55:08.966 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 20:55:39.028 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 20:56:09.184 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:56:39.372 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:57:09.434 VERBOSE checking signal stats took total: 0ms (1,1,19,90).....(,0,0,0) 20:57:39.622 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 20:58:09.778 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 20:58:39.856 VERBOSE checking signal stats took total: 31ms (1,1,19,80).....(,0,0,0) 20:59:10.013 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 20:59:40.169 VERBOSE checking signal stats took total: 15ms (1,1,19,80).....(,0,0,0) 21:00:10.247 VERBOSE checking signal stats took total: 16ms (1,1,19,90).....(,0,0,0) 21:00:40.403 VERBOSE checking signal stats took total: 0ms (1,1,19,90).....(,0,0,0) 21:01:10.575 VERBOSE checking signal stats took total: 16ms (1,1,19,60).....(,0,0,0) 21:01:40.638 VERBOSE checking signal stats took total: 15ms (1,1,18,80).....(,0,0,0) 21:02:10.809 VERBOSE checking signal stats took total: 16ms (1,1,19,80).....(,0,0,0) 21:02:40.966 VERBOSE checking signal stats took total: 15ms (1,1,18,80).....(,0,0,0)
I'm not always right
GB-PVR 1.2.9
Accent HT-400 Case, AMD Athlon 64 3800+ 1024MB, 1TB+300GB+180GB, WinXP Pro-SP2, NVidia 7600GT
Nova-T USB2, PVR-350 recording from Dilog 355 DVB-T box, USB-UIRT (receiving & transmitting)
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 108,494
Threads: 784
Joined: Nov 2003
#7
2007-03-25, 08:33 PM
I'm not really sure what to suggest. If its not the mux, I'd have to guess the device itself is having problems delivering the packets.

If you're using multidec, then it could also be a factor.
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 108,494
Threads: 784
Joined: Nov 2003
#8
2007-03-25, 08:35 PM
stefan Wrote:Ah, ok. Higher being better, I'd assume?
I dont know with this device. Some report -44000 or -4000 or 64 or 100 when they have a really good signal. I've not seen a device using a number in that range, but if it normally works, then I guess it represents an ok strength?
stefan
Offline

Posting Freak

Posts: 3,116
Threads: 81
Joined: Oct 2004
#9
2007-03-25, 08:35 PM
Nah, I haven't dared going to multidec yet because of this issue. Would like to solve it first. It seems to have become worse lately, though, so maybe the device is going poofed. I'll poke around a bit more. Thank's so far, though.
I'm not always right
GB-PVR 1.2.9
Accent HT-400 Case, AMD Athlon 64 3800+ 1024MB, 1TB+300GB+180GB, WinXP Pro-SP2, NVidia 7600GT
Nova-T USB2, PVR-350 recording from Dilog 355 DVB-T box, USB-UIRT (receiving & transmitting)
stefan
Offline

Posting Freak

Posts: 3,116
Threads: 81
Joined: Oct 2004
#10
2007-03-26, 09:06 PM
I did some more digging. Half an hour ago my computer started doing a defrag all by itself. I can't for the life of me figure out why. I'm hoping that's what's causing it, though. I can see why it would interfere with recordings. Some checking on the net tells me that more people have a problem with dfrgntfs.exe running by itself. Nothing scheduled. Someone suggested "allow indexing of this disk" caused it, and others said changing a registry key could turn the automatic junk off. I just tried both. Time will tell if it works Smile
I'm not always right
GB-PVR 1.2.9
Accent HT-400 Case, AMD Athlon 64 3800+ 1024MB, 1TB+300GB+180GB, WinXP Pro-SP2, NVidia 7600GT
Nova-T USB2, PVR-350 recording from Dilog 355 DVB-T box, USB-UIRT (receiving & transmitting)
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)

Pages (2): 1 2 Next »


Possibly Related Threads…
Thread Author Replies Views Last Post
  Live TV and recordings do not match greg in kansas 8 8,452 2013-02-22, 06:35 PM
Last Post: sub
  Can't view recordings on pc jerry430 8 8,437 2013-01-21, 07:27 PM
Last Post: jerry430
  Live TV not showing anything although recordings are OK. Pls advise. seymoria 8 6,383 2012-08-07, 05:07 PM
Last Post: ACTCMS
  CSI Miami Recordings Always In Spanish ga_mueller 6 5,798 2012-06-12, 12:41 AM
Last Post: mikeh49
  Recordings missing after switching hard drive tegat 8 6,564 2011-12-21, 03:00 AM
Last Post: tegat
  Recordings and live TV fail with TS mux dvasco 4 3,676 2011-06-22, 05:47 PM
Last Post: dvasco
  Stream errors in recordings with GBPVR seymoria 11 6,041 2011-06-19, 06:44 PM
Last Post: seymoria
  Lost all my recordings pduncan67 2 2,726 2011-02-27, 03:12 PM
Last Post: pduncan67
  Zero byte recordings chuck_2330 0 1,898 2011-02-09, 01:25 PM
Last Post: chuck_2330
  Black screen when playing back recordings gonzo90017 1 2,314 2011-01-19, 06:12 PM
Last Post: gonzo90017

  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode