sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jan Stary <hans@stare.cz>
To: sox-devel@lists.sourceforge.net
Subject: Re: Adjusting write buffer for recording
Date: Mon, 12 Aug 2013 19:48:59 +0200	[thread overview]
Message-ID: <20130812174858.GA12108@www.stare.cz> (raw)
In-Reply-To: <CACB3T6GVDBOwPnH6tRxkO-0wHXUOgmgU6EN8ANd61npYgU3okQ@mail.gmail.com>

On Aug 12 10:28:51, shane.blaser@callfire.com wrote:
> Just to confirm there is no way to have rec not pause once it has started?

I repeat: call rec(1) without the silence effect.
That way, you record everything, continuously.

> I could use silence detection to start the recording then record everything
> until we see the set number of seconds of silence ?

Yes, that is also possible. But if you have the (unexplained) need
to process the audio signal in realtime, just let rec(1) do its writing,
and maybe postprocess the file later (trimming the silence).


------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk

      reply	other threads:[~2013-08-12 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 21:05 Adjusting write buffer for recording Shane Blaser
2013-08-11 17:10 ` Jan Stary
2013-08-12  5:11   ` Shane Blaser
2013-08-12  6:09     ` Jan Stary
2013-08-12 14:31       ` Shane Blaser
2013-08-12 16:03         ` Jan Stary
2013-08-12 16:16           ` Shane Blaser
2013-08-12 17:11             ` Jan Stary
2013-08-12 17:28               ` Shane Blaser
2013-08-12 17:48                 ` Jan Stary [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130812174858.GA12108@www.stare.cz \
    --to=sox-devel@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).