sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk>
To: ML - sox-users <sox-users@lists.sourceforge.net>
Subject: Re: Duration of recorded file is longer than recording time using SoX
Date: Mon, 16 Dec 2019 20:53:50 +0000	[thread overview]
Message-ID: <a8e3d61914d42524ccce7aee2f6def13@wingsandbeaks.org.uk> (raw)
In-Reply-To: <f1382121-d632-9252-17a8-e7baed8913f2@websterling.com>

On 2019-12-16 16:44, George S. Williams wrote:
> On 12/16/2019 11:14 AM, Jeremy Nicoll - ml sox users wrote:
>> 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?

> The command is run by itself- the pipe characters are a consequence of
> copying and pasting that I didn't catch.
> 
> The wave file contains what was recorded, nothing extra. It is
> 'stretched' to the longer duration.

George's reply to me was, it seems, off-list.  Don't know why.  I'm
replying on-list.

What does  soxi  say about the wave file?

Does the file have the file-size you'd expect for the single channel,
unknown (to us anyway) bit depth, 6000 samples per second?

Is what's in the file a recording of something (music, speech?) that
sounds 'sensible' to a human, or is it some sort of scientific data
that one can't tell about (by ear)?

Does the header info in the wav file contain the right descriptive
info for the data?


-- 
Jeremy Nicoll - my opinions are my own


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

  parent reply	other threads:[~2019-12-16 20:54 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
     [not found]   ` <f1382121-d632-9252-17a8-e7baed8913f2@websterling.com>
2019-12-16 20:53     ` Jeremy Nicoll - ml sox users [this message]
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=a8e3d61914d42524ccce7aee2f6def13@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).