sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Glenn English <ghe2001@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: multitasking
Date: Thu, 26 Oct 2017 02:35:01 +0000	[thread overview]
Message-ID: <CAKS_MTt6nq6Jvu6bE=GrRfu_y7+BGYQBCfdm8P9SsK0kSKk4-w@mail.gmail.com> (raw)
In-Reply-To: <5b9a165c42cd55ae452528ef50edf6fc@wingsandbeaks.org.uk>

On Wed, Oct 25, 2017 at 9:11 PM, Jeremy Nicoll - ml sox users
<jn.ml.sxu.88@wingsandbeaks.org.uk> wrote:

> Have you found some way to extract tiny snippets of audio from some
> copyrighted source, where you can trap a buffer-full (or something)
> before lack of full access stops the rest of the acquisition?

No, not doing anything untoward (I don't think).

I'm trying to move audiobooks (that have been paid for) from the CDs
to something I can listen to without having to walk across the room to
change the disks every so often, and to get distracting announcements
(like which disk we're on) out of the story.

Or to get podcast readings of books in several mp3s into one piece,
again with fewer irrelevant announcements. And with less retelling of
stuff from last week's podcast.

Cdparanoia rips the CDs into a bunch of wav files (often vast numbers
of tiny ones), and the mp3s just need a little un-processing. Both
formats are in many files when sox gets them. No snippets or buffers
or lack of acquisition; it's all there on the disk.

I know that what I'm making could be used for pirating copyrighted
material, but that's not the objective here. I just want the readings
I listen to back in one uninterrupted piece, like they were before
they were chopped up. Like the recordings I made back in my misspent
youth as an audio engineer.

--
Glenn English

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

  reply	other threads:[~2017-10-26  2:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 19:00 multitasking Glenn English
2017-10-24 19:44 ` multitasking Jeremy Nicoll - ml sox users
2017-10-25  0:29   ` multitasking Glenn English
2017-10-25 18:39     ` multitasking Jeremy Nicoll - ml sox users
2017-10-25 18:07 ` multitasking Jan Stary
2017-10-25 19:49   ` multitasking Jan Stary
2017-10-25 20:25   ` multitasking Glenn English
2017-10-25 21:11     ` multitasking Jeremy Nicoll - ml sox users
2017-10-26  2:35       ` Glenn English [this message]
2017-10-26  7:39         ` multitasking Jeremy Nicoll - ml sox users
2017-10-26  9:51         ` multitasking Jan Stary
2017-10-26 14:41           ` multitasking Glenn English
2017-10-26 18:57             ` multitasking Jan Stary
2017-10-26 19:17               ` multitasking Glenn English
2017-10-26 20:27                 ` multitasking Jeremy Nicoll - ml sox users
2017-10-26 22:05                   ` multitasking Glenn English
2017-10-26  9:43     ` multitasking Jan Stary
2017-10-26 14:26       ` multitasking Glenn English
2017-10-26  9:48     ` multitasking Jan Stary
2017-10-26 14:34       ` multitasking Glenn English

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='CAKS_MTt6nq6Jvu6bE=GrRfu_y7+BGYQBCfdm8P9SsK0kSKk4-w@mail.gmail.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).