Hi,
OK, my gbpvr installation is ALMOST working now. Only problem left now is that whenever I restart my machine, or reconnect my PVR USB2 device, then the video renderer in gbpvr somehow goes for a toss.
The sound is ok, but the display is all hazy and if the last frame is mixed with the current frame. Now, if i just close gbpvr, and start the standard WinTV 2000 application, then I see perfect TV in WinTV. Now, when I close WinTV and restart GBPVR's Live TV, I see perfect TV in GBPVR too.
So, now when i need to use GBPVR's Live TV, i first start and close WinTV and then start GBPVR. Any ideas anybody?
Hi, anyone out there have a solution to resolve system unable to go to standby with the above version of GBPVR. I have initially installed ver 99.12 but system refused to go standby( okay if goto standby set at 1 minute). I reformat my whole harddisk and revert back to ver 99.05 and standby working fine for a few days but now the system refuse to go standby again. Pls help. :confused:
Finding a mux (multiplexer) that works well can be a little tricky. There are not only different 'brands' but also many different versions.
These muxes are scattered through cyberspace, often as part of large downloads. You might download several different packages only to find they all include the same version of a mux that is not working for you.
I felt it might aid the community to create a catalogue of muxes. This gives users the chance to try several different versions quickly and easily to find the one that works best for you.
To contribute please pm me with the details of what muxes you have. You can use Sub's mux checker, graphedit or direct show filter manager to locate your muxes and extract the file.
These filters can be registered or de-registered by command line or with direct show filter manager.
I am currently using v96.11 (Access DB) specifically because I love your Priority Recording plugins. I know there have been some discussions about having this feature standard with GBPVR. Iâve been out of the GBPVR loop recently. What is your opinion of the latest release with regards to priority recordings? Is Priority Recordings standard with the latest verion? Is it worth it for me to upgrade to the latest version? Thank you for your opinion.
having a newbe set up problem with a Twinhan Mantis DVB-T card.
After having added the BDA plug in, and the EPG, I am to map the channels, only find that scaning starts at T:C50 where I would ned the scan to start at C21 in order to find the free tv channels.
Where can I find the settings to modify?
Running the supplied DigitalTv SW works fine, but this works without the BDA drivers.
I have tried the TSReaderLite, but have not found any driver there that will work with my card...
OK I have GB-PVR installed on Windows XP Home, using a Hauggpauge WinPVR USB 2 as my my tunner and using a Expressvu 3100 (Dishnet 301:10) receiver for my signal source.
I have it configered so that I get picture and sound in GB-PVR from my satillite receiver, and I have my EPG setup correctly, all I have to do is set up my Hauggpauge MCE remote to work with GB-PVR and my satillite receiver?
Can anyone help me?
Thanks?
Not quite knowing the technical term, can you disable the music library's video screen saver? When I escape to the main GBPVR menu after hitting play on a playlist I don't want to see it in the main screen. I just want to see the GBPVR main screen info and the name of the song in the Video Panel.
This night in Itlay we had to add an hour to our clock. GBPVR show caos in TV listing and misses to record programs. Looking at TV scheduling I can see the caos last serveral days (till freday). Any advice?
thank you.
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.
