• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

[ir] Web-based Remote Control

Apologies for inaccuracies in the old threads quoted,

In old 1.19 to 1.20 versions of ir pressing Yellow or Green buttons with the multi key macros would cause an immediate humax crash because they are repeating buttons and my old fat fingers are not fast enough to only generate a single button press action, running multiple macros simultaneously brought the humax down.

Early attempts to fix this (the block repeats option) didn't and @af123 was implementing another fix when he fell ill
I don't understand the Foreign flags either but it appears to be 1 on initial button press and 0 on generated repeats.

The good news is that this fix is in the current package 1.22 and Green and Yellow button macros now work correctly to change channels without crashing (when using the Humax remotes)

The F1 code introduces a 1 second pause as documented in the wiki

Humaxtv.log for pressing the Yellow button:-
Code:
458    macro thread exiting.
457    +New IR code: 0x00000001 0xec131000 (13) [foreign=0]
456    GetEvents(): faking key 13 (1)
455    GetQueueSize: 1
454    +New IR code: 0x00000000 0xec131000 (13) [foreign=0]
453    GetEvents(): faking key 13 (2)
452    GetQueueSize: 1
451    InjectCommand: setting signal (0x100ab80)
450    InjectCommand: Input list 0
449    InjectCommand: Buffers 0 0100ad08 1 0100ad14
448    InjectCommand: Got mutex
447  
446    Injecting 13
445    Macro inject: 13
444    +New IR code: 0x00000001 0xfa051000 (5) [foreign=0]
443    GetEvents(): faking key 05 (1)
442    GetQueueSize: 1
441    +New IR code: 0x00000000 0xfa051000 (5) [foreign=0]
440    GetEvents(): faking key 05 (2)
439    GetQueueSize: 1
438    InjectCommand: setting signal (0x100ab80)
437    InjectCommand: Input list 0
436    InjectCommand: Buffers 0 0100acf0 1 0100acfc
435    InjectCommand: Got mutex
434  
433    Injecting 05
432    Macro inject: 5
431    Macro inject: f1
430    +New IR code: 0x00000001 0xe51a1001 (1a) [foreign=1]
429    Blocking 1a.
428    Real IR code: 0x00000001 0xe51a1000 (1a) [foreign=0]
427    GetQueueSize real
426    +New IR code: 0x00000001 0xe51a1001 (1a) [foreign=1]
425    Blocking 1a.
424    Real IR code: 0x00000001 0xe51a1000 (1a) [foreign=0]
423    GetQueueSize real
422    macro thread starting for 1a (0x1018948).
421    +New IR code: 0x00000001 0xfa051000 (5) [foreign=0]
420    1a is assigned to a MACRO. Replacing with 5.
419    Real IR code: 0x00000001 0xe51a1000 (1a) [foreign=0]
418    GetQueueSize real = 1
417    GetQueueSize real
416    +New IR code: 0x00000000 0xfa051000 (5) [foreign=0]
415    1a is assigned to a MACRO. Replacing with 5.
414    Real IR code: 0x00000000 0xe51a1000 (1a) [foreign=0]
413    GetQueueSize real = 1





The only oddity is that when using a LG magic remote that can operate the humax it only issues the first button press of the macro i.e. switches to channel 3 rather than 33 - from the log the macro processing doesn't complete.
Code:
487    +New IR code: 0x00000000 0xf00f1000 (f) [foreign=0]
486    Real IR code: 0x00000000 0xf00f1000 (f) [foreign=0]
485    GetQueueSize real = 1
484    GetQueueSize real
483    +New IR code: 0x00000000 0xf00f1000 (f) [foreign=0]
482    Real IR code: 0x00000000 0xf00f1000 (f) [foreign=0]
481    GetQueueSize real = 1
480    GetQueueSize real
479    +New IR code: 0x00000000 0xfa051000 (5) [foreign=0]
478    1a is assigned to a MACRO. Replacing with 5.
477    Real IR code: 0x00000000 0xe51a1000 (1a) [foreign=0]
476    GetQueueSize real = 1
This is not a real problem - the code can't really be expected to handle all of the myriad of other manufacturers remotes.

I hope this helps
 
Last edited:
I have installed IR 1.23-2 on my parents' HDR Fox T2. The settings to block remote control mode icons and disable volume control are enabled but not working. The HDR Fox T2 is setup for stereo audio without audio description. Settings attached. CFW is 3.14, all packages updated just before I installed IR.
 

Attachments

  • IMG_1068.png
    IMG_1068.png
    367.6 KB · Views: 6
  • IMG_1069.jpeg
    IMG_1069.jpeg
    52.1 KB · Views: 6
Did you reboot it?
Several times. Ran fix-flash-packages in web UI, rebooted, updated remaining packages in web UI, rebooted, installed IR package, rebooted, configured IR, rebooted, found not working so turned all IR options off and back on again, rebooted, still not working.
 
Does anything to do with it work?
Run the ir3/debugon diagnostic, reboot and then look in the /tmp/humaxtv.log file to see what's happening when you try it.
 
Does anything to do with it work?
I'm only trying to disable the volume control and icons for remote mode changes. I also enabled suppressing duplicate commands since the remote sometimes does that. I'm not currently interested in any other IR functions.
Run the ir3/debugon diagnostic, reboot and then look in the /tmp/humaxtv.log file to see what's happening when you try it.
File attached. I cycled round the modes on the remote, then did volume down several times and volume up several times.
 

Attachments

I'm only trying to disable the volume control and icons for remote mode changes. I also enabled suppressing duplicate commands since the remote sometimes does that. I'm not currently interested in any other IR functions.
Irrelevant. It's useful to know what works even though you may not intend to use it.
File attached.
Mine generates foreign=0 messages and it works OK.
I would suggest your physical control is not configured for the same mode as the package is (looks like mode 2), so you need to change one of them.
 
Irrelevant. It's useful to know what works even though you may not intend to use it.
I don't know how to use any of the rest of the IR package features.
Mine generates foreign=0 messages and it works OK.
I would suggest your physical control is not configured for the same mode as the package is (looks like mode 2), so you need to change one of them.
The remote successfully controls the HDR Fox T2, how can it not be correct?

EDIT: there is only one HDR Fox T2 in use at my parents and if I ever changed what mode it uses I have forgotten, and cannot work out why on earth I would have done that given only one box has ever been in use here.
 
What does the control for the remote mode do in IR? It says my box is in mode 1, but you say it looks like it is in mode 2. And if I use the menu in IR to change what mode the box is in, won't that mean it can't receive commands from my remote any more?
 
Oh I get it now, the option in the IR package settings is to tell it what mode the HDR Fox T2 and remote control are in. I didn't get that at all, I thought it was for changing the mode the HDR Fox T2 is in. My mistake.

OK I've set mode 2 now in IR and it is working, blocking the volume commands and mode change icons and repeated commands. Proof attached:
 

Attachments

I guess the only thing left now is to disable the debug. Is that running diagnostic ir3/debugoff perhaps? I don't want to try it and screw something up, I know relatively little about these debug options.
 
I notice when commands are blocked IR seems to do it by just changing the command inserted. Is it changing them to a different mode which the box then ignores because that is not what it is configured to use?
 
Oh I get it now, the option in the IR package settings is to tell it what mode the HDR Fox T2 and remote control are in.
The relevant Wiki page is not explicit on this point (quelle surprise). However, from af123's original IR post:
If you have changed your remote control mode from the default, for example to support having multiple Humax boxes in the same room, then you will need to set the remote control mode in the webif settings to match. To find out your current remote control mode you can hold down the OK and ZERO buttons on your real remote for five seconds and a message will appear on-screen which tells you the current mode, along with the option to change it.
 
OK there is stuff written that would have answered my questions. But in my defence there's a hell of a lot of stuff written here and it takes a long time to find the right thing and read it. On top of that there is the risk the firmware has subsequently changed and the documentation has not been updated to match.
 
Back
Top