sox-users@lists.sourceforge.net unofficial mirror
 help / color / Atom feed
From: Jan Stary <hans@stare.cz>
To: sox-users@lists.sourceforge.net
Subject: Re: Duration of recorded file is longer than recording time using SoX
Date: Sat, 28 Dec 2019 16:52:19 +0100
Message-ID: <20191228155218.GA41251@www.stare.cz> (raw)
In-Reply-To: <0709217c-c34d-2ab5-19bb-bd8b44b8e066@websterling.com>

> > Also, a command line like that will not stop recording its input
> > just because the other side has stopped producing output
> > (as opposed to reading a file as input). So how exactly
> > is the above SoX process terminated?
> SoX is terrminated with Ctrl-C

In that case, the sox recording will be as long
as the time between start and the ctrl-c termination
(give or take a buffer or two).

> > > > > In your "too long" wave file, does it start with 1h 6m of something
> > > > > else, or end with 1h 6m of something else?  Or what?
> > > > The wave file contains what was recorded, nothing extra. It is
> > > > 'stretched' to the longer duration.

What do you mean by that. Does it play slower?
Then I would suspect a sample rate mismatch
- hard to tell without actual soxi  or sox -V output.

> > How can it "contain what was recorded, nothing extra"
> > and at the same time be of different length? Is it the
> > rate change? That is, are you recording a 6kHz channel
> > at the specified rate of 6kHz?

Jan



_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

      reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16  2:39 George S. Williams
2019-12-16 16:14 ` Jeremy Nicoll - ml sox users
     [not found]   ` <f1382121-d632-9252-17a8-e7baed8913f2@websterling.com>
2019-12-16 20:53     ` Jeremy Nicoll - ml sox users
2019-12-25 21:23       ` Jan Stary
2019-12-26  1:02         ` George S. Williams
2019-12-28 15:52           ` Jan Stary [this message]

Reply instructions:

You may reply publically 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=20191228155218.GA41251@www.stare.cz \
    --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

sox-users@lists.sourceforge.net unofficial mirror

Archives are clonable: git clone --mirror https://public-inbox.org/sox-users

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.audio.sox
	nntp://ou63pmih66umazou.onion/inbox.comp.audio.sox
	nntp://news.gmane.org/gmane.comp.audio.sox

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git