I also forgot device select buttons that light up. That is far from a critical feature, but I found it convenient on the few models of remote I've used that had it.
The problem it is solving is that remotes are modal and users forget which mode the remote is in. Remotes such as the 8910 try to solve that by displaying the mode in the LCD. But that is harder to see and takes up more space than having device select buttons that light.
It's especially convenient when you have punch through or my system mode or keymoves etc. complicating device select issues. In simple volume punch through the user may press DVD then vol+ and the vol+ command goes to the RCVR, not the DVD. He probably isn't confused, but having the RCVR button light as he presses vol+ helps. In more complicated Transport Punch Through, the user may press TV, then FF. Where did the FF go? VCR? DVD? PVR? Having the right button light up really helps.
A Plan to provide a new brand of JP1/JP1.2 Remotes
Moderator: Moderators
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
Many OEM remotes have around 50-60 buttons. Sharp Aquos TV has 70, if I recall. One of the two Onkyo remotes mentioned hereyesok wrote:Could you tell me examples where you need more than 75 keys learning memory?
http://www.hifi-remote.com/forums/viewtopic.php?t=5905
claims learning space for 150 commands and, if I recall, the number of buttons on the remote is around 70. Mine run 45-60.
BTW, There are normally more functions than hard buttons to learn. Due to multiple devices, as John mentioned, and various mode switches on top of that. Two, three, trips to Circuit City for learning 20 buttons is a pain. Part of the capacity issue can be solved by no restrictions on memory allocation as we currently have.
Precisely. And so cat can't knock it off that easilyjohnsfine wrote:I assume flat bottom is so it will be very stable if you use it on a table rather than in your hand
YESSSS! Lighted device button is sufficient, and a better approach than the LCD device display (except for the setup code feedback).johnsfine wrote:I also forgot device select buttons that light up....The problem it is solving is that remotes are modal and users forget which mode the remote is in. Remotes such as the 8910 try to solve that by displaying the mode in the LCD. But that is harder to see and takes up more space than having device select buttons that light.
Some round, some square, some triangles pointing up, down and sideways, some big some small, some stars, or crescents and possibly numbers (like on the 7800) while looking goofy are very easy to use in the dark. When grouped well, it could be a gem.yesok wrote:What shapes would you recommend for the buttons?
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
-
classicsat
- Posts: 279
- Joined: Fri Feb 20, 2004 2:24 pm
A commercially available programmer, sold alongside the remotes, with included professional software to set up the remote and create and load upgrades, macros, keymoves, and such. The remote wouldn't learn (well it could), the programmer would have an IR eye and learn for you. Learns could be distilled to simple or complex upgrades.yesok wrote:Hello Jeff,
Regarding 6)PC Programmability, any specific requirements other than current software implementations?
Best regards,
Yesok
I need to have a skip back/forward. I really liked my 8017, and kinda like my 8910. My 6800 is a bit awkward, but tolerable. I am also a fan of the TiVo peanut.
All keys available on all devices.
If and LCD, let the user program what the device shows up on the display.