sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Erich Eckner <erich@eckner.net>
To: sox-users@lists.sourceforge.net
Subject: Re: find clicks
Date: Mon, 12 Dec 2016 09:59:59 +0100	[thread overview]
Message-ID: <f4824ccb-3643-a6e9-b6ab-dcfea8833a9f@eckner.net> (raw)
In-Reply-To: <584BC5F3.9000407@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1465 bytes --]

Hi fmiser,

thanks, this has exactly the effects, I was looking for.
Just for the archive: It's 'gramofile'.
It won't process my 24bit-wavs, but I'll get around that.

regards,
Erich

On 10.12.2016 10:08, fmiser wrote:
>> Erich wrote:
> 
>> probably this is beyond sox' scope, but maybe one of you can
>> help anyway:
>>
>> I have some recordings (flac-files) which have emp-interference
>> (audible "clicks" of length ~ 1/2000s) in them. Do you know any
>> scriptable tool (or a plugin to sox) to extract the positions
>> (time or sample) of potential clicks?
> 
>  > Furthermore (this is probably closer to what sox can do), is there a
>  > effect combination in sox (or a ladspa plugin) which can "iron out"
>  > these disturbed samples (and intrapolate their values somehow from
>  > surrounding samples) - given, I know the position of the samples?
> 
> Gramophile?  I use it for de-clicking vinyl LP recordings.
> 
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/xeonphi
> _______________________________________________
> Sox-users mailing list
> Sox-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users
> 


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 322 bytes --]

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi

[-- 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:[~2016-12-12  9:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09  8:57 find clicks Erich Eckner
2016-12-09 10:51 ` Peter P.
2016-12-09 11:31   ` Erich Eckner
2016-12-10  9:08 ` fmiser
2016-12-12  8:59   ` Erich Eckner [this message]
2016-12-12 20:39     ` fmiser
2016-12-12 20:47       ` Erich Eckner

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=f4824ccb-3643-a6e9-b6ab-dcfea8833a9f@eckner.net \
    --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).