Hi Steve B,
Currently, I don't use the beep feature because of its slow reaction speed
after pressing a button. It's off here. But there are situations where it
would be very useful to have, where it has not been implemented yet. Of
course, moving the beep code away from the play routines into the button
handling could be benificial because of the time difference that will
probably result in, but there's another use.
I understand that playback and recording are mutually exclusive, i.e. you
can have one, but not the other at the same time. This makes implementing
the beeps where I and many others want to have them, somewhat complicated I
guess, but I'm not a developer so I don't really know.
To answer your question: I don't personally need differently pitched beeps
for different buttons I press. A good use for beeps where they are not yet
implemented though, is in the recording screen while the rec monitor is on.
We, blind folks, have no feedback on whether the device is recording or
pausing. I screwed up several live recordings because of this. I have to go
into the rec monitor, and press play to start recording. Pressing play again
pauses, pressing it again resumes recording etc.
It would be great if the device would issue a beep, just after it has gone
into pause mode. To start recording, I don't need to hear anything
personally. But pausing is important to be aware of, so that you don't
accidentally record what you intended to leave out, and vice versa. Hearing
a beep when going from rec into pause mode, would be really helpful. Even if
the rec monitor has to be turned off for the time the beep is sounding,
would not be a problem in my opinion.
Do you know if something can be done about this, or would you find it worth
----- Original Message -----
From: "pondlife" <pondlife_at_ntlworld.com>
Sent: Tuesday, June 12, 2007 5:06 PM
Subject: Do you use the BEEP feature?
>I use the beep feature whenever I'm operating the player while driving.
> It's useful as confirmation that I actually pressed the button, especially
> as crossfade can result in quite a delay before the track skip is audible.
> I'd rather like the beep to operate when any button is pressed (well,
> a shorter "click"), but it's currently part of the playback code (rather
> than the button code), so maybe I've got the wrong end of the stick about
> this and this isn't the main use for this feature.
> So could all users of this feature explain why they use it and whether
> feedback on all keypresses would be useful. (Also would different pitches
> of short beep for different buttons be useful?)
> Steve B
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.472 / Virus Database: 269.8.13/844 - Release Date: 6/11/2007
> 5:10 PM
Received on 2007-06-12