IMON support (3 Viewers)

[JoeSmith]

i've been using imon for some time and it worked fine as soon as i had configured and mapped buttons to mp. A year ago imon and mp was a real nightmare (crashing..) but its become much better.
In MY case IRSS (my remote) feels much more responsible and you can do a lot of other nice things with irss. The option of configuring buttons on tv, music or whatevery differently is also very nice (in imon you can only assign a button to a single keypress).

If youre happy with imon - keep it - if not -> irss

 

[hulkhaugen]

so if i use irss, i can drop shortcut'er plugin?

 

[belcom]

so if i use irss, i can drop shortcut'er plugin?

I don't even know the shortcutter plugin, so I would say YES!

 

[belcom]

Hi all,
After trying several versions of IRSS with my iMON remote (iPAD), I finally managed to get it working (almost) using this new version (1.4.2.3129). The only problem I now have is that IRSS cannot configure the remote mode (mouse/keyboard). As a result using the direction pad triggers corresponding actions in MP (Up/Down/Left/Right) but also moves the mouse and there is no way to stop it from doing so. I have unchecked "Enable keyboard input" and "Enable mouse input". Checking "Enable mouse/keyboard switch..." makes no difference.

iMON Manager version: 7.64.0930 (Thermaltake) (iMON is not running)
Firmware version: 0x380206 LCD HID OEM

And here is the log: View attachment 49092

Any clues what is wrong?

Thanks,
Arion

Pleae jump in here: https://forum.team-mediaportal.com/ir-server-suite-irss-165/imon-support-66786/index25.html . I think this should be fixed in this version of minidisplay if you use it:

Hi arion!

Can you please try to delete "Direct Input Receiver.*" from "%ProgramFiles%\IR Server Suite\IR Server Plugins\" ?
Note that IR Server has to be stopped and Configuration Dialog has to be closed for this to work.

btw. did you install IRSS as Application oder Service?
Application is the prefered option for iMON, even with XP.

So try again and please provide all logs from IRSS log directory, along with your feedback.

@1stdead: the MiniDisplay-Bug only affects MCE remotes.

 

[arion_p]

Can you please try to delete "Direct Input Receiver.*" from "%ProgramFiles%\IR Server Suite\IR Server Plugins\" ?
Note that IR Server has to be stopped and Configuration Dialog has to be closed for this to work.

I will try tonight and report back with full logs.

btw. did you install IRSS as Application oder Service?
Application is the prefered option for iMON, even with XP.

Using Application mode.

Thx

 

[belcom]

This attached test version tries to enable Front Panel Buttons.

Please provide feedback!

 

[arion_p]

Hi Belcom

I moved "Direct Input Receiver.*" to another folder (outside Plugins), rebooted and tried again. Still the same behavior.

Logs attached are from the following test:

1. After reboot, stopped IR Server and exited IR Server Configuration
2. Deleted all logs except Install*.log
3. Started IR Server Configuration and IR Server
4. Moved mouse pointer around using the pad
5. Tried to change to keyboard mode by pressing the keyboard/mouse key
6. Moved mouse pointer around using the pad
7. Stopped IR Server and exited IR Server Configuration
8. Copied logs

I noticed that initially an attempt is made to switch the remote to keyboard mode which fails after 100 retries. Then when I pressed the keyboard/mouse key an attempt is made to switch the remote to mouse mode which also fails after 100 retries.

BTW: Wouldn't logging the actual win32 error help track down this problem?

Tell me, if you need me to do additional tests.

 

[belcom]

Hi Belcom

I moved "Direct Input Receiver.*" to another folder (outside Plugins), rebooted and tried again. Still the same behavior.

Logs attached are from the following test:

1. After reboot, stopped IR Server and exited IR Server Configuration
2. Deleted all logs except Install*.log
3. Started IR Server Configuration and IR Server
4. Moved mouse pointer around using the pad
5. Tried to change to keyboard mode by pressing the keyboard/mouse key
6. Moved mouse pointer around using the pad
7. Stopped IR Server and exited IR Server Configuration
8. Copied logs

I noticed that initially an attempt is made to switch the remote to keyboard mode which fails after 100 retries. Then when I pressed the keyboard/mouse key an attempt is made to switch the remote to mouse mode which also fails after 100 retries.

BTW: Wouldn't logging the actual win32 error help track down this problem?

Tell me, if you need me to do additional tests.

Attached is another test build of IRSS.
Should enable iMON HID devices on systems running strong cultured setups. (For example English Windows, Greek codepage)

pls provide feedback!

 

[arion_p]

Hi,

I just tried the new test build but unfortunately it didn't work (logs attached). It seems there is some argument count mismatch in DebugWriteLine().
I also tried what we discussed yesterday, using Unicode instead of ANSI strings in GetRawInputDeviceInfo(). It didn't crash like yesterday, but it didn't make any difference so I am not so sure it is related to regional settings.

(BTW: yesterday it probably crashed because changing to the Unicode version of the function also requires that you allocate twice the buffer size - returned pcbSize is in chars not bytes)

I still cannot figure out why GetRawInputDeviceInfo() returns the name with \??\HID instead of \\?\HID

 

[belcom]

Another test version... still trying to fix arion_p's problem.
It turned out that it probably is a WinXP issue!