From: "Graff, David E" <graff@ldc.upenn.edu>
To: Eyob Yirdaw <edyirdaw@yahoo.com>,
"sox-users@lists.sourceforge.net"
<sox-users@lists.sourceforge.net>
Subject: Re: Recording in chunks using sox
Date: Fri, 25 Aug 2017 17:20:05 +0000 [thread overview]
Message-ID: <DM5PR10MB19782E182E09F24B4DDA45EBF19B0@DM5PR10MB1978.namprd10.prod.outlook.com> (raw)
In-Reply-To: <790552421.2332795.1503680652651@mail.yahoo.com>
[-- Attachment #1.1: Type: text/plain, Size: 1339 bytes --]
My first intuition on this would be to have your continuous a/d process pipe to some custom process (not sox), which simply takes a binary stream on stdin and creates a continuous series of data files on disk of equal length (e.g. 20 minutes worth of samples, or whatever seems like a good interval), using some reasonable template pattern for file names.
Then, there'd be a separate process (running continuously) that scans for new files at regular intervals, and runs sox on each new file, converting it from raw to whatever format you want as a final product.
Dave Graff
________________________________
From: Eyob Yirdaw via Sox-users <sox-users@lists.sourceforge.net>
Sent: Friday, August 25, 2017 1:04:12 PM
To: sox-users@lists.sourceforge.net
Cc: Eyob Yirdaw
Subject: [SoX-users] Recording in chunks using sox
Hi all,
I want to record 24/7 transmission of FM radios using DVB-T dongles. I want to direct the input audio from some dongle to sox, eg. something like
rtl_fm -f 88.8M -d 0 -M wbfm | sox -r 32k -t s16 - -t ogg device_0.ogg
here am using the rtl_fm terminal program.
Can sox help me save the continuous FM audio that comes from rtl_fm to be saved in some time length chunks, say 10 minute long chunks?
It means that sox would write to disc every 10 minutes.
Thanks for any help!
[-- Attachment #1.2: Type: text/html, Size: 2911 bytes --]
[-- Attachment #2: Type: text/plain, Size: 202 bytes --]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
[-- 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 prev parent reply other threads:[~2017-08-25 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <790552421.2332795.1503680652651.ref@mail.yahoo.com>
2017-08-25 17:04 ` Recording in chunks using sox Eyob Yirdaw via Sox-users
2017-08-25 17:20 ` Graff, David E [this message]
2017-08-25 18:11 ` Peter P.
2017-08-25 18:18 ` Graff, David E
2017-08-26 12:42 ` Eyob Yirdaw via Sox-users
2017-08-27 14:37 ` Jan Stary
2017-08-25 18:12 ` Jan Stary
2017-08-25 18:18 ` Jan Stary
2017-08-26 13:54 ` Jeremy Nicoll - ml sox users
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=DM5PR10MB19782E182E09F24B4DDA45EBF19B0@DM5PR10MB1978.namprd10.prod.outlook.com \
--to=sox-users@lists.sourceforge.net \
--cc=edyirdaw@yahoo.com \
/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).