Talk:Recorder III:functional-spec
From The Neuros Technology Wiki
Audio Playback better support AAC and Ogg
Can we support higher than 16X on the FF? If you've ever not had a bookmark and had to get to an hour into a movie, 16X can seem pretty slow.
-- Yes, we can support much higher FF speed/step. mgao 07:48, 29 Jan 2006 (CST)
Contents |
[edit] Comments on Remote Control
[edit] on/off
Power should be just for the TV for several reasons, first given timed recordings, the unit really should not "turn off" from a consumer perspective. This is typical behavor of PVRs. Second, the shutdown and bootup is long and not what consumers expect of a CE device, we're better off just having an automatic sleep power saving mode.
[edit] Presets
These send a fixed signal (not programmable at the remote) to the R3 and the user can program certain shortcuts on the R3, like to play a given playlist, etc. Hopefully you can assign this with an Xi menu.
[edit] Channel
User should typically not be required to manually change channel on tuner, but in the case that they are, they would be required to use the remote that came with the tuner.
[edit] video source
do we really need this? Can't we auto-detect? Alternately, we should do this from the menu selection since it won't be done very often.
[edit] numeric input
we'll need some input scheme for alphanumeric. what should * and # be used for? We should print something on the remote for these if we know.
Sophia>How will this work? Press the key for one time, it shows A. Press it again, B is shown. Just like the mobile phone.
Or Press the key one time, A, B, C all show on TV and then the user use the nevigation buttons to choose the appropriate letter. Which way will the numeric keys work?
[edit] display
do we really need this? Can't we just have any key bring this up and have it time out relatively quickly?
[edit] press and hold
I'm not entirely clear on how this typically works, but I would guess that holding typically sends out a repetitive signal of a press and hold, I guess we can sense this at the R3 and interpret it as a press and hold, but it would be better for the remote itself to vary the signal if press and hold v. just press and release. --mgao
The problem with sending a single signal for when press and hold is initiated and when released is that if the reciever misses the release signal, the device will continue to act as if the button is still held. I think this will be very frustrating for users. I think we should send out the continuous signal and the OSD should know to interpret the continuous signal. i.e. if it sees the continous signal (with the exact continuous timing of signal) it will know its being held rather than pressed repeatedly and it will take the action according to that.
--JoeBorn
The remote can send the continuous bit not just the repetitive signal when press and hold. We need to defind how long after press and hold the remote should send the continuous bit. Taking the wrong judgement of the press and release vs press and hold into consideration. --slee
ok, I modified it, after 1 second, we can send out the "continous bit" repeatedly. If 1 second turns out to be too short, then the device firmware can compensate for it. I think this is a good setting for the remote. Unless anyone has an objection, let's finalize on that. --JoeBorn
