FS#1291 - Key click
Attached to Project:
Rockbox
Opened by Björn Stenberg (zagor) - Tuesday, 29 April 2003, 14:44 GMT
Last edited by Björn Stenberg (zagor) - Thursday, 05 June 2003, 09:36 GMT
Opened by Björn Stenberg (zagor) - Tuesday, 29 April 2003, 14:44 GMT
Last edited by Björn Stenberg (zagor) - Thursday, 05 June 2003, 09:36 GMT
|
DetailsThis patch adds a crude key click by turning off and on the dac,
generating a short pop, every time a key is pressed. I have only tested this for the recorder, so I would appreciate feedback from player users. Is it useful? Could it be better? There's not a whole lot we can do about the sound, unfortunately. We can make several consecutive pops, making a longer sound. However we can not make a high-frequency beep, since the dac is controlled over a slow i2c link. The highest frequency possible only sounds like a coarse noise, so I opted for the single discreet pop instead. |
archos.mod
key_click.patch
This task depends upon
Closed by Björn Stenberg (zagor)
Thursday, 05 June 2003, 09:36 GMT
Reason for closing: Rejected
Additional comments about closing: Logged In: YES
user_id=1157
Since we can't make it work 100% (sometimes misses clicks)
the feature has only limited value.
Thursday, 05 June 2003, 09:36 GMT
Reason for closing: Rejected
Additional comments about closing: Logged In: YES
user_id=1157
Since we can't make it work 100% (sometimes misses clicks)
the feature has only limited value.
isn`t it possible to use one or more mp3-frames with the
appropriate sound for such?
i tried it and found, that sometimes it doesn`t click. e.g some
clicks are left out when browsing the dir
Yes, sometimes the click is not audible. This is because the dac is not
designed to click (in fact, it is generally undesirable). So you could say
I'm exploiting a dac bug that doesn't always happen. :-)
Inserting
mp3 frames in the running stream is rather difficult since data is
transfered with dma. Please ask on the mailing list for more detailed
technical discussion.
I like it! =) After a few minutes playing with it, I have
these comments:
- I would use keyclick in a "blind operation" mode, to
help in menu navigation. It is much less useful in this
regard if sometimes keypresses "miss" clicks (as discussed
below).
- I'd prefer no clicks on repeat (I know this just a
demo), personally
- Another use of "click" feedback I'd thought of was to
take the place of an "error beep" in the PC-world. It might
be implemented as a long-click, to distinguish from normal
click. Events that might generate error beeps would be:
trying to skip past last track in a repeat-off playlist,
trying to adjust settings past limit, etc.
- Also, maybe tie clicks to valid UI events rather than
keypress (more coding); so keypresses that are ignored
generate no click.
Just some thoughts. =) It doesn't sound pretty, but enough
to be usable, I think.
Since we can't make it work 100% (sometimes misses clicks)
the feature has only limited value.