On 2021-10-06 07:50, Lee Jones wrote:
It's almost certainly my fault, but I'm perplexed as to how to fix it.
I'm just guessing, but ...
# Trimming all silence to 2 seconds
ljkenny:~$ sox -V manchester_app_test.wav
manchester_app_test-trimmed.wav silence -l 1 0.1 1% -1 2.0 1%
That effect: silence -l 1 0.1 1% -1 2.0 1%
has parameters -l then 1 0.1 1% then others. According to the
manual:
1 0.1 1%
^ 1 means trim audio from the start of the file
until
it first finds non-silence
^^^ 0.1 means the length of time that non-silence must
be
detected for
^^ 1% means the level sound must have to be treated
as
non-silence
You possibly thought that the "0.1" meant 0.1 seconds. It doesn't. It
means 0.1 samples which seems to me to be meaningless and might cause
sox to think that non-silence is never detected. In that situation I'd
suspect that sox would then "trim" away ALL the contents.
--
Jeremy Nicoll - my opinions are my own
_______________________________________________
Sox-users mailing list
Sox-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/sox-users
