sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Mark Sweeney <marksweeneyre@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: Sox Truncating MP3
Date: Wed, 14 Jun 2017 14:20:41 -0700	[thread overview]
Message-ID: <CAGZ8Zr__48-N8Nh45CiJTgwSmRpKo18bPXqBTyDXwpaFcbepvA@mail.gmail.com> (raw)
In-Reply-To: <DM5PR10MB1978EA5502B5C8ABC03487ADF1CF0@DM5PR10MB1978.namprd10.prod.outlook.com>


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

I would prefer to use one application because the file is alreadly loaded
in Sox.  And more importantly if data is getting thrown away in Sox I want
to see something in the output to warn me.  If I run the file through
ffmpeg and then Sox afterwards, how do I know that Sox didn't throw
something away if the output from ffmpeg was bad?

If Sox can't handle the file at the least Sox should output a warning.

On Sat, Jun 10, 2017 at 9:22 AM, Graff, David E <graff@ldc.upenn.edu> wrote:

> If you want to do something sox-ish with uncompressed mp3 data, despite
> knowing that some of the data is faulty, why not just use ffmpeg to get
> (faulty) uncompressed output, and then run sox on that output?
>
>
>   Dave Graff
> ------------------------------
> *From:* Mark Sweeney <marksweeneyre@gmail.com>
> *Sent:* Saturday, June 10, 2017 1:04:06 AM
> *To:* sox-users@lists.sourceforge.net
> *Subject:* [SoX-users] Sox Truncating MP3
>
> I used Sox to process an MP3 file, but the output file was truncated.
> At first I thought the problem was with the command or options, but
> after removing all options and using Sox just to do a copy, the output
> file was still truncated.
>
> So I ran the same file through ffmpeg.  It processed the entire file
> even though there was a warning about invalid data found in the input
> file.
>
> Can I force Sox to finish processing this file without truncating?  If
> not, can I have Sox output a message so I that I know there was a
> problem?  Currently it just fails silently.
>
> ------------------------------------------------------------
> ------------------
> 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
>
> ------------------------------------------------------------
> ------------------
> 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
>
>

[-- Attachment #1.2: Type: text/html, Size: 3910 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-06-14 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-10  5:04 Sox Truncating MP3 Mark Sweeney
2017-06-10 16:22 ` Graff, David E
2017-06-14 21:20   ` Mark Sweeney [this message]
2017-06-29 10:07 ` Jan Stary
2017-06-29 10:59   ` Måns Rullgård
2017-06-29 11:20     ` 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=CAGZ8Zr__48-N8Nh45CiJTgwSmRpKo18bPXqBTyDXwpaFcbepvA@mail.gmail.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).