Channel Changer Stopped Working

[zed]

For some reason, channel changing stopped working. It was working fine but the past few days I've missed recordings because it didn't change channels. I haven't changed anything (famous last words ). I'm using hipsend and hip and it's a gen-you-wine Microsoft remote/blaster. I see in the log where it says it ran the command (2008-04-07 19:59:13.778 VERBOSE [7] Running: C:\Junque\HiPstuff\HipSend.exe 62) but nothing happens. If I paste that command into a cmd window, it works fine so I'm pretty sure hip is configured OK. I have the 'Allow service to interact with desktop' box checked for the recording service. I don't see any errors anywhere. I'm stumped. Any ideas?

[sub]

I have the 'Allow service to interact with desktop' box checked for the recording service.

Thats all I would have had to suggest. The log message and lack of error means it successfully ran HipSend.exe. There is no way of knowing from the GB-PVR's logs whether HipSend.exe had any problems during its execution.

[rbelisle]

Have you tried running hipsend from the command line to make sure it is sending your IR request?

[zed]

Yes, it works if I run it from the command line...it changes the channel to whatever I tell it.

This is very strange because I haven't changed anything in the system (that I know of) and it was working earlier in the week. Then again, it's Microsoft...

[zed]

Sub, when you have a chance could you take a look at these log files. There's something about insufficient privs and another error in the native.log file. Something about the joystick?? :confused:

I dunno if it's anything to worry about but I don't remember seeing anything like it before (not that I'm an authority on log file contents...).

Thanks...

[sub]

2008-04-08 18:09:49.564 VERBOSE [5] Running: C:\Junque\HiPstuff\HipSend.exe 762

Everything is fine in those logs. GB-PVR is successfully running HipSend.exe. In your case it sounds HipSend.exe is failing to communicate with Hip.exe. The usual cause of this is because the recording service is running in a different desktop session, which is at odds with Hip&HipSends usual method of sharing communicating (via the clipboard), and can be solved by setting the recording service to 'allow service to interact with desktop'. You've already indicated you'd done that, but I'd double check. After that you might need to ask the author of HIP if HipSend produces any log files.

You can ignore that pin connection error. Its normal. I had meant to hide that before putting the release out so as not to scare people. Its a normal part of working out the directshow pin connections.

[zed]

Thanks for the quick look. I was mainly wondering about those pin errors. The HIP issue is puzzling but I'll keep hacking at it. I'll let you know if I figure it out...

[zed]

Well, I got it working again. I think the problem had to do with remote desktop sessions. The system is connected to our big HDTV and it's difficult to do anything to it when the wife's watching so I use a remote desktop session to get into it. I must have logged off the session the other day which probably killed HIP. When I reconnected and logged back in, HIP restarted (it's set up to start at logon) and I could manually run hipsend but for some reason the recording service didn't seem to be able to communicate with hipsend. I disconnected the remote desktop session but then HIP woulda still been running under the session I started. I just went in and rebooted the box (during a commercial, of course ), which restarted everything including HIP and now it works OK. So, problem resolved, at least for now. I'll just have to remember not to log out of remote sessions.

At least I think that's what happened. Does that make any sense? I really don't completely understand all this Windoze stuff...