Any table for the Key sets?

eddie_bowers · Post by **eddie_bowers** » Thu Feb 05, 2004 5:15 pm

Does anyone have a table that shows what buttons belong to which key sets? (PIP, Menu, Channel, Volume, Transport, Other).
Some are obvious, but others are not.

-Eddie

Mark Pierson · Post by **Mark Pierson** » Thu Feb 05, 2004 5:22 pm

They should be noted in the readme file.

JohnParks · Post by **JohnParks** » Fri Feb 06, 2004 1:45 pm

What are the advantages of key groups? Maybe for native code, but for upgades they seem like just something else to keep up with in debuging process. I mean couldn't key moves do the some thing more clearly?

johnsfine · Post by **johnsfine** » Fri Feb 06, 2004 2:04 pm

Key sets are the central aspect of the "HT" (Home theater) feature, so I think you're really asking what are the advantages of HT.

What I call "static HT" could be accomplished more flexibly and maybe more intuitively as a big pile of KeyMoves. HT has the advantage over that pile of KeyMoves that it needs less eeprom space.

An example of "static HT" is having one button you can press to select something like a device mode in which your transport keys operate your VCR, your volume keys operate your Amp, your channel keys operate your cable tuner, and your pip keys operate your TV.

What I call "dynamic HT" cannot be accomplished reasonably with a pile of KeyMoves.

An example of dynamic HT is having a device key for your DVD and another for your VCR and of course pushing either one selects the device for your transport keys (and probably other keys), BUT subsequently pushing another device key (such as TV) that has no transport functions, will leave the transport keys associated with either VCR or DVD, whichever was selected last.

I have a moderately large need for dynamic HT, since my remote controls two TV's, each of which has two VCRs connected and two (of the four) VCRs are identical. So when I press a TV device button, I don't want the remote to forget which of two VCRs I was using last, and when I press the button for the VCR that I have two of, I don't want the remote to forget which TV I was using last. All the devices have menu commands (that aren't used as often as basic commands) so pressing any device key selects the menu commands for that device.

Nils_Ekberg · Post by **Nils_Ekberg** » Fri Feb 06, 2004 2:08 pm

JohnParks wrote:What are the advantages of key groups? Maybe for native code, but for upgades they seem like just something else to keep up with in debuging process. I mean couldn't key moves do the some thing more clearly?

The advantage of key groups is with device button assignements. Example: On the Home Theater button of a remote you may want all of the cable buttons active for Menu, channel and power for cable, receiver for volume but for some reason you want the VCR transport buttons and TV Pip buttons available. With key groups you can do that. with something like this (depending on the extender)

M_CBL;C_CBL;O_CBL;V_RCVR;T_VCR;P_TV

JohnParks · Post by **JohnParks** » Fri Feb 06, 2004 9:28 pm

Thanks guys, I see your point. The urc-6131 probably does not qualify as a HT romote since it only has three groupings. Can these groupings be changed/increased? I don't recall seeing anything in the doc's about this with the 6131 extender.

Nils_Ekberg · Post by **Nils_Ekberg** » Fri Feb 06, 2004 10:22 pm

JohnParks wrote:Thanks guys, I see your point. The urc-6131 probably does not qualify as a HT romote since it only has three groupings. Can these groupings be changed/increased? I don't recall seeing anything in the doc's about this with the 6131 extender.

Any button could be used as an HT button and defined as such with the group commands.

Yes, it is possible to add more groups but from what I remember it was done that way to conserve buttons. Each button group takes 7 button hex values and there may not have been enough left in the 6131. If I remember correctly it was a choice of more group buttons or more devices and Hal went for the devices.