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: sound to sox to .txt to chatscript
Date: Sun, 28 Dec 2014 19:03:08 +0100	[thread overview]
Message-ID: <trinity-cc35bc48-9645-4fbe-98d1-305d68d654da-1419789788389@3capp-mailcom-bs05> (raw)

thanks to Eric Wong, hopefully his will be readable this time

I was looking for a sox forum I tried audacity and was directed here.
I do not know the etiquette of this site so I will just start begging for help.

The project I am trying to build is a speech to text system. 
The system as 2 parts: first a sox filter to convert the mic input into a binary file with a .txt label. The .txt file is the in put to another beautiful and free program called chatscript. Chatscript is designed to let people make there own chat bots, I am intending to use its most basic property. If the pattern of the input matches the pattern of the rule then output is the rules response. Or less abstractly, if the input pattern matches the rule for P then it prints the letter P.

what I need sox to do is.
A) use the key board space bar to mute and unmute the mic.
B) to take 32 bit samples of the sound.
C) to contain no clobber at first so I can generate the files to go into the rules to be matched against.
D) maximize The gain without clipping.
E) no dither or other noise.
F)  multi thread, to process the tracks in parallel.
G) divide this into 2 tracks, if possible one the inverse of the other.
H) using the echo function (not echoes) add multipal echoes to each track, these echoes should be at the same volume as the track and have no decay. It is these echoes superimposed on there original track that carry the information about how the sound is changing with time.
I) one track would have delays of 11, 17, 23, 31, 47 millisecond. And he other would be 13, 19, 29, 37, 53 millisecond.
J)  these 2 tracks are then converted into a single bindery file by using soxes multiplication option.
K) this is then given the .txt file name.txt

I may have made a mistake I saying no decay for the echo. What I want from the 11 millisecond echo is for the echo to happen once at its original volume after 11 milliseconds then not at all at 22 milliseconds. 

if you listened t his as a sound file it would probably sound bad, but hopefully it contains enough parametric information to allow for pattern matching.


------------------------------------------------------------------------------
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

             reply	other threads:[~2014-12-29  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-28 18:03 paul fellows [this message]
2014-12-29 22:18 ` sound to sox to .txt to chatscript fmiser
  -- strict thread matches above, loose matches on Subject: below --
2014-12-30 21:57 paul fellows
2014-12-31 14:25 ` Jan Stary
2015-01-01 18:52 paul fellows
2015-01-01 19:43 ` 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=trinity-cc35bc48-9645-4fbe-98d1-305d68d654da-1419789788389@3capp-mailcom-bs05 \
    --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).