From: SourceForge.net <noreply@sourceforge.net>
To: SourceForge.net <noreply@sourceforge.net>
Subject: [ sox-Bugs-2254919 ] Silence doesn't trim digitial silence correctly
Date: Mon, 18 Feb 2013 15:30:38 -0800 [thread overview]
Message-ID: <E1U7aAS-0006S6-5p@sfs-ml-4.v29.ch3.sourceforge.com> (raw)
Bugs item #2254919, was opened at 2008-11-10 02:57
Message generated for change (Comment added) made by uklauer
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=2254919&group_id=10706
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Hash (mrhash)
Assigned to: Nobody/Anonymous (nobody)
Summary: Silence doesn't trim digitial silence correctly
Initial Comment:
14.2.0 and maybe other versions.
Trimming digital silence using command such as:
sox source.wav target.wav silence 1 1 0% or
sox source.wav target.wav silence 1 00:00:01 0% etc.
doesn't work.
sox source.wav target.wav silence 1 1 0.01%
does work!
silence is definitely digital silence according to soundforge.
----------------------------------------------------------------------
>Comment By: Ulrich Klauer (uklauer)
Date: 2013-02-18 15:30
Message:
$ sox -n source.wav synth 3 whitenoise gain -10 pad 7
$ sox source.wav target.wav silence 1 00:00:01 0% 2>&1 | grep Length
Length s 3.000
----------------------------------------------------------------------
Comment By: max fon (maxfon)
Date: 2009-12-11 12:29
Message:
I think it is still not working, can you give example how it works
(removing digital only silence from beginning)
----------------------------------------------------------------------
Comment By: robs (robs)
Date: 2009-06-28 08:33
Message:
Hmm, the documentation is contradictory here: in one place it says `Silence
is anything below a specified threshold', but elsewhere, `Threshold is used
to indicate what sample value you should treat as silence'. But I think I
agree that the latter makes more sense, hence now fixed in CVS.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=2254919&group_id=10706
------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
reply other threads:[~2013-02-18 23:31 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-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1U7aAS-0006S6-5p@sfs-ml-4.v29.ch3.sourceforge.com \
--to=sox-devel@lists.sourceforge.net \
--cc=noreply@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).