Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Speech-To-Text commands for (mostly) hands-free play #30

Open
blamarche opened this issue Dec 26, 2018 · 8 comments
Open

Add Speech-To-Text commands for (mostly) hands-free play #30

blamarche opened this issue Dec 26, 2018 · 8 comments

Comments

@blamarche
Copy link

After trying this great app (thanks for making it open source) I was thinking this would be an amazing activity for long commutes or other activities where looking at/tapping on your device would be unwise. Is this something on the roadmap or has had any work been done to this end? If not, I may look into adding it if it would be merged in.

@onyxbits
Copy link
Owner

onyxbits commented Dec 26, 2018 via email

@ralphtrickey
Copy link

Out of curiosity, is that because of privacy concerns or battery/network usage? From my viewpoint, the privacy ship has sailed years ago.

I like the idea, but you'd have to flag a large area to the main screen to turn recognition on or off for a commute. I suspect that leaving it on constantly would drain the battery quickly as well as using up network bandwidth. Actually, you might be able to capture the button on a bluetooth headset to toggle the mic on and off with an inactivity timer.

My 2c,
Ralph

@onyxbits
Copy link
Owner

onyxbits commented Dec 26, 2018 via email

@blamarche
Copy link
Author

I can absolutely understand the concern with privacy!

For such a limited set of commands, I am fairly confident it could be done using a local STT engine and some common string comparison algos instead of uploading to a server first.

For example you'd rarely need to detect words other than the initial command followed by something likely existing within the past few text descriptions. With modern android permissions you don't need to ask for microphone permission until its enabled by the user. I'd imagine this setting would be off by default and just another checkbox next to the TTS option.

Since the primary use case example I proposed is a commute, I don't think battery life would be a major concern since you could have it charging and even potentially have the screen off entirely.

@onyxbits
Copy link
Owner

onyxbits commented Dec 27, 2018 via email

@blamarche
Copy link
Author

blamarche commented Dec 27, 2018

It seems you are determined to shut this down, as you keep coming up with new reasons. Its your project, so do as you will, but can you really not think of other use cases?

How about for the vision or mobility impaired? The TTS is a good first step, but that doesn't help someone type easily and those voice keyboards don't have ease of use the advantage of app integration would provide (like I said, to be able to correct commands based on contents of previous descriptions, auto-listen for next command, etc).

I guess the only option then is to fork and make a separate app? That'd be a real shame.

PS: Voice command is one of the safest machine-interaction methods for drivers on the road. Far better than those touch-screen controls they are slapping into every vehicle console these days. With voice command, this app wouldn't be significantly more distracting than an audio book or podcast or even just a regular phone call.

@onyxbits
Copy link
Owner

onyxbits commented Dec 27, 2018 via email

@blamarche
Copy link
Author

I mean no ill will towards you or this project, thats for sure. As I said before, I am thankful this project is open source!

To do the proof of concept you state adequately and have the local text recognition be accurate enough it would be just as simple for me to add it into to the actual TextFiction source, since it'll need the context of the fiction text itself. On its own, a local recognizer won't be good enough.

When I get some time, I will likely add this STT feature. If you won't merge it in, it'll be a fork with a separate listing in the app store, simple as that. Its not a threat, just a statement of fact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants