Re: sound to sox to .txt to chatscript

[Jan Stary <hans@stare.cz>]

On Jan 01 19:52:24, 4-werk@gmx.com wrote:
> Let me start by thanking Jan.
> she is right 100 Hz is way to low.

he.

> 1) the microphone picks up the sound and the hardware converts it to digital.
> 2) sox then tells the computer to treat the input as 32 bit words, one to describe each 1/8000 of a second.
> 3) these input samples are then processed by sox to produce the output samples.

Up to here, that's a pretty standard recording scenario.
rec -b 32 -r 8k

> 4) after 54 milliseconds these output samples will contain information from the current input sample plus those from 11, 13, 17, 19, 23, 29, 31, 37, 47 and 53, milliseconds erlaer.
> That is what the echoes are for.

I still have no idea why you want to do this at all,
let alone why you want it to be precisely 11, 13, etc.

> 5) each output sample is re-branded as *.txt

What do you even mean by a sample being "rebranded as *.txt", exactly?

> processing as describe in the original submission.
> what I need sox to do is.
> A) use the key board space bar to mute and unmute the mic.

SoX has no say over the spacebar.

> B) to take 32 bit samples of the sound.

rec -b 32

> C) to contain no clobber at first so I can generate the files
> to go into the rules to be matched against.

What clobber?
What rules?

> D) maximize The gain without clipping.

gain -n

> E) no dither or other noise.

-D

> F)  multi thread, to process the tracks in parallel.

What "tracks", and why does that imply "multi-threaded"?

> G) divide this into 2 tracks,

Divide _what_ into 2 tracks?

> if possible one the inverse of the other.

Why?

> H) using the echo function (not echoes) add multi pal 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.

The original soundwave already contains precisely thta information,
woithout superimposing any echo.

> I) one track would have delays of 11, 17, 23, 31, 47 millisecond.
> And he other would be 13, 19, 29, 37, 53,, millisecond.

Why?

> J)  these 2 tracks are then converted into a single bindery file
> by using soxes multiplication option.

What "multiplication option"?

> K) this is then given the .txt file name.

You can give any file any name you want.
What does the "txt" have to do with anything?


I can see very little point in trying to help you further
unless you answer all of these questions in detail.

	Jan


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