From: "George S. Williams" <ra@websterling.com>
To: sox-users@lists.sourceforge.net
Subject: Duration of recorded file is longer than recording time using SoX
Date: Sun, 15 Dec 2019 21:39:46 -0500 [thread overview]
Message-ID: <d39859c7-5b7d-afb5-a26a-8da9d234a64c@websterling.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 743 bytes --]
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 |
This works and my test.wav is what I expect except that the duration of
the file is about a third longer than the actual recording time. 3 hours
and 15 minutes of recording time results in a file with a duration of 4
hours and 21 minutes.
I couldn't find anything online or in the SoX documentation concerning
this. Is there something else I can try to make the wave the actual
length of the recording?
[-- Attachment #1.2: Type: text/html, Size: 1004 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next reply other threads:[~2019-12-16 3:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 2:39 George S. Williams [this message]
2019-12-16 16:14 ` Duration of recorded file is longer than recording time using SoX 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
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=d39859c7-5b7d-afb5-a26a-8da9d234a64c@websterling.com \
--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).