From: "Graff, David E via Sox-users" <sox-users@lists.sourceforge.net>
To: "sox-users@lists.sourceforge.net" <sox-users@lists.sourceforge.net>
Cc: "Graff, David E" <graff@ldc.upenn.edu>
Subject: Re: "norm" effect causes intermittent truncation of MP3 output.
Date: Thu, 17 Jun 2021 14:12:47 +0000 [thread overview]
Message-ID: <D4C2E179-BFD3-498F-8384-D39314D5700C@upenn.edu> (raw)
In-Reply-To: <CAAyoY+s3spoRUHfka7+pTeGF+V_sOKg-1pHnwc0frkXcQGySqw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1216 bytes --]
If you run the same batch of files two times using -R, do you get the same pattern of truncations both times?
Dave Graff
From: Scott Temby <scottt@damsmart.com.au>
Reply-To: "sox-users@lists.sourceforge.net" <sox-users@lists.sourceforge.net>
Date: Thursday, June 17, 2021 at 10:03 AM
To: "sox-users@lists.sourceforge.net" <sox-users@lists.sourceforge.net>
Subject: [SoX-users] "norm" effect causes intermittent truncation of MP3 output.
Hi,
When using "sox.exe <source_file>.wav -C 192.01 <destination_file>.mp3 norm" I've found the output is occasionally truncated (shorter duration than the input, but matches up to that point).
I've tried this on a few systems, and while the fault is intermittent (not linked to any particular input file or condition), it does repeatedly occur (a few times in a "batch"). Immediately re-processing the same input files often yields success, or at least, failures on different files. I've also tried -C 192.2 to see if that was the issue, and it is not. removing "norm" solves the problem, and I can reliably encode thousands of files without truncation.
Hopefully there's an easy fix, if not, at least you are now aware of the issue.
Regards,
Scott
[-- Attachment #1.2: Type: text/html, Size: 4004 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- 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
next prev parent reply other threads:[~2021-06-17 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 13:00 "norm" effect causes intermittent truncation of MP3 output Scott Temby
2021-06-17 14:12 ` Graff, David E via Sox-users [this message]
2021-06-17 15:46 ` Peter P.
2021-06-17 17:00 ` [EXTERNAL] " Scott Temby
2021-06-17 19:54 ` Jan Stary
2021-06-18 13:39 ` Scott Temby
2021-06-18 22:01 ` Jeremy Nicoll - ml sox users
[not found] ` <a770f72d-1a5a-abef-dfbf-4b605f2a8360@mailbox.org>
2021-06-19 10:44 ` unsubscribe Jeremy Nicoll - ml sox users
2021-06-19 14:36 ` unsubscribe Jeff Learman
2021-06-17 18:51 ` "norm" effect causes intermittent truncation of MP3 output Jeremy Nicoll - ml sox users
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=D4C2E179-BFD3-498F-8384-D39314D5700C@upenn.edu \
--to=sox-users@lists.sourceforge.net \
--cc=graff@ldc.upenn.edu \
/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).