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@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/sox-users
