sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Måns Rullgård" <mans@mansr.com>
To: <alant123@btconnect.com>
Cc: sox-users@lists.sourceforge.net
Subject: Re: Sox FM Radio Processing Example
Date: Mon, 01 Feb 2021 13:15:35 +0000	[thread overview]
Message-ID: <yw1xk0rsc4js.fsf@mansr.com> (raw)
In-Reply-To: <000b01d6f88c$dff1bd40$9fd537c0$@btconnect.com> (alant's message of "Mon, 1 Feb 2021 11:24:57 -0000")

<alant123@btconnect.com> writes:

> Hi all.  
>
> I have used Sox for simple stuff in the past but am intrigued by the FM
> Radio processing example which (in different variations over time) appears
> in the man page.  It may be just what I am looking for - but I can't get it
> to work.  Referring to various posts on the Internet asking about this and
> also different versions of the man page scattered around, I have gleaned
> that the sinc effect is now the filter effect? However, there is still
> something wrong I get an error.  Oddly, the sox manpage for Ubuntu 18 still
> uses the "sinc" version. 

It's the other way around, sinc is the new name (since 2009).

> I am using it in a script file that contains this:
>
> play t1.wav gain -3 filter 8000- 32 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 filter -17500 256  \
>                    gain 9 lowpass -1 17801
>
> but I get the following error message
>
> "play FAIL gain: usage [-e] [-b] .."

That's because "filter" isn't a valid effect name, to it's parsed as an
argument to the "gail" effect which (rightly) rejects it.

> For reference this is copied from the manpage at 
>
> https://linux.die.net/man/1/sox

That's a very old version of the man page.  Unfortunately, the current
one is also wrong.  Someone simply forgot to update that example at some
point.  I've fixed it just now.

Here's the updated command:

    play track1.wav gain -3 sinc -n 29 -b 100 8000 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

Hope this helps.

-- 
Måns Rullgård


_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

      reply	other threads:[~2021-02-01 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 11:24 Sox FM Radio Processing Example alant123
2021-02-01 13:15 ` Måns Rullgård [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=yw1xk0rsc4js.fsf@mansr.com \
    --to=sox-users@lists.sourceforge.net \
    --cc=alant123@btconnect.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).