From: Chris Angelico <rosuav@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: sox to chatscript
Date: Mon, 5 Jan 2015 03:31:43 +1100 [thread overview]
Message-ID: <CAPTjJmqPACTZ3WRgq9RhVDQVZLtVbCxfmkF7C7qkAvXidB161w@mail.gmail.com> (raw)
In-Reply-To: <trinity-663d44e9-8253-4e3e-a5e0-fac5ab00a8f3-1420387354336@3capp-mailcom-bs14>
On Mon, Jan 5, 2015 at 3:02 AM, paul fellows <4-werk@gmx.com> wrote:
> The nonsense that this would output is not a problem, provided that the sound /p/ as spoken by me produces the same set of patterns each time, and no other sound produces the same patters. Then it will do what I want. Chatscript will print the letter p.
>
What you're asking for is the entire pattern recognition code. Perhaps
it would be easier to describe this using written text, taking the
whole question of speech recog out of the picture. Would you expect
the pngtopnm program to be able to produce a file which has a unique
and consistent pattern for the handwritten letter 'p'? No, because
optical character recognition is not a part of pngtopnm's job. Plus,
handwriting is inherently messy (in the computing sense; though mine
is messy in every other sense too), so it's extremely difficult to
produce a perfect transcription.
You're asking for some fairly magical features here, and you'll do far
FAR better to look for a dedicated speech-to-text tool and see if you
can do it with that.
ChrisA
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
next prev parent reply other threads:[~2015-01-04 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 16:02 sox to chatscript paul fellows
2015-01-04 16:31 ` Chris Angelico [this message]
2015-01-04 20:31 ` fmiser
-- strict thread matches above, loose matches on Subject: below --
2015-01-04 17:47 Mike Hamilton
2015-01-04 13:23 Mike Hamilton
2015-01-03 15:57 paul fellows
2015-01-03 17:49 ` Jan Stary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPTjJmqPACTZ3WRgq9RhVDQVZLtVbCxfmkF7C7qkAvXidB161w@mail.gmail.com \
--to=sox-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).