"Your system does not support the required VMR9 video renderer"

[bustedse-r]

No, I haven't found a way to detect or handle this yet. Suggestions welcome.

perhaps I could send a "return and ESC" to the window. I'll try and take a look.

I think this would be pretty easy in AutoIT by searching for window text

Code:

If WinActivate("PVRX2", "does not support the required VMR9 renderer") Then
  Send("{ENTER}")
End If

[sub]

I'm happy to look into this (again), but I've got to clear the decks of some work I've got on first (and some work travel). If someone can remind me in about two and half weeks, then I'll definitely have more by then.

[gEd]

I think this would be pretty easy in AutoIT by searching for window text

Code:

If WinActivate("PVRX2", "does not support the required VMR9 renderer") Then
  Send("{ENTER}")
End If

cheers bustedse-r, nice first post and welcome!

I'll try it out.

[frankmcg]

Any feedback on whether this worked gEd? Apologies haven't had a chance to try it out myself yet.

[gEd]

No yet but I have only just got the text exactly right. I will let you know.

[sinclair67]

Thanks gEd and frankmcg for taking a look at it. I have been using Custom VMR9 with PVRX2.exe as a work-around and its been working OK, at least I can record shows, and have the computer hibernate and wake at the correct times. The displays breaks up sometimes in custom VMR9.

[gEd]

Ok, I have had time to look into this a little more. Unfortunately, bustedse-r's idea didn;t work as there is no window active, just the "Sorry" dialogue box.

The way I see it though is that if gbpvr/pvrx2 is running but there is no active window that my script can bring to the foreground, gbpvr must be barfed, presumably with the VMR9 error.

I have therefore modded my script to manage this situation and kill the gbpvr process if it cannot find a running window.

Attached is an updated version of the script if anyone suffering from this problem wants to try it out.

[welshy]

Skip read through most of the posts in this thread, but remembered I had this problem when I setup GB-PVR over the weekend. Also noticed someone mention they had this when using 'remote control software'

When I setup my dedicated box in the lounge I initially used RDP (Remote desktop) to hit it from my main machine. RDP was giving me the 'VMR9' errors when I launched GB-PVR remotely. When I launched it on the dedicated box it ran perfectly. This was doing my head in but I eventually figured it out...

Most remote software, it seems, will not allow you to fully use your GFX card. It basically uses the default window display drivers, so starting GB-PVR remotely, using those drivers, causes it to throw up that error.

I eventually solved this by using Dameware (which I use in work daily). Brilliant little program. If you have local admin credentials and an address it will install itself completely on a remote client, then remove itself when done. It also, more importantly, does not use the windows drivers, but the actual display drivers used by the client itself

Not sure if this is the problem everyone is experiencing, but it may help some

[hzwaal]

When I setup my dedicated box in the lounge I initially used RDP (Remote desktop) to hit it from my main machine. RDP was giving me the 'VMR9' errors when I launched GB-PVR remotely. When I launched it on the dedicated box it ran perfectly. This was doing my head in but I eventually figured it out...

The VMR9 renderer is not available under RDP, which is why you're getting the error. With RDP you really have a separate terminal session, with your RDP terminal and generic graphics drivers. You'll also will not have any overlays. I can't even see the nVidia control panel when I'm logged on using RDP.

I eventually solved this by using Dameware (which I use in work daily). Brilliant little program. If you have local admin credentials and an address it will install itself completely on a remote client, then remove itself when done. It also, more importantly, does not use the windows drivers, but the actual display drivers used by the client itself

I'm not sure what Dameware is doing nor what you are using it for. I always use VNC (or actually TightVNC) to do things I cannot do in RDP. With VNC you'll see a snapshot copy of your login session on the remote machine. This way you can use any renderer that is available and have full control over the hardware. Since VNC will only send screen snapshots, you will not see any 3D animation or movies, but you'll see individual frames from them. When operating GB-PVR remotely, you will therefore have to refresh the screen now and then. I always do this by pressing shift or ctrl or any other keypress without effect, which will trigger an update.

[welshy]

I'm not sure what Dameware is doing nor what you are using it for.

It's freeware if I remember. Very small remote app. It displays the remote client's desktop in real time, so you can even play with GB-PVR's menu's etc remotely. It does flicker a bit but that's to be expected.