Sluggish remote performance

[madcat]

Using the setup below. when using the remote, many times the response is very slow, or a click on a remote won't do anything, and then the next click would do them both (like, "down" - nothing happenes. Press "down" again - on screen moves two lines down).

Using the IR software form Hauppauge (not the "direct" setup).
There is nothing significant running on the box (CPU, if any, is used by GBPVR).

I think I have the latest drivers from Hauppauge (their site is not the friendliest).

Any idea?

[madcat]

Anyone? you want to tell me that nobody has suffered this Hauppauge remote behavior?

[gEd]

sorry no ideas on a fix.

I do find it a bit sluggish but I have kind of learned to live with it.

Maybe on your pvr it is worse.

Are you saying that sometimes, if you press down arrow it will completely ignore this command (irrespective of how long you wait) until you press the key again, at which point it performs down twice? If so, that sounds like a bug in ir.exe to me.

What does drive me mad it that the remote on my nova-t usb2 frequently inserts an up arrow when I press OK - very annoying. I contacted Hauppauge about it and they very swiftly sent me a replacement remote - no questions asked. It does the same thing!

Hope you find a solution soon.

[madcat]

Yes, what you described does happen.
I also notices that extra Up Arrow for the OK, but disregarded, thought it's all part of the same thing.
I guess a new remote wont help, sounds like a SW issue.

Did anyone try to transfer the Hauppauge remote to a universal remote (by "learning")? I will try tonight, but thought ppl might have experience.

[rtiangha]

I've found that giving the ir.exe process a higher priority using the Task Manager seems to help some. Of course, with changing system process priorities, you run the risk of making your system unstable if you don't know what you're doing, so as always, proceed with caution.

[sub]

I suspect it's something to do with parts of the remote control sofware being paged out...

If I use my remote (Non Hauppauge) after a long time of inactivity (i.e. days) with lots of recordings being taken in between, there is a period of furious disk activity before the system responds to the button I just pressed.

Once that first button 'gets through' everything is 'normal'

There is a memory leak I've found and fixed for DVB users, that could be your possible cause for this. If use set <BDAUsePsiParser> to 'false' in config.xml, it'll help...but remember to put it back to 'true' for the next release.

[sub]

.NET memory management can be a pain, and does typically lead to a lot of memory being used, but this wasnt the specific issue I've found and corrected.

The leak was in the PsiParser, which is native C++ code (not .NET).

[madcat]

Without getting this thread into a how-does-garbage-collection-works (.Net, Java and alike), I may add:
The fact that the runtime manages memory for you (no "free" or "delete" commands), does not mean there are no leaks. I call it "you only sweep it under the curpet". The runtime "knows" not to delete or free an object, if it's still being referenced. So, like in any coding situation - you can never have a perfect code, instead of in the "old days" forgetting to free something, you forget to remove a reference to an object, or to write it in a way that will not hold un-needed references beyond the point of usage. Otherwise, the runtime "thinks" it is being used, will not free it, and viola - memory leak.

[sub]

Without getting this thread into a how-does-garbage-collection-works (.Net, Java and alike), I may add:
The fact that the runtime manages memory for you (no "free" or "delete" commands), does not mean there are no leaks. I call it "you only sweep it under the curpet". The runtime "knows" not to delete or free an object, if it's still being referenced. So, like in any coding situation - you can never have a perfect code, instead of in the "old days" forgetting to free something, you forget to remove a reference to an object, or to write it in a way that will not hold un-needed references beyond the point of usage. Otherwise, the runtime "thinks" it is being used, will not free it, and viola - memory leak.

I am well aware of this, and do my best to test that the app isnt continuing to consume memory. The only leak I'm aware of is this DVB one I've mentioned above, which is fixed for the next release.

[madcat]

Don't get me wrong - I am sure you are aware of all this. Without me knowing you - having gone that far with this project, you must know.
This comment was more intended for Mvandere's question.

Rtiangha - how do you maintain the process priority across reboots?
Sub - what is "DVB"? am I a "DVB user"?