Black Hole
May contain traces of nut
Discussion in this thread: https://hummy.tv/forum/threads/urc-1280-with-2-x-hdr-fox-t2.9661/ got me wondering what are the minimum buttons for a handset to still provide the essentials of HDR-FOX use. I have a vested interest: my supported user is now not using the PVR capability because (I believe) poor sight makes the Harmony 300 I provided intractable, and declining mental capacity means she can't even remember what button she is looking for.
The selection of buttons needs to be targeted at convenience without clutter, in other words is guaranteed to be a compromise between the two (with nobody agreeing on where that compromise is). However, I propose that no button is needed for a secondary function which can be accessed via a Menu button, and no set-and-forget function is needed unless it can't be enforced at boot by the CF.
I also think complications like bookmarks are dispensable for the target audience.
So, what's left:
** Vformat is only included because there is no other way to get at it. If CF could enforce it, we wouldn't need a button.
That's 43 buttons.
But the handset also needs to control the TV, ideally with macros for turning both on or off in such a way they can't get out of sync, and a means to select the source on the TV:
So now I have to find (or build*) a programmable RC with 45 easy-read high-tactile buttons and JP1 programming. Maybe, with a "shift" button, secondary functions could be assigned to the number buttons (so still be available for tech support), so SHIFT takes the place of VFORMAT.
* "Build" could mean using an existing JP1 handset as the basis, and giving it a new set of buttons.
Anyone find a flaw in this analysis?
The selection of buttons needs to be targeted at convenience without clutter, in other words is guaranteed to be a compromise between the two (with nobody agreeing on where that compromise is). However, I propose that no button is needed for a secondary function which can be accessed via a Menu button, and no set-and-forget function is needed unless it can't be enforced at boot by the CF.
I also think complications like bookmarks are dispensable for the target audience.
So, what's left:
- On/Off
- Numbers 0-9
- Menu
- Play/Pause/Stop/Record
- FF/RW/Skip-/Skip+
- Red/Green/Yellow/Blue
- Media
- Guide
- Left/Right/Up/Down
- OK/Back/Exit
- Info
- Vol-/Vol+/Mute*
- Ch-/Ch+
- Opt+
- TV/Radio
- Sub (or AD, according to the user's particular impairment)
- Vformat**
** Vformat is only included because there is no other way to get at it. If CF could enforce it, we wouldn't need a button.
That's 43 buttons.
But the handset also needs to control the TV, ideally with macros for turning both on or off in such a way they can't get out of sync, and a means to select the source on the TV:
- On/Off/TV/PVR
So now I have to find (or build*) a programmable RC with 45 easy-read high-tactile buttons and JP1 programming. Maybe, with a "shift" button, secondary functions could be assigned to the number buttons (so still be available for tech support), so SHIFT takes the place of VFORMAT.
* "Build" could mean using an existing JP1 handset as the basis, and giving it a new set of buttons.
Anyone find a flaw in this analysis?
Last edited: