I discovered last week that a seldom-used group of channels will not tune properly on my PVR350 with an IR200L pointed at a Dish 301 receiver. They end up on channel 10 instead of, say, channel 168. This happened four times in a row. I also have a 150 using the built-in blaster pointed at another Dish 301 receiver. I am running 1.08 on a system with Intel Celeron D, XP and 1G memory (a.k.a. "The Cheat".)
The day after my recordings failed I tried again. I tried to record four programs on 168. I again got channel 10 four times.
Live TV tuned to 168 correctly. I isolated live TV to the 150 and (priority?) recordings to the 350.
I started the GBPVR configuration utility and made various adjustments to the repeat count and delay. 168 tunes to 10.
I connected a TV to the CATV-out of the tuner and tried 168. The tuner showed receiving channels "1...6" and fails to 10 because there isn't a 16 in our lineup. (Which I'd guessed, but this just confirmed it.)
I tried making more adjustments to the delay and repeat values. 168 yields 16 which goes to 10.
122 goes to channel 122.
268 goes to channel 268.
I pointed a digital camera at the IR200L emitter. I entered 168. It went "Blink Blink ...". I entered 122. It went "Blink Blink Blink".
I raised and lowered and gently massaged repeat counts and delays. No effect.
I went through channels and isolated the problem to only 16X channels.
I looked at the log files. There were no obvious errors. I saw a reference to the IR200L.EXE. I tried running IRL200L.EXE from the command prompt. It entered test mode. It crashed. I tried running it from a DOS prompt. It entered test mode. It crashed. I tried running it from a DOS prompt with 168 as a parameter. It entered test mode. It crashed.
I laid down on my side on the floor. I moved my legs as though I were running. I went around in circles in this position saying, "Wooo wooo wooo wooo. Wooo wooo wooo wooo." It didn't help. 168 still stops after the 6 and tunes to 10. 122 tunes to 122. Other channels tune as expected.
I love GBPVR as a replacement for my ShowStopper ReplayTV, and the money that would have gone into a competing commercial product will eventually end up as a donation for Sub to cover me and a friend I converted GBPVR. This isn't a slam. It isn't even terribly important, because I almost never record from those channels. The Cheat is not dead and tunes to all other channels correctly as far as I can tell. But there's something happening other than what should be happening, and I'm not going to be able to sleep until I figure out why and correct it.
Anything went smooth in 1.08 until i started a channel scan.
I have two tuners and edited then in the bda.ini. I checked the description against graphedit, it's the same for both cards and it's like the s-1400 already present in the .ini.
When i scan channels i see good reception and 100% quality for both cards, but no channels show up. It is clear that it finds the transponders. The scan is quite fast.
Of course i checked my install against dvbviewer, which does find channels.
Although this is a fresh install (XP-SP2, vcruntime, direct-x updates, .net 2.0, bda fixes from microsoft, cyberlink from technotrend), my system fails on the mux check.
I am having the random skip with MVP problem referred to elsewhere in this forum. My machine has a Hauppauge Nova T 500 dual (digital) tuner and I am wondering whether the PVR150 timestamp fix referred to is needed. I don't want to just do it since the fix included new drivers for the capture card which surely can't be the same between the PVR150 and the Nova-T 500. Can anyone enlighten me? Or is there some other reasons for the random skip behaviour? I am running 99.12. Will the new version help?
I've gotten a few messages on my local box about PVRX2.xml not being found. Most recently I got this:
UbuNetStreamPlayer - VLCOverlay - unhandled exception at : WinIOError
Could not find file 'C:\Program Files\devnz\gbpvr\PVRX2.xml'.
Attaching screenshot and logs.
I got this trying to view AFTV - Cartoons, but have gotten it simply navigating through different items.
Does the Hauppauge WinTV-HVR-950 work with this whole set up? If so could someone please give me some assistance with getting it work. I have DirectTV now but I will be back at school in about a month with regular cable service. Thankyou.
I have an MCE machine with Satellite card, connected to MVP. On the PC recording and playback of TV is fine. However, on the MVP all you get is a blank screen for a few seconds then typically re-boots.
This is not a firewall issue as per other posts as I have disabled this for now.
The logs complain about no mux being found.
Also the MVP will play back MPEG2 files recorded OK, through the GBPVR interface.
The actual problem appears to be that all live and recorded TV is dvr-ms format, hence I believe it complaining about mux's.
I cant figure out how to stop it recording in this format. Under the Misc tab have selected various decoders - now on cyberlink. Also selected the option to convert DVR-MS to MPEg - it still records in DVR-MS.
I have cyberlink Ultra installed on the machine so would have expected that to be OK. I am sure this is something simple but I cant figure it out.
One last point is that I have never installed the Haupauge MVP software on this since it was re-built.
Has anyone had any success with the Hauppauge 1800 PCIe card and QAM, I have been trying and so far no luck with WinTV wo with GB-pvr. Does GB-PVR even support it as it won't detect an 1800 and using the 1600 (QAM) from the list doesn't work. Please, I need help or I am sending this thing back!
MVPServerChecker was unscathed by the loss of ZTools Source code. So I was able to update it to work more smoothly with GB-PVR 1.0.8...
MVPServerChecker continues to check for MVP Server boxes that pop up from time to time IF you have the GB-PVR Recording Service 'allowed to interact with the desktop' -- which is necessary if using other software like HIP...
It will also make sure that your Graphic User Interface (GUI) is always in the foreground...
And finally, it will now raise the CPU Priority of the GUI and hip.exe to 'Above Normal', so that it the GUI will perform better...
Quote:PVRX2.exe in GB-PVR 1.0.x requires 'grunty' computers. In other words, the program has evolved and now needs more power.
I have found on my systems, that extra power required conflicts with other operations like comskip or the recording service itself.
Raising the priority from Normal to Above Normal solved some of the conflicts. I also needed to raise HIP to Above Normal so the GUI and HIP would interact correctly...
