I had to revert to earlier version, as newest did not my make STB change channel.
IR Server Suite - Public Test Version (1 Viewer)
- Thread starter and-81
- Start date
- Status
Toggle problem
just want to confirm that by removing the toggle statement and the layer 1 &2, MP does not crash. Still the translator crash, see the logs.
Tks
New findings: Crash avoided by changing the last serial command in the macro causing the translator crash. Changed option "Wait for respons" from True to False.
just want to confirm that by removing the toggle statement and the layer 1 &2, MP does not crash. Still the translator crash, see the logs.
Tks
New findings: Crash avoided by changing the last serial command in the macro causing the translator crash. Changed option "Wait for respons" from True to False.
- August 31, 2007
- 6
- 0
- Home Country
-
Canada
First, Thank you very very very much for the new release. I've been eagerly waiting for it. Just been playing with it for a couple hours and a few notes so far:
1. Setting a key to send a PGUP or PGDN command crashes Translator, unfortunately... any way to fix this or get around it? I tried sticking the PGUP in a macro and the same thing happened. This was working fine in the previous release.
2. Thanks for adding mouse functionality and the fixed mouse positioning in the macro section. For some reason, when I use the fixed mouse positioning, though, my X and Y coordinates don't function right. My resolution is 1366x768, but the whole XY area covered by the fixed mouse coordinates of 10,000 x 10,000 is about a tenth of my screen, in the upper left corner.
3. I'm currently getting around this by running a macro to send the mouse to 0,0, and then another two commands to move it right X amount and then down Y amount. This has its own problem...The X movement does not set correctly when I do the "move Mouse right" command. The Y movement (down command) is fine. With the X, it works incorrectly with the amount it moves to the right -- somewhat less than what it should be (half maybe, it seems?). This happens the FIRST time i run the macro in the program. If I trigger the macro again, it moves to the correct location. However, any movement or click of the (real) mouse will make it do what it does the first time, with the X movement not being set correctly.
Thanks again for the hard work.
1. Setting a key to send a PGUP or PGDN command crashes Translator, unfortunately... any way to fix this or get around it? I tried sticking the PGUP in a macro and the same thing happened. This was working fine in the previous release.
2. Thanks for adding mouse functionality and the fixed mouse positioning in the macro section. For some reason, when I use the fixed mouse positioning, though, my X and Y coordinates don't function right. My resolution is 1366x768, but the whole XY area covered by the fixed mouse coordinates of 10,000 x 10,000 is about a tenth of my screen, in the upper left corner.
3. I'm currently getting around this by running a macro to send the mouse to 0,0, and then another two commands to move it right X amount and then down Y amount. This has its own problem...The X movement does not set correctly when I do the "move Mouse right" command. The Y movement (down command) is fine. With the X, it works incorrectly with the amount it moves to the right -- somewhat less than what it should be (half maybe, it seems?). This happens the FIRST time i run the macro in the program. If I trigger the macro again, it moves to the correct location. However, any movement or click of the (real) mouse will make it do what it does the first time, with the X movement not being set correctly.
Thanks again for the hard work.
Hey, I've been away for a while. But I've still got the hibernation issue. INow also noticed the server doesn't work when I restart the computer. I have to manually close it, and start it up again to get it working.
I there anyway to reinstall the default mce remote driver? And how can I check which MCE services are running when I startup?
Is there anyway you can help me with this problem? ( I already uninstalled IR server suite and reinstalled the newest version)
The SVN after the stable relase Mp 0.2.2.0 and the irserver have this problem with my system. The only work around I've found is to delete the USBBIOSX from registry, but losing the resume capability with the remote.
I've tried MCE replacement, Irserver, USBUIRT with TV2 and also MYblaster in TV3!
My system o.p. is Windows XP.
- Thread starter
- #316
Thank you all for your feedback, there are a few issues that are causing some grief at the moment but I hope to have them all sorted out within a week or so.
I'll try to address your problems individually below, but I'd also like to suggest a few general solutions people might try:
For issues with the MCE Remote support you can try using the MceIr.dll by using the IR Server Girder Plugin support. Disable the MCE Transciever plugin in IR Server and enable the Girder Plugin, then configure the Girder Plugin and point it at the MceIr.dll from the replacement driver. You don't need to be using the replacement driver for this to work, and it will use the old method of accessing the device. This might get around some of the problems that are occurring ... if not then at least it's worth a try. If it does solve your problem let me know so I can try to fix the new code.
For issues with standby/resume please try the MCE Standby Tool (you can find it in the forums).
Also, could people who are trying to send keystrokes to ffdshow let me know if the new system for keystroke commands works for you?
Thanks,
I'll now try to address people individually, if I've left anyone out then let me know:
SweetHome:
Standby/Resume issues are causing me a lot of grief, mainly because it just works for me... All I can recommend to people is to try the MCE Standby tool. In the meantime I am still trying to improve this.
Also, regarding item 2 in your first post, you may need to press Enter when you change the screen you'd like the button to map to. This makes it store the new details. If that makes sense?
I'm going to add Window minimize/maximize/restore macro items in the future, which should address your external program launching concerns.
Tazman:
I haven't forgotten you, I just wasn't able to get everything into the latest test version. The next test version (which will be only a few days away this time) will have what you need to try to get your stb working with the plugin... I'll talk to you more about that when the feature is ready.
TVmecken:
Your problem with crashing macro's will be fixed in the next version.
Spragleknas:
I'm working on the STB problems at the moment, this should be fixed for the next version, but if you can provide log files if there is anything in them then that would help me.
blankpoint:
I changed the Keystroke simulation code to make it a lot better and more reliable. Unfortunately I missed the Page Up/Down commands :> I've fixed this now and it will be available in the next version.
Also, it turns out that absolute mouse positioning is not based on screen coordinates but on dividing the screen into ~65,000 steps. I've re-written the code for this so it will be fixed in the next version too.
generator:
You should definitely switch back to the default driver, to do this go to Device Manager and remove the replacement driver, this is detailed in the documentation for the replacement driver. To check which services are running (though I doubt this is the cause of the problem) you can go to Start Menu -> Run -> Services.msc
Give that a try and then send me a Private Message and we can work on this issue more closely. Standby/Resume issues are causing me a lot of headaches at the moment and I want to get it sorted out once and for all.
Fabolus:
If you have standby/resume problems with all those solutions (MCE Replacement plugin, USB-UIRT, MyBlaster) then it sounds like a problem that is in your hardware setup (perhaps updating your bios would solve it?).
Cheers,
I'll try to address your problems individually below, but I'd also like to suggest a few general solutions people might try:
For issues with the MCE Remote support you can try using the MceIr.dll by using the IR Server Girder Plugin support. Disable the MCE Transciever plugin in IR Server and enable the Girder Plugin, then configure the Girder Plugin and point it at the MceIr.dll from the replacement driver. You don't need to be using the replacement driver for this to work, and it will use the old method of accessing the device. This might get around some of the problems that are occurring ... if not then at least it's worth a try. If it does solve your problem let me know so I can try to fix the new code.
For issues with standby/resume please try the MCE Standby Tool (you can find it in the forums).
Also, could people who are trying to send keystrokes to ffdshow let me know if the new system for keystroke commands works for you?
Thanks,
I'll now try to address people individually, if I've left anyone out then let me know:
SweetHome:
Standby/Resume issues are causing me a lot of grief, mainly because it just works for me... All I can recommend to people is to try the MCE Standby tool. In the meantime I am still trying to improve this.
Also, regarding item 2 in your first post, you may need to press Enter when you change the screen you'd like the button to map to. This makes it store the new details. If that makes sense?
I'm going to add Window minimize/maximize/restore macro items in the future, which should address your external program launching concerns.
Tazman:
I haven't forgotten you, I just wasn't able to get everything into the latest test version. The next test version (which will be only a few days away this time) will have what you need to try to get your stb working with the plugin... I'll talk to you more about that when the feature is ready.
TVmecken:
Your problem with crashing macro's will be fixed in the next version.
Spragleknas:
I'm working on the STB problems at the moment, this should be fixed for the next version, but if you can provide log files if there is anything in them then that would help me.
blankpoint:
I changed the Keystroke simulation code to make it a lot better and more reliable. Unfortunately I missed the Page Up/Down commands :> I've fixed this now and it will be available in the next version.
Also, it turns out that absolute mouse positioning is not based on screen coordinates but on dividing the screen into ~65,000 steps. I've re-written the code for this so it will be fixed in the next version too.
generator:
You should definitely switch back to the default driver, to do this go to Device Manager and remove the replacement driver, this is detailed in the documentation for the replacement driver. To check which services are running (though I doubt this is the cause of the problem) you can go to Start Menu -> Run -> Services.msc
Give that a try and then send me a Private Message and we can work on this issue more closely. Standby/Resume issues are causing me a lot of headaches at the moment and I want to get it sorted out once and for all.
Fabolus:
If you have standby/resume problems with all those solutions (MCE Replacement plugin, USB-UIRT, MyBlaster) then it sounds like a problem that is in your hardware setup (perhaps updating your bios would solve it?).
Cheers,
Hi Aaron,
I also had some suspend/resume issues, but only with IR Blaster. With MRP it works fine again so I don't think it has to do with the HW or BIOS as for Fablus.
For now I am happy with MCE Replacement Plugin and there is no functionality missing. Still the problem bothers me...
/Peter
I also had some suspend/resume issues, but only with IR Blaster. With MRP it works fine again so I don't think it has to do with the HW or BIOS as for Fablus.
For now I am happy with MCE Replacement Plugin and there is no functionality missing. Still the problem bothers me...
/Peter
- Thread starter
- #318
I'm doing some big standby/resume testing as we speak and I've found a problem...
There is a race-condition that was not showing up in my earlier testing because of my development/debug environment.
This may not be the only problem with standby/resume, so I will continue my testing and hopefully the next version will be better for it.
Cheers,
There is a race-condition that was not showing up in my earlier testing because of my development/debug environment.
This may not be the only problem with standby/resume, so I will continue my testing and hopefully the next version will be better for it.
Cheers,
- May 15, 2006
- 173
- 0
- Home Country
-
Denmark
If I remember correctly there are no errors, as the IR blaster does send IR-signals... they just don't do anything (STB unresponsive). I'll install the new version for testing purpose (if wanted) @ (or before) friday.
My HTPC is in daily usage by the familiy, so I have limited "fiddeling time"
- Status