sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Paul Jessop <paul@countyanalytics.com>
To: "sox-users@lists.sourceforge.net" <sox-users@lists.sourceforge.net>
Subject: FM radio compressor example bug
Date: Fri, 5 May 2017 10:06:33 +0000	[thread overview]
Message-ID: <CDE4D7E9-81C5-4193-8EE1-EA1B5274707D@countyanalytics.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2389 bytes --]

Hi,

SoX is an awesome tool and mostly I’m making very good use of it.

There are a few references in the archive here (*) and elsewhere to a problem with the example in the current (2014-12-31) documentation for mcompand:

play track1.wav gain −3 sinc 8000− 29 100 mcompand \
            "0.005,0.1 −47,−40,−34,−34,−17,−33" 100 \
            "0.003,0.05 −47,−40,−34,−34,−17,−33" 400 \
            "0.000625,0.0125 −47,−40,−34,−34,−15,−33" 1600 \
            "0.0001,0.025 −47,−40,−34,−34,−31,−31,−0,−30" 6400 \
            "0,0.025 −38,−31,−28,−28,−0,−25" \
            gain 15 highpass 22 highpass 22 sinc −n 255 −b 16 −17500 \
            gain 9 lowpass −1 17801

I am looking to emulate the kind of compressor used in FM broadcasting and broadly understand the chain here: decrease level, some sort of filter (read on), multiband compander with crossovers at 100, 400, 1600 and 6400Hz, increase level, filter out very low frequencies, lowpass at 17.5kHz, increase level and lowpass at 17.8kHz.

The second instance of “sinc” seems to be correct but the first “sinc 8000− 29 100” throws an error (using 14.4.2) and (according to others who have looked at this) seems to retain the parameters of the old “filter” effect. That would make it a low pass filter with a corner at 8kHz and a window-length of 29 (the default being 128) and a beta of 100 (default being 16 for a Kaiser window). I wonder if 29 and 100 are the right way around even? They are very far from their defaults.

My simplistic attempts to emulate this with “sinc” or “lowpass” create all sorts of level problems and I’m trying to understand what this effect is intended to do! If it is indeed supposed to roll off the response of the overall effect at 6dB/octave above 8kHz, that doesn’t seem to be recovered further down the chain. Knowing what the chain emulates would help!

Has anyone solved this?

Best regards,

Paul


(*) Most recently Doug Lee at https://sourceforge.net/p/sox/mailman/message/34787636/

Paul Jessop              county analytics ltd
---------------------------------------------
rights - technology - markets - music - media
---------------------------------------------
paul@countyanalytics.com<mailto:paul@countyanalytics.com>      +44 7850 685378



[-- Attachment #1.2: Type: text/html, Size: 8814 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

                 reply	other threads:[~2017-05-05 10:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CDE4D7E9-81C5-4193-8EE1-EA1B5274707D@countyanalytics.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).