Why Can't I Define 14 Keys in an LKP Setting?

[Kruskal]

I'm using Extender 3 2K URC-8811. When I tried to save an LKP definition with 14 keys, I got the message:

The total number of entries in both lists cannot exceed 14

Ideas?

Thanks -- Vincent

[Capn Trips]

Yeah! My first idea is that you probably cannot have that many buttons in your LKP sequence!

But seriously, from the 8811 ex 3 LKP readme:

First and second command sequence:

The keystrokes expressed by keycodes in hexadecimal. The first
command sequence is for a shorter press or a single press, and
the second is for a longer press or a double press. The first
sequence can be up to 7 keystrokes long, and total of the both
parts can be up to 12.

So you're already one over the advertised number!

If you REALLY need such a long sequence, then create a macro on an unused key (a phantom or x-shifted button somewhere) and use the LKP to simply call that macro.

[Kruskal]

Yeah! My first idea is that you probably cannot have that many buttons in your LKP sequence!

But seriously, from the 8811 ex 3 LKP readme:

First and second command sequence:

The keystrokes expressed by keycodes in hexadecimal. The first
command sequence is for a shorter press or a single press, and
the second is for a longer press or a double press. The first
sequence can be up to 7 keystrokes long, and total of the both
parts can be up to 12.

So you're already one over the advertised number!

If you REALLY need such a long sequence, then create a macro on an unused key (a phantom or x-shifted button somewhere) and use the LKP to simply call that macro.

So the app says the max is 14 and its documentation says its 12. The reality is 13 -- absolutely correct on average

You seem skeptical that I would need as many as 14. My use is really quite modest. The key selects by SKP or LKP between to device modes -- actually a home theater mode for a device and a raw mode for the same device. There are six key groups to define, so that is 12 already. In this case, each sequence needs a sevenths phantom key press to select whether Power will be for the TV or native. So that's 14.

I'll take the solution to move some of the keys to sub-macro. But it's pretty yucky in this case -- there is no natural place to break up M_, T_ etc.

Thanks -- Vincent

[The Robman]

You probably already have the macros that you need programmed to some of the device buttons, so couldn't you use those in the SKP/LKP macros to reduce the number of steps?

[Capn Trips]

Actually, I'm NOT skeptical of the need for 14 steps. But I agree with Rob, that in most cases - including mine - I keep the majority of "common" sequences, like device definitions (button assignments), assigned to their own macors, and simply invoke them in the LKP where/when needed. Even if then you have to add one or two "modifiers" to that sequence. It usually ultimately ends up saving space, and making the LKP easier to keep track of.

[Kruskal]

You probably already have the macros that you need programmed to some of the device buttons, so couldn't you use those in the SKP/LKP macros to reduce the number of steps?

I had no macro calls on my device buttons -- just six key group selections. Then I added device-specific home theater modes by defining a LKP macros with six keys on each branch and calling those macros with the device keys. Then I wanted to break out Power from its key group, so each device definition had to call a key to define the Power key mode -- TV Power or Device Power. That upped the key count on the LKP to 2(6+1)=14.

Any idea why the error message says I can have 14 even though I can't?

Thanks -- Vinent

[Capn Trips]

You know, at this point, I wouldn't get hung up aobut the number (12, 13, or 14). This is how I would structure your workaround. Put your basic device selection macros on xshift-device buttons. Then build your LKP calling on that for the short sequence, and calling on that, followed by any modifications in the long sequence. e.g.:

macro on xs-TV: P_TV; M_TV; C_TV; V_TV; T_TV; O_TV

LKP on TV: Short = xs-TV; long = xs-TV, V_RCVR, T_DVD

That makes for a pretty short LKP sequence, leaving you room to throw in a power on sequence as well, if you need it.

Just my 2 cents.

[Kruskal]

You know, at this point, I wouldn't get hung up aobut the number (12, 13, or 14). This is how I would structure your workaround. Put your basic device selection macros on xshift-device buttons. Then build your LKP calling on that for the short sequence, and calling on that, followed by any modifications in the long sequence. e.g.:

macro on xs-TV: P_TV; M_TV; C_TV; V_TV; T_TV; O_TV

LKP on TV: Short = xs-TV; long = xs-TV, V_RCVR, T_DVD

That makes for a pretty short LKP sequence, leaving you room to throw in a power on sequence as well, if you need it.

Just my 2 cents.

I did pretty much what you suggest. I took the key group selectors which always stay the same, whether home automation or not, out into a separate DSP.

My interests at this point are:

1- To vent and defend my frustration with having to beak up such a naturally contiguous sequence as selecting six key groups.

2- To get the bugs properly reported. Bugs: the max in the documentation, the max in the error message or both.

Thanks -- Vincent

[ElizabethD]

IR's old message is not correct. See Hal's, and only Hal's replies here http://www.hifi-remote.com/forums/viewtopic.php?t=4350 to settle the 12,13,14 issue.
Technically, it depends whether you count bytes available to the user or all the bytes in the keymove (15), and then there's the issue of the meaning of 'exceeds'

[Kruskal]

IR's old message is not correct. See Hal's, and only Hal's replies here http://www.hifi-remote.com/forums/viewtopic.php?t=4350 to settle the 12,13,14 issue.
Technically, it depends whether you count bytes available to the user or all the bytes in the keymove (15), and then there's the issue of the meaning of 'exceeds'

I don't see the meaning of 'exceeds' to be questionable.

Thanks for the reference -- Vincent