From: Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk>
To: sox-users@lists.sourceforge.net
Subject: Re: Duration of recorded file is longer than recording time using SoX
Date: Mon, 16 Dec 2019 16:14:08 +0000 [thread overview]
Message-ID: <87d93d9e13fb4fe46d7ecd8f74e3876a@wingsandbeaks.org.uk> (raw)
In-Reply-To: <d39859c7-5b7d-afb5-a26a-8da9d234a64c@websterling.com>
On 2019-12-16 02:39, George S. Williams wrote:
> I'm using SoX on Centos 7 to record the audio output from GQRX, a SDR
> application. I've selected Monitor of Built-in Audio Analog Stereo
> from the Recording Tab of the Pulseaudio Volume Control. I'm trying to
> save a .wav file with a sample rate of 6k. I'm using the command
>
> |sox -t pulseaudio 2 --rate 6k --channels 1 test.wav |
Does the presence of the 'pipe' character before "sox" mean that audio
was being generated by a previous command?
If so, although you may think you terminated the recording after a
certain time, maybe that program still sent data to sox? Or maybe
sent data before you though you started the recording?
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?
--
Jeremy Nicoll - my opinions are my own
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2019-12-16 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 2:39 Duration of recorded file is longer than recording time using SoX George S. Williams
2019-12-16 16:14 ` Jeremy Nicoll - ml sox users [this message]
[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
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=87d93d9e13fb4fe46d7ecd8f74e3876a@wingsandbeaks.org.uk \
--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).