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: Thu, 1 Jan 2015 19:52:24 +0100	[thread overview]
Message-ID: <trinity-fafd3448-00cc-43ae-abab-e607c64c4d02-1420138344004@3capp-mailcom-bs04> (raw)


Happy new year Jan and all.

Let me start by thanking Jan.
she is right 100 Hz is way to low. I made that mistake from thinking about the low rate of spoken words, typically less than 3 words per second. If I had gone on as I was it would not have worked. Somewhere in the sox documentation it says that phone companies use 8000Hz. So that will be my sample rate from now on. 

I will try to explain again from scratch, a '32 bit word' to mean the content of the particular sample I am talking about. For 'input sample' to mean an individual 1/8000 th of a second of the on going microphone input, recoded as a 32 bit word. And 'output sample' to mean an individual 1/8000 th of a second of modified input, recoded as a 32 bit word.

There are two uses of the word sample in sox so to be clear I mean, that 10 seconds of recording is 80 000 samples, if recorded at 8000 samples per second.

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

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

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

Subsequent modifications\
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. 

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

             reply	other threads:[~2015-01-01 18:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 18:52 paul fellows [this message]
2015-01-01 19:43 ` sound to sox to .txt to chatscript Jan Stary
  -- strict thread matches above, loose matches on Subject: below --
2014-12-30 21:57 paul fellows
2014-12-31 14:25 ` 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-fafd3448-00cc-43ae-abab-e607c64c4d02-1420138344004@3capp-mailcom-bs04 \
    --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).