I have gone through the wireless route for connecting MVP to my GBPVR Server, but have never been satisfied with the results. Dropped connections continue to frustrate me, so was wondering if any of you have had experience with using the new 85Mbps Homeplug network devices, especially with the MVP. It seems that these new devices may be just the ticket where wireless just doesn't seem to cut it.
I'm starting to think about future support for the new MPEG-4 based DVB is being used in a couple of countries (France is one), and wondered if anyone here is able to supply me a transport stream from one of these broadcasts? If you are in a position to help out, please PM me.
In the Disk Space tab, there are entries for variable bit rates. What are they for? Do they change the rates I have set in the GB-PVR Capture Sources tab?
Do anyone of you who have GBPVR installed on your computers notice that the monitor doesn't turn off even if you have it set in the power settings to turn off after # mins?
having a few issues on my new pc with both the cyberlink multiplexor and the intervideo one.
Ive always used the cyberlink one with no problems, but on my new pc using exactly the same file about 1 in 3 recording fail and crash the recording services with an error from mpgmux.
So I installed the intervideo one but this seems to have really bad audio / video sync issues.
Ill go and try the showshifter one next, but does anyone have any ideas?
I have changed processor, motherboard etc but not tv card (twinhan DTV) and im still usings winxp so Im not sure if its an issue with my pc or with the latest release of gbpvr.
As I am severely artistically challenged I would like to ask if there is anyone out there that could develop a logo for Comskip.
I would like to have one big version for on the Comskip forum site (instead of the phpbb logo) and one small one as a program Icon.
Any artists out there?
Hi all, help please! Am a newbie, have installed GBPVR but when clicking OK to update configuration, restarting recording service popup appears, goes away, then I get the following error. I was getting the other process error (dealt with in previous threads) but sorted that with the MS fix. Now this :
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.InvalidOperationException: Couldn't get process information from remote machine. ---> System.FormatException: Input string was not in a correct format.
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Int32.Parse(String s)
at System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean isHelp)
at System.Diagnostics.PerformanceCounterLib.get_NameTable()
at System.Diagnostics.PerformanceCounterLib.get_CategoryTable()
at System.Diagnostics.PerformanceCounterLib.GetPerformanceData(String[] categories, Int32[] categoryIndexes)
at System.Diagnostics.NtProcessManager.GetProcessInfos(PerformanceCounterLib library)
--- End of inner exception stack trace ---
at System.Diagnostics.NtProcessManager.GetProcessInfos(PerformanceCounterLib library)
at System.Diagnostics.NtProcessManager.GetProcessInfos(String machineName, Boolean isRemoteMachine)
at System.Diagnostics.ProcessManager.GetProcessInfos(String machineName)
at System.Diagnostics.Process.GetProcesses(String machineName)
at System.Diagnostics.Process.GetProcesses()
at xeb983fa94d0b4753.xfd6951461fe46d87.xd1bc48f5dba57993(Object xdf2e3583f942db7b, EventArgs xc4f45905cb1fc7ba)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
In using Bleb for EPG, the last programme on each day does not supply an endtime or duration. However, the GBPVR TV Guide seems to handle this ok, presumably working out where the first programme of the following day comes in. However, for channels ITV2 and BBC7 it just shows the last programme of the day running for the entire day.
I've looked at the source XML files on bleb and I can't see any discernible differences between channels that work and ITV2/BBC7.
I'm having a frustrating problem with gbpvr - my hushpc (specs above) records like a champ, but if I try to watch completed recorded programs on it (using the video-out of the on-board video) it will freeze after some variable amount of time, background recording or not.
Pausing seems to reliably make it freeze, but just watching a 1 hour recording it will freeze after 10, or 15, or 40, or any other random number of minutes.
Watching the recorded video in Windows Media Player (10) on the box/video out (I have a wireless keyboard/mouse attached, so this is possible) works flawlessly and never crashes the machine.
When it freezes, the video remains frozen on screen, the machine itself is completely hung - no response from the web interface, from Remote Terminal, Ping, Ctrl-Alt-Del, etc... it's dead jim. Nothing in the logs, nada. Just one frozen machine needing a hard reset/reboot.
After reboot if I don't try watching anything, It will run forever - recording shows, scheduling new shows, updating the EPG nightly, etc... rock solid.
Sooooo any thoughts? During recording the cpu usage is 5% or so, during playback it's 70-80% playback+recording 75-85%, so it's busy but not maxxed out. Playback settings are:
InterVideo NonCSS Video Decoder for Hauppauge
tried both Use VM7 and Use Overlay Manager, behaves the same for either
tried both check and uncheck minimal OSD - behaves the same for either
This machine has only run 95.16, it was a new install, fresh WinXP Pro, current drivers, current BIOS.
