Rockbox

Tasklist

FS#8083 - Voice feature for Accessibility : Speak current item, or WPS infornation on button press

Attached to Project: Rockbox
Opened by Bread (Calcipher) - Sunday, 04 November 2007, 06:31 GMT
Task Type Feature Requests
Category User Interface
Status Closed
Assigned To No-one
Operating System All players
Severity Low
Priority Normal
Reported Version Daily build (which?)
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I am proposing the inclusion of a "Speak current item, or WPS information on button press" function to Rockbox. I myself am a visually impaired rockbox user, and have a blind friend who also uses rockbox on his player(thanks to me). We both agree that such a feature would be a great improvement to the powerful accessibility features offered in rockbox. This feature would allow for anyone who can't see the display to know exactly what is happening on their player and be more comfortable and in control. I use the voice functions so I don't have to remove my player from my pocket for instance, and sometimes lose track of exactly where I am in the menus or other section.

As an example of a possible implementation method of mapping the function to a button, in the case of the Sansa e200 series players the record button which doesn't seem to have any use at the moment, could be the "speak" button. My friend and I both have e200 series players, so I am not familiar with other targets to give other suggestions of mappings.
This task depends upon

Closed by  Bj√∂rn Stenberg (zagor)

Reason for closing:  Fixed
Additional comments about closing:  Closing all feature requests.
Comment by Daniel Dalton (ddalton) - Sunday, 04 November 2007, 08:27 GMT
A couple of comments/questions:

Nice for blind users. What about sighted users? I think they will not accept something like this into RB. Most people who use rb are sighted. And most devs are. I think that this is a good idea for us if we're happy to patch our builds.
What do you think?
Remember there is always an argument when someone wants to change a keymap for a button or add one. I feel there are unused buttons on my player. But I won't start an argument here...

Also what should it speak in the WPS? Like should it put it in a list for you like:
-elapsed
-length
-track number of number of tracks
-Path
-ID3 info (everything on a separate line...)

Like that? Or should it just say it.
I prefer the first idea. Since hearing it all together will be quite annoying.

Re the repeating, should it just speak what ever was spoken last by the voice?
Like menu options, lists, settings and file/dirs?
Comment by Bread (Calcipher) - Sunday, 04 November 2007, 08:49 GMT
You have some good points Dalton, I understand that this would not seem so appealing to sighted users, although I myself am sighted and would still use the feature to control rb without looking at the display.

As per your key map comment, I agree that it is not something that all users will use, so I am suggesting making this an optional mapping, maybe an alternative mapping that can be selected in settings menu. What I was suggesting the function do in a menu or file browsing or anywhere where voices can prompt the user what they have selected at the moment is to re read as you said. In the case of the WPS, I made the comment vague since information available in the WPS screen is dependent on what WPS your using, I noticed some include information that others do not. Are you suggesting that each item read off the WPS screen have a tag like "playing: song 1" "by: artist" " x minutes and x seconds of x minutes and x seconds" "next: song2", maybe the items read in WPS voice support could be selected in settings, so for example if you don't care what genre the song is, or don't want to hear the vol level, you can opt to have certain fields excluded from being read. If I knew how WPS files group the information they display... what I mean is if the different information fields are a uniform set of possible pieces of information that can be displayed, then the "speak WPS" function can be filtered(does that make any sense?). I would say this WPS aspect is much more complex if we have it filter items to include or exclude, or if people like your idea of an item to read menu list(to me this sounds like an extra step or two that are not so convenient). Well if you need any clarification on what I'm trying to convey, be my guest and ask away.

Thanks for the interest and quick response!
Comment by Steve Bavin (pondlife) - Sunday, 04 November 2007, 11:26 GMT
I'd think that any "speak WPS" function should produce output based on the fields included in the current WPS, in the order that they appear. This keeps the voice and display UI consistent, and allows full customisation of the fields for voice users.

On that point, I'd like to emphasise that there are probably many voice users who are not blind, or visually impaired; it's useful when driving, or using a non-LCD remote control, or simply when the DAP is in your pocket.

I don't think there are many key mappings left on the WPS, but Voice WPS could be included as a context menu option.

OR maybe it could be achieved by voice support for Show Track Info?
Comment by Daniel Dalton (ddalton) - Monday, 05 November 2007, 04:39 GMT
My opinion on this:
-When in the wps if a blind user wants access to some id3 info or track duration/elapsed time they can go to track info.
One of sdoyon's patches do this not sure which one but it shouldn't be hard to find.
I did think a button to tell you the elapsed time, length and title could be useful but I think this would be considered a waste of a button...

In menus and stuff. Hmmm its a good idea but I doubt it would be accepted. I guess it could be nice in noisy environments but I guess we would have to have this sort of thing in an unafficial build because we don't like configurable buttons in rockbox.
And sighted devs/users wouldn't like it. They would have no use for it.

And could a combination of buttons work? Does it have to be easy to press?
Comment by Steve Bavin (pondlife) - Monday, 05 November 2007, 08:39 GMT
Hi Daniel,

It's more likely to get into SVN if it uses a menu than a button.

>> And sighted devs/users wouldn't like it. They would have no use for it.
You are mistaken; sighted users (e.g. me) would like this too, for the reasons I gave above.

>> And could a combination of buttons work?
Different targets allow different combinations of buttons. For example, the H300 hardware allows combinations of PLAY+another key, but that's it. Many (if not all) of these combinations are already used. I don't know what restrictions exist on other devices.
Comment by Daniel Dalton (ddalton) - Wednesday, 07 November 2007, 05:56 GMT
> It's more likely to get into SVN if it uses a menu than a button.

How would a menu work? I don't quite understand.
What would be in the menu. One part of this is to do with the wps and
the other part is to do with repeating stuff that was just spoken.

>
>>> And sighted devs/users wouldn't like it. They would have no use for it.
> You are mistaken; sighted users (e.g. me) would like this too, for the reasons I gave above.

Sorry. I meant to say a lot of people don't use voice and this would be
a waste of a button to them. Yes it could be useful but a button for just voice
I can't see been accepted.

>
>>> And could a combination of buttons work?
> Different targets allow different combinations of buttons. For example, the H300 hardware allows combinations of PLAY+another key, but that's it. Many >(if not all) of these combinations are already used. I don't know what restrictions exist on other >devices.

Yes so we could use:
-play + rec
-play +ab
-play + navi (Not sure actually)

And maybe others.
I'll just have to play around.


what exactly do you think this should have?

Comment by Steve Bavin (pondlife) - Wednesday, 07 November 2007, 07:06 GMT
For a menu, I meant as an option in the WPS context menu. "Read WPS", maybe, which speaks everything on the current WPS and immediately returns to the WPS. The option would only appear if voice menus are enabled, and perhaps could be the first entry.

Personally, I'd be happy if track info was voiced.

Comment by Peter D. (PeterD) - Saturday, 29 March 2008, 12:34 GMT
Adding a "read WPS" option to the context menu seems like a good idea to me.

Also voicing "context menu" once before starting to voice the menu items would be a plus. Perhaps the cursor should be allowed to scroll off the menu to the menu title so that it can be re-read?

Perversely many menu items are currently (r16863-080328) spoken wrongly. I'll raise a separate bug report if I can't find any existing reports about it.
Comment by Marc Guay (Marc_Guay) - Saturday, 29 March 2008, 14:40 GMT
Regarding the wrong-spoken menu items, try updating your english.voice file.
Comment by Peter D. (PeterD) - Sunday, 30 March 2008, 06:39 GMT
Doh!

It is much better now. Thank you Marc.

I will not raise a bug report about that, but I am thinking about raising a feature request for rbutil to warn the user after a code update that old voices are now wrong and should be updated as well.
Comment by Peter D. (PeterD) - Sunday, 30 March 2008, 07:14 GMT
Back on topic...

How about while playing a long select brings up the context menu. (Current behaviour.) The context menu should look the same as now except for two changes.

First, like pondlife suggested. If voicing is configured on then, an extra entry "read WPS" appears as the first menu item.

Second, the cursor could start on the menu title (rather than the first menu item) and speak, "menu title, context menu". Then moving the cursor down to the first item it should speak, "menu item, read while playing screen".

Possibly the cursor should only be allowed onto the title when voicing is enabled.

The scroll bar should definitely stay the same as now and the the menu title should definitely stay at the top of the screen as the menu items are scrolled.
Comment by Bread (Calcipher) - Monday, 31 March 2008, 01:52 GMT
I'm very glad to see some activity and interest into this suggestion, I see maybe I had not thought out as clearly as it should have been, but the comments are definitely helping in coming up with something useful. I do like the idea of the optional add on to the context menu, and as long as all the menus are read things would be great, I see how the use of the context menus own title would help in making things much easier to navigate, and for allowing these voice options to work with less changes.

if there are any actual changes in RB reflecting these options I'd like to know about them, I don't regularly update my builds unless theres something I'm specifically interested in, to avoid those times where wierd glitches and broken functions randomly get by hehe, so when I have a build that works well I stay with it as long as I can.


Thanks to all of you, and keep us all posted.

Loading...