From: Erich Eckner <erich@eckner.net>
To: sox-users@lists.sourceforge.net
Subject: Re: volume extremely low when combining many files
Date: Sat, 24 Sep 2016 19:14:25 +0200 [thread overview]
Message-ID: <d66eb70b-2b42-1dec-09c6-395272726d75@eckner.net> (raw)
In-Reply-To: <20160924154154.psuxcpxgis6lbs6w@www.stare.cz>
[-- Attachment #1.1.1: Type: text/plain, Size: 2086 bytes --]
Hi Jan,
I expected it to start with silence and was just checking, however Bobs
file does _not_ start with silence, although he claimed to pad 10
seconds at the beginning. That's why I wanted to know the actual command
in use.
cheers, Erich
On 24.09.2016 17:41, Jan Stary wrote:
> On Sep 24 07:06:23, erich@eckner.net wrote:
>> Hi Bob,
>>
>> can you post the command you used to generate that file?
>> It is indeed not "silent" at the beginning:
>>
>>> sox sound77.wav -n trim 0 9 stats
>>
>> DC offset -0.000002
>> Min level -0.007812
>> Max level 0.007812
>> Pk lev dB -42.14
>> RMS lev dB -48.17
>> RMS Pk dB -47.83
>> RMS Tr dB -48.64
>> Crest factor 2.00
>> Flat factor 2.17
>> Pk count 99.0k
>> Bit-depth 1/8
>> Num samples 397k
>> Length s 9.000
>> Scale max 1.000000
>> Window s 0.050
>>
>> However, if I do a pad:
>>
>>> sox sound77.wav test.wav pad 10
>
> The manpage says
>
> pad { length[@position(=)] }
> [...]
> position is optional for the first and last lengths specified
> and if omitted correspond to the beginning and the end of
> the audio respectively.
>
> So if I am reading this right, you are padding
> with 10 seconds of silence at the beginning.
>
> Then in particular the first 9 seconds is silence:
>
>> and analyze the result, it's silent:
>>
>>> sox test.wav -n trim 0 9 stats
>> DC offset 0.000000
>> Min level 0.000000
>> Max level 0.000000
>> Pk lev dB -inf
>> RMS lev dB -inf
>> RMS Pk dB -inf
>> RMS Tr dB -inf
>> Crest factor 1.00
>> Flat factor 111.97
>> Pk count 794k
>> Bit-depth 0/0
>> Num samples 397k
>> Length s 9.000
>> Scale max 1.000000
>> Window s 0.050
>
> Jan
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 79 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:[~2016-09-24 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 23:10 volume extremely low when combining many files Bob S
2016-09-22 5:35 ` Erich Eckner
2016-09-22 16:19 ` Bob S
2016-09-22 17:37 ` Jeremy Nicoll - ml sox users
2016-09-22 17:56 ` Bob S
2016-09-23 4:56 ` Erich Eckner
2016-09-23 21:43 ` Bob S
2016-09-24 5:06 ` Erich Eckner
2016-09-24 15:41 ` Jan Stary
2016-09-24 17:14 ` Erich Eckner [this message]
2016-09-27 20:55 ` Bob S
2016-09-27 21:30 ` Erich Eckner
2016-09-29 16:40 ` Bob S
2016-09-29 16:49 ` Bob S
2016-09-24 17:49 ` Bob S
2016-09-22 18:07 ` Bob S
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=d66eb70b-2b42-1dec-09c6-395272726d75@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).