3.1.1 and irremote.ini for hauppauge

[kylebrophy]

Hi Guys,

Im sure this is something to do with the changeover to .net 4.0 - I use the irremote.ini commands for my Hauppauge remote - and it has been working marvellously until the upgrade to 3.1.1...

I suspect its just a matter of someone letting me know what the new app codes would be - as the ones below don't do anything anymore.
Ive only added a few lines - as its the app name that will have changed, so should just be a matter of find/replace.

[Default]
GRNPOWER={run(C:\Progra~2\NPVR\NextPVR.exe)}
0={findwnd(WindowsForms10.Window.8.app.0.33c0d9d,,)}{SendMsg(32775,48,0)}
1={findwnd(WindowsForms10.Window.8.app.0.33c0d9d,,)}{SendMsg(32775,49,0)}
2={findwnd(WindowsForms10.Window.8.app.0.33c0d9d,,)}{SendMsg(32775,50,0)}

Thanks in Advance

[pBS]

i get this on xp:
WindowsForms10.Window.8.app.0.2bf8098_r16_ad1
and this on win7/vista:
WindowsForms10.Window.8.app.0.2bf8098_r13_ad1

not sure why it's different on each os, but i had to modify my remotes to switch profiles on program change...very inconvenient...
not to mention the difference between pvrx2 and npvr now... [both pvrx2 and nextpvr used to be WindowsForms10.Window.8.app.0.33c0d9d]
used to be able to have one remote setup for both.. [now diff. for each os, and not same as old program, tho that's not a biggie]

[kylebrophy]

Thanks - ill try this later tonight or tomorrow and see how it works

[kylebrophy]

i get this on xp:
WindowsForms10.Window.8.app.0.2bf8098_r16_ad1
and this on win7/vista:
WindowsForms10.Window.8.app.0.2bf8098_r13_ad1

Sorry looks like that doesn't work for me. I have 64bit windows 7 if that makes any difference?

[ady_m]

Hi Guys,

Im sure this is something to do with the changeover to .net 4.0 - I use the irremote.ini commands for my Hauppauge remote - and it has been working marvellously until the upgrade to 3.1.1...

I suspect its just a matter of someone letting me know what the new app codes would be - as the ones below don't do anything anymore.
Ive only added a few lines - as its the app name that will have changed, so should just be a matter of find/replace.

[Default]
GRNPOWER={run(C:\Progra~2\NPVR\NextPVR.exe)}
0={findwnd(WindowsForms10.Window.8.app.0.33c0d9d,,)}{SendMsg(32775,48,0)}
1={findwnd(WindowsForms10.Window.8.app.0.33c0d9d,,)}{SendMsg(32775,49,0)}
2={findwnd(WindowsForms10.Window.8.app.0.33c0d9d,,)}{SendMsg(32775,50,0)}

Thanks in Advance

Same problem here.... Updated to 3.1.1 and has killed everything on the remote except for the START WITH GREEN BUTTON function.

Can we please have a fix for this? Love NPVR, hate having to get up!

BR Ady_m

EDIT:- Windows XP 32bit

[kylebrophy]

Same problem here.... Updated to 3.1.1 and has killed everything on the remote except for the START WITH GREEN BUTTON function.

Can we please have a fix for this? Love NPVR, hate having to get up!

BR Ady_m

EDIT:- Windows XP 32bit

I have just had to revert to the earlier irremote.ini file that was focus dependant - and that works... But would be nicer to have one that works regardless of npvr having the focus.
I can post the older file if you need. Just to save having to get out of the chair

[mvallevand]

For me on Win7 64 it is

WindowsForms10.Window.8.app.0.2bf8098_r15_ad1

It reports this in spyxx and also in AU3Info from AutoIt

Martin

[mvallevand]

Testing in VM's I have this in Win 8.1 32 bit preview

WindowsForms10.Window.8.app.0.141b42a_r9_ad1

my 32bit Win7 VM s the same as pBS's.

Martin

[kylebrophy]

For me on Win7 64 it is

WindowsForms10.Window.8.app.0.2bf8098_r15_ad1

It reports this in spyxx and also in AU3Info from AutoIt

Martin

Bingo - im working now.
It seems these codes are all dependant on the version of windows - and the version of npvr (.net version used).
Might be useful if someone could add these to the section on irremote.ini

[JP23]

I changed the window class in my irremote.ini to get my remote working again, but then it stopped working again, and it turned out that the window class had changed. This morning it seems to have changed again, so I don't think it's going to remain constant like it used to.

You can retain the 'no focus' functionality by reverting to matching the window name, so you'd replace {findwnd(WindowsForms10.Window.8.app.0.33c0d9d,,)} with {findwnd(,nPVR)}

The only issue with this is you may occasionally get the commands sent to the wrong window if you have another window name starting with npvr, such as Firefox on the NPVR announcements forum, or your NPVR data folder open in windows explorer.