From: Robert Jeffares <jeffares.robert@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: Self-introduction and my first question ... which programming language sox is written in
Date: Mon, 13 Nov 2023 07:38:51 +1300 [thread overview]
Message-ID: <9e53869b-0bbe-4749-a573-7df0e223b21e@gmail.com> (raw)
In-Reply-To: <CAEG4cZVyA+T+SCyvDq3oVSd37oAaDHZkBoqD4HwYHVUeGFRkTA@mail.gmail.com>
Hi all,
On 10/11/23 02:44, Susmita/Rajib wrote:
> Can python modules be made to use sox as a background tool for audio
> processing?
You can call SOX from Python, Bash, .bat .exe and anything else you can
access the code with.
It happens to be written in C.
I use SOX to apply equalisation to audio, removing hum and hiss, then
apply multi band leveling to achieve a consistent audio output from
multi sourced speech items.
Input audio here comes in many formats. SOX is used to output consistent
wav bitrate. The transcoding loss is acceptable for speech.
Opening and closing audio is then added with fade out and fade in on cue.
In another application I use SOX to edit a news bulletin out of an audio
stream based on the silence between time signal pips [head] and the
mandatory silence at the end [tail] Its unbelievably accurate.
While the scripting is a subject on it's own, SOX has a huge array of
options, well documented with many examples published on line.
Of all the audio processing tools available SOX is the one I use most often.
regards
Robert Jeffares
--
Communication Consultants
64 Warner Park Avenue
Laingholm
Auckland 0604
New Zealand
0221693124 +6498176358
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
prev parent reply other threads:[~2023-11-12 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 13:44 Self-introduction and my first question ... which programming language sox is written in Susmita/Rajib
2023-11-12 12:56 ` Jan Stary
2023-11-12 18:38 ` Robert Jeffares [this message]
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=9e53869b-0bbe-4749-a573-7df0e223b21e@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).