sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "paul fellows" <4-werk@gmx.com>
To: sox <sox-users@lists.sourceforge.net>
Subject: Re: sound to sox to .txt to chatscript
Date: Tue, 30 Dec 2014 22:57:32 +0100	[thread overview]
Message-ID: <trinity-2c4f0cfa-2766-4019-94a3-ddaf10d1638d-1419976652211@3capp-mailcom-bs08> (raw)

Sorry Jan I should have replied quicker.
You wrote “Does that mean you want the *.txt file to be a text transcript of the speech?”
My answer is almost but not quite, I want the *.txt file to be a …............pattern transcript of the speech.
I want sox to transcribe a twentieth of a second length of microphone in put into a 32 bit binary pattern in a. .txt file.

By devied I mean splitting the mono input from the mic to stereo tracks that can be processed separately. Sorry if my switching between talking about tracks and files as the same thing caused any confusion.

fmiser asked “ You want the characters "b" "o" "o" "k" to be generated from the
sound of a voice saying "book"? My answer is no I ant to say 'book' and have it out put “b” “oo” “c”, after chatscript has done its work. 

Fmiser you are right about chat bots being far more complex than the simple pattern matching that I am proposing. but if you strip away all of this extra stuff, what you are left with is pattern matching.

Jan said “The signal itself carries that information. why do you need the echo, exactly?”
I will try to explain it like this. the sound coming in from the mic has all of the information about the sound at that instant. If you where to make an image that instant of sound, and stack it next to images of all of the proceeding instances, you would have a picture of how the sound had changed over time. A conventional speech to text system dose something like that but with out the pretty picture and uses statistical analysis to try to understand the sound. By adding the multiple echoes I will be adding in the information about how the sound has changed. Imagine just 100 samples per second each 32 bits in size and containing the information about how the sound had changed. Each of these 32 bit files should unequally pass the information on to the chatscript side of the project to print to the screen the letter or letters hat match the sounds

to look at this an other way. A sample contains its own information, but nothing about the samples that preceded it. the echoes smear the information across samples.

Sorry if that is still clear as mud. What I am trying to do with the echo effect is to convert the samples to parametric time, as opposed to real time. If you are not familiar with the idea this will sound like techno babble, if you are I have done both of us a disservice by underestimating you.

The reference to no clobber comes from the sox PDF. I read it and thought I was understanding it until I to the bit that said that the effect that stops the train has to be first. (???) I can ham out from the sox PDF what the bits of code might be, but dose any one know of a good sox tutorial on how the bits go together.

------------------------------------------------------------------------------
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
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

             reply	other threads:[~2014-12-30 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 21:57 paul fellows [this message]
2014-12-31 14:25 ` sound to sox to .txt to chatscript Jan Stary
  -- strict thread matches above, loose matches on Subject: below --
2015-01-01 18:52 paul fellows
2015-01-01 19:43 ` Jan Stary
2014-12-28 18:03 paul fellows
2014-12-29 22:18 ` fmiser

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=trinity-2c4f0cfa-2766-4019-94a3-ddaf10d1638d-1419976652211@3capp-mailcom-bs08 \
    --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).