Rockbox mail archiveSubject: Re: roadmap to blind Rockboxing (need an audio amateur/speaker)
Re: roadmap to blind Rockboxing (need an audio amateur/speaker)
From: Rocker <rocker_at_shaw.ca>
Date: Wed, 25 Feb 2004 21:18:09 -0700
With respect I disagree. I would rather have greater access to the menu
options and sub options buttons etc then being able to adjust on the fly.
With all the great features that rock box offers, you pretty well just need
to set your options prior to playing or recording anyway.
----- Original Message -----
From: "Aman Singer" <aman_at_asinger.net>
To: "'Rockbox development'" <rockbox_at_cool.haxx.se>
Sent: Wednesday, February 25, 2004 9:22 AM
Subject: RE: roadmap to blind Rockboxing (need an audio amateur/speaker)
I'd only have this idea done if it's the only way to make the menu
accessible. The best situation would be that a user could adjust options on
the fly without resort to the docs except to find out what the options do.
If that is impossible, then I think the below idea about beeps is a good
From: rockbox-bounces_at_cool.haxx.se [mailto:rockbox-bounces_at_cool.haxx.se] On
Behalf Of jobarjo
Sent: Wednesday, February 25, 2004 10:49 AM
To: Rockbox development
Subject: Re: roadmap to blind Rockboxing (need an audio amateur/speaker)
as I suggested on another thread, I propose a much more generic and simple
solution for blind people (although less confortable)
Recording all the menu names in a file is not easy to maintain unless it is
done automatically with an offline speech synthesizer.
If someone adds a new menu entry, it would be difficult to have all messages
updated in all langages.
If you record only english numbers from 0 to 9 plus a beep, you can have a
generic and simple "display for the blind".
Eventually, it is possible to translate only these numbers.
A little simple protocol can then tell you where you are in the menus:
for example, "beep 1" tells you that you are on the root menu over choice
"beep 3 5" tells you that you are in menu 3 and submenu or choice number 5
"beep" tells you that you are out of config menu
Of course you have to read your doc to navigate...
It might also be possible to do something similar to tell where you are in
the song folder hierarchy:
"bop 2 point 1 6 point 2 5" would tell you are in folder 2 subfolder 16 song
----- Original Message -----
From: "[IDC]Dragon" <idc-dragon_at_gmx.de>
Sent: Wednesday, February 25, 2004 9:24 AM
Subject: roadmap to blind Rockboxing (need an audio amateur/speaker)
> there have been some understandable requests for blindly operating
> This is of course useful to handicapped people, but also in a car.
> As a developer, I have the following picture in mind:
> Speech synthesis is not an easy option, way too complex, since we already
> can play mp3 audio. Recently I've added playing from memory, mainly for my
> video plugin, but also with an eye on UI support. My suggestion would be
> little mp3 clips for the language IDs, then have some script tie them all
> together to one big (bitswapped) file which includes an index. This could
> be a part of the build process. This file has to fit into the mp3 buffer,
> about 1.6 MByte on regular 2 MB boxes. Currently we have 335 entries, if
> takes a one second clip that means we can use up to 40kBit/s. More if we
> into account that not all language IDs are needed. Voice is mono by
> or 16 kHz should be sufficient.
> OK, once the big file is there, it needs to be loaded into the mp3 buffer
> startup and every time you stop your music, because the normal playback
> trashes it. Loading this takes less than a second (excluding spinup) with
> recent speedups. We can have the UI talking only if we're not playing (or
> recording), this is the limitation.
> I would implement the changes to the menu/screen code to play what's under
> the cursor, if somebody else does the authoring of the clips. I am no
> amateur (don't even have something that deserves the name microphone), and
> don't want to hear _me_ talking out of your box. This need some stamina
> reproduceability, some more clips will be needed as Rockbox evolves along.
> Some help on the scripting would also be appreciated.
> Any takers, can we form a team?
> We need nicely trimmed clips of what's in "english.lang". I suggest naming
> the clips like the LANG_xx ID, e.g. "LANG_DELETE.mp3". This makes it easy
> a script. They should not contain any ID tags, don't waste space on this.
> suggest keeping the original .wav's, so we can re-encode with a sample
> bit rate that just fits. The clips should have a little fade in/out, to
> clicks, but no silence at the begin or end, to avoid latencies. Maybe
> is some kind of push-to-talk tool that records and does the trimming and
> fading more or less automatically?
> Plus, this would be a good time to merge the "classic" talkbox patch, if
> want this in the main cvs.
> And I have in mind to delay the file opening for recording until the
> runs full for the first time. This delays the disk spinup and makes the
> internal mic useable for clips that are shorter than the buffer.
> (Phew, when will I ever complete all my other stuff: the JPEG viewer, the
> all-in-one video converter tool, my car stereo integration, remote control
> plugins, etc...)
> GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...)
> jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel
Received on 2004-02-26