Chris, You seemed to understand what I was saying, You then did method 2, which I think you were saying also worked. Now I was just trying to get my head around this by asking. In using method 2, does it take 1 or 2 button presses to get the command to recognize when switching from TV to SAT. I'm trying to figure out what your remote is doing with that keymove, so I understand what it. Itranx wrote:Re. '...do a keymove for each input from a FUNCTION in the TV device to a button (phantom, or shifted) on the relevant device'
and
'...when switching from TV to SAT do you need to press the SAT key once or twice to get this to work to select the HDMI?'
May have misunderstood and #1. was to show what (I thought) you had described, but now think you may have meant InputTv should be on SAT-shift-3, to go back to Tv mode?
Thanks for the explanation, that explains to me that the SAT button first changes mode, then does what ever is assigned to that key. The TV's-SAT button didn't work, because when physically pressing the SAT button, the first step was to change modes, as you just confirmed by telling me that it worked in 1 press, when it was SAT-SAT button.(One of the PVR's (FoxSat HD) is the device 'SAT' and requires Hdmi1).
Should have made it clear that #2 was chosen as an alternative, which selects Hdmi1 with one press of the SAT button, and works in any mode.
Thought it had not worked when Hdmi1 had been keymoved to TV's-SAT button - but find it does work, in #2, when Hdmi1 is keymoved to SAT's-SAT button.
The * indicates that any functions assigned to these keys are going to be keymoved, because the selected upgrade device mode, doesn't map them natively. Sometimes changing a TV upgrade to a CBL upgrade gives you more native keys, and less keys that are only available via keymoves. That really depends on the remote. Old JP1 remotes had a huge difference in the keys available between the upgrade device modes, while the more modern remotes include more keys natively in all the device upgrade modes.The titles of the device buttons and phantom buttons have a '*' symbol attached to them and are marked in red, and FF and Rew are also in red.
The special protocol tab, is controlled by the RDF. Typically there is only a grayed out Pause protocol in the dropdown of an unextended remote, although if the remote did device specific macros (DSM) natively, then DSM would be included in the dropdown too. A Pause protocol can usually be added with remote master or KeyMaster and then the Pause will be enabled. Otherwise the special protocols usually come bundled with an extender. While the pause protocol can usually be created for a remote without custom code, getting a remote to perform a DSM, LKP, DKP, or MultiPlex requires remote specific knowledge that is usually found/added when an extender is being developed.There is a special functions tab but after pressing New the page opens and there is a drop down box called 'type' which is empty.
If something has been entered in the first other boxes and ok, it says 'no special protocol found for type "null"'. Can anything be done with this please?
Edit:
When I looked at the RDF, I did see an entry for a multiplex, so I'll bet if you search, you'll find a Multiplex upgrade for this remote somewhere.
