2007-10-04, 08:02 PM
Unfortunately it's going to be a while. I literally havnt started development yet. I've been out of the country most of the time since the 1.0.16 release, and have only got home a few days ago.
2007-10-04, 08:02 PM
Unfortunately it's going to be a while. I literally havnt started development yet. I've been out of the country most of the time since the 1.0.16 release, and have only got home a few days ago.
2007-10-04, 10:10 PM
Sorry for not replying sooner sub, had been out of the country myself the last few days. Looks like bobbuilder has done most of the diagnosis for me(!) already but to confirm I'm getting a similar error.
2007-10-05, 11:01 AM
Bobuilder - I should also have mentioned, this thread is worth a look for the issue:
http://forums.nextpvr.com/showthread.php...ght=remote In particular the MVPserverchecker app mentioned is one worth installing. I'm finding the remote much more reliable out of standby now with it running in the background.
2007-10-05, 11:39 AM
sub Wrote:I'm not sure why, but something different about your setup is causing Windows to not notify the PVRX2 that is activated, which means you're missing this very important message in your logs: Don't applications get WM_POWERBROADCAST messages with an PBT_APMRESUMExxx code whenever the system comes back from suspend/hibernate? Might they be more reliable?
2007-10-05, 11:51 AM
Ok thanks Ill give MVPServerChecker a go.
My remote is currently recieved via a novat-usb and its not great, I often get missed buttons or worse a sort of double press where ok gets received as up then ok, so you end up in the wrong menu. Ive just ordered a new MCE remote and Im going to start using HIP so hopefully that will improve things along with the suggestions in the other thread. Thanks Bob
2007-10-05, 04:00 PM
seldomshaven Wrote:Don't applications get WM_POWERBROADCAST messages with an PBT_APMRESUMExxx code whenever the system comes back from suspend/hibernate? Might they be more reliable?Yes, they do and GB-PVR currently uses this message as part of it's processing, but this is often too early to reintialise fullscreen exclusive mode. (ie, some users resume to the Windows locked, 'select user' screen etc)
Just wanted to say I have the same problem with FSE 90% of the time after resuming from hibernation. Black screen, the app is still running as the remote is still audibly working. What's worst for me is that it then also never hibernates again, so any kind of night-time wakeup means it's on forever.
It's clearly the focus issue, when I shift the focus by bringing up the Start Menu (CTRL-ESC), then ALT-TAB back to PVRX2, it then unloads & reloads automatically and everything is fine. The patch also caused the same problems (endless exceptions). Unfortunately I can't even go back to non-FSE, because in this version I get severe jerking (something I didn't in previous versions).
GBPVR System:
XP Pro SP2, AMD XP1800+, 512MB DDR, NVidia 6200 AGP (1.90.62 drivers), PVR-150 (2.0.43.24108 drivers), nVidia Purevideo Mpeg2 codec, PVRX2 1.4.7
2007-11-14, 10:55 AM
Still the same in 1.1.5...
GBPVR System:
XP Pro SP2, AMD XP1800+, 512MB DDR, NVidia 6200 AGP (1.90.62 drivers), PVR-150 (2.0.43.24108 drivers), nVidia Purevideo Mpeg2 codec, PVRX2 1.4.7
2007-11-14, 04:13 PM
You can find a fix here: http://forums.gbpvr.com/showpost.php?p=2...stcount=11
sub Wrote:You can find a fix here: http://forums.gbpvr.com/showpost.php?p=2...stcount=11 Just tried it <snipped - patch didn't extract properly, now works>
GBPVR System:
XP Pro SP2, AMD XP1800+, 512MB DDR, NVidia 6200 AGP (1.90.62 drivers), PVR-150 (2.0.43.24108 drivers), nVidia Purevideo Mpeg2 codec, PVRX2 1.4.7 |
|