From: Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk>
To: sox-users@lists.sourceforge.net
Subject: Re: Trim WAV file Meta Data
Date: Wed, 06 Dec 2017 20:52:30 +0000 [thread overview]
Message-ID: <2e768c3a2bc7f4022318d5b16faad19f@wingsandbeaks.org.uk> (raw)
In-Reply-To: <CAFgr-jSkG2cqBq29LGPw=829ypvfiUYrh8Y-LQTuG61rK-Wh5A@mail.gmail.com>
On 2017-12-06 19:54, david wrote:
> Hello all, love sox and am so glad it's out there. I'm using SOX to
> verify, convert and "normalfy" audio files coming in from untrusted
> sources
> (web). Basically I'm converting source audio to WAV PCM. Audio files
> that
> come from sources like Adobe Audition often contain meta data, which
> just
> renders as ~100ms of noise at the end of the track. I'm wondering if
> that
> could be trimmed off somehow.
>
> I've tried a variety of things. The command I'm using currently:
>
> sox --ignore-length [infile] -t wavpcm [outfile]
Why are you sure that the audio-length data in the file headers is
wrong?
You're telling sox to regard everything in the file as sound data.
What does soxi say about such files? Does it identify their contents
as
having a particular format?
> I tried to attach some files, but they got flagged for moderation 6
> days
> ago, so I'm resubmitting this.
Upload them somewhere and post a URL.
--
Jeremy Nicoll - my opinions are my own
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2017-12-06 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 19:54 Trim WAV file Meta Data david
2017-12-06 20:52 ` Jeremy Nicoll - ml sox users [this message]
2018-02-10 20:30 ` Jan Stary
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=2e768c3a2bc7f4022318d5b16faad19f@wingsandbeaks.org.uk \
--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).