Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been doing some research on Speech Recognition Software and I'm having trouble finding any concrete evidence of folks saying that it works efficiently and has good functionality.
Like many of you if you type a lot and have been typing for many years your most likely growing tired of it.
With just looking at the 5 that are on that Arch page it's hard to decided which software to install.
The other thing is what type of head piece with a microphone to use?
W/O even looking (I'll look later)I'm almost willing to bet that there are so many different types of them that it's ridiculous.
John Kulp, who podcasts at Hacker Public Radio, uses Blather.
If you open the following link and use your browser's search page text feature, you will find several HPR episodes he's done in which he discusses speech recognition: http://hackerpublicradio.org/corresp...php?hostid=238
John Kulp, who podcasts at Hacker Public Radio, uses Blather.
If you open the following link and use your browser's search page text feature, you will find several HPR episodes he's done in which he discusses speech recognition: http://hackerpublicradio.org/corresp...php?hostid=238
I played with viavoice a long, long time ago. The headset was a vast improvement over any other means. Some have noise cancel tech that helps even more.
My moto x has a chip in it to assist with voice and I can say that it works a lot better than apples iphone does. Window phone was maybe equal to the moto x. So, if they can get that to work on a phone, I'd think there is hope of getting it to work on a computer. Opensouce is a different issue.
If I needed this for production then I'd look at Dragon and see if it would run in linux.
I played with viavoice a long, long time ago. The headset was a vast improvement over any other means. Some have noise cancel tech that helps even more.
My moto x has a chip in it to assist with voice and I can say that it works a lot better than apples iphone does. Window phone was maybe equal to the moto x. So, if they can get that to work on a phone, I'd think there is hope of getting it to work on a computer. Opensouce is a different issue.
If I needed this for production then I'd look at Dragon and see if it would run in linux.
If I'm not mistaken Dragon works only with Microsoft Windows:-
I'll look at headset's this evening and see what I can find.
He mentioned that Blather has a lot of dependencies and it was a bit challanging to get them installed but aside from that Blather looks like one of the top 3 in my list.
Blather BTW (didn't know) uses CMU Sphinx as it's backend-
For those of you watching Blather is not in the SlackBuilds repo-
I hope I can find out all of the dependencies w/o going through a painstaking compilation.
-::-Any thoughts on '(finding out the dependencies)' frankbell? <OR> jefro?-::-
For dependencies I usually try the build process and see what errors happen. Then fool with trying to get those build and see what errors exist then build those and 4 years later......
You can try the other open source projects for sure and see how far you get. Maybe someone else may have build some of the chain already. LQ may have someone that has it all already. Post on new thread maybe errors.
You can try the other open source projects for sure and see how far you get. Maybe someone else may have build some of the chain already. LQ may have someone that has it all already. Post on new thread maybe errors.
I think I'm going to go with one of the Logitech headsets-
I'll decide later which one I'll purchase later after I either install Blather or CMU Sphinx:-
This post is more specific to Blather, but is it okay if I add it to the thread?
I successfully ran Blather on Debian Jessie yesterday. I didn't get the QtGui version to work yet, but did get the Gtk gui operational.
I have contrib and non-free software available in my repos file. All the dependencies of Blather (with the possible exception of what waas needed for the Qt version to work) were satisfied.
I used a git version of Blather. No compiling was necessary, and I didn't "install" it; I used it directly from the source directory.
Here is a prototype of my commands.conf file. It's a bit crude but wanted to do some initial experimentation.
Quote:
#commands are key:value pairs
# key is the sentence to listen for
# value is the command to run when the key is spoken
hello world:echo "hello world"
#programs are opened in the blather terminal window, so the & is needed, otherwise blather stops "listening" until
#the program is closed
open pidginidgin &
open ice dove:icedove &
open ice weasel:iceweasel &
# These lines will print characters of the alphabet to the active window (e.g. a text editor, terminal window).
# Blather had a few problems recognizing certain
# letters, so I used the military phonetic alphabet for a few of them.
# Because blather appends the keyword to the command, a space is needed at the end of each line (xdotool will
# ignore the appended keyword)
# xdotool is available in the Debian repo and is independent from Blather
a:xdotool key a
b:xdotool key b
c:xdotool key c
d:xdotool key d
echo:xdotool key e
f:xdotool key f
guerilla:xdotool key g
h:xdotool key h
i:xdotool key i
j:xdotool key j
k:xdotool key k
l:xdotool key l
mike:xdotool key m
november':xdotool key n
o:xdotool key o
p:xdotool key p
q:xdotool key q
r:xdotool key r
sierra:xdotool key s
t:xdotool key t
u:xdotool key u
victor:xdotool key v
w:xdotool key w
x:xdotool key x
y:xdotool key y
zulu:xdotool key z
click left:xdotool click 1
click right:xdotool click 3
click middle:xdotool click 2
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.