Rockbox mail archiveSubject: RE: Voice UI on iRiver H320
RE: Voice UI on iRiver H320
From: Nick Allan <nallan_at_wdev.net>
Date: Sat, 3 Dec 2005 15:55:13 +1100
I installed rockbox on my iriver h340 last week and for the most part it
works fine. The rockbox developers have done a fantastic job to make
something that won't run tts work for vision impaired users.
Having not used a previous player I'm not sure exactly how much is supposed
to speak. Ie I've noticed a few things
1. when setting options pressing right arrow to actually open a particular
option, the voice UI doesn't say the current value, you have to up and down
arrow to find that out.
2. At one point the voice ui was speaking while music was playing, this was
good. It even seemed to lower the music volume while speaking. For some
reason I now need to press stop before I get speech back.
3. When it did speak during playback, I had it on spell filenames, I
noticed that the background music volume would lower and raise between each
letter spelled. I think it would be better to lower the background volume
spell the entire filename and raise the volume again.
4. I've noticed various items in the menus that do not seem to have a voice
string attached, as I'm blind I don't know exactly what they are, but I
could go through and write down what they are between if that helps.
1. I've created .talk files for all directories and files. It would be
fantastic if rockbox could interupt speaking of the talk file if I arrow
passed it. I might want to scroll quickly through a list and at the moment
I have to wait for a .talk file to finish playing before the next one
From: rockbox-bounces_at_cool.haxx.se [mailto:rockbox-bounces_at_cool.haxx.se] On
Behalf Of Linus Nielsen Feltzing
Sent: Saturday, 3 December 2005 10:38 AM
Subject: Re: Voice UI on iRiver H320
Jani Kinnunen wrote:
> Hi there,
> Does the Voice UI already work on the iRiver H320? I'm sorry if
> someone gets annoyed about this question, but I had to ask it.
To be honest: I don't know. I can't think of a reason why it shouldn't.
Received on 2005-12-03