From: Jan Stary <hans@stare.cz>
To: sox-devel@lists.sourceforge.net
Subject: Re: libsox
Date: Thu, 30 May 2024 11:18:15 +0200 [thread overview]
Message-ID: <ZlhEVzztbqKO2FDC@www.stare.cz> (raw)
On May 30 04:04:28, martinwguy@gmail.com wrote:
> On 5/30/24 00:03, Jan Stary wrote:
>
> > I very much doubt anyone uses libsox at all.
> In fact, I was looking for something that uses libsox today,
> and the only Debian packages that depend on it are sox and sox-fmt-* (!)
Exactly.
> Maybe I should use it for sound file reading, just to be the only one,
> but unfortunately it only delivers (and requires) 32-bit signed samples,
> which is a bit lumpy.
Yes; that is the SoX internal format.
If you just need to read an audio file,
you are better off with libsndfile.
> > I guess it wins if you want effect chains.
See example*.c - some of them are explicitly examples
of setting up an effects chain. (I haven't tried those yet.)
The others simply read and write and concatenate files,
things not specific to sox.
Jan
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
next reply other threads:[~2024-05-30 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 9:18 Jan Stary [this message]
2024-05-30 10:41 ` libsox Jan Stary
2024-05-30 14:31 ` libsox Claude Warren
2024-05-30 15:50 ` libsox 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-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZlhEVzztbqKO2FDC@www.stare.cz \
--to=sox-devel@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).