From: "Jürgen Koslowski via Sox-users" <sox-users@lists.sourceforge.net>
To: "sox-users@lists.sourceforge.net" <sox-users@lists.sourceforge.net>
Cc: "Jürgen Koslowski" <koslowj@protonmail.com>
Subject: discrepancy between sox and ffmpeg when extracting parts of flac file
Date: Sat, 25 Feb 2023 13:32:37 +0000 [thread overview]
Message-ID: <hgm5uo9_nUsgeNNOPQHlRL9QtMXTlPuUfGrDHiY9b0zUNx25npm9dxZXrjxeZJTp_atcEebIvsO8yFc6hGbCyWBNjWqDSLdu_b3JUkKZd2c=@protonmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1301 bytes --]
I have a large flac file (24bits 96kHz) A.flac containing several songs. I can extract those
bei using either sox (B.flac) or ffmpeg (C.flac) with the same splitting points:
sox T04.flac B.flac trim 22:26.342 =34:41.708
ffmpeg -i T04.flac -ss 22:26.342 -to 34:41.708 -compression_level 12 -c copy C.flac
Unfortunately, the results seem to differ in important aspects:
- C.flac that is larger (despite using "-compression_level 12")
- soxi C.flac as well as ffprobe C.flac shows the wrong lengh, namely the length of A.flac
- soxi B.flac and ffprobe B.flac show the correct length
- dr14_tmeter shows different dynamic range values for B.flac (smaller) and C.flac (larger):
DR Peak RMS Duration Title [codec]
---------------------------------------------------------------------------------------------- DR15 -2.25 dB -24.99 dB 12:15 B.flac
DR16 -2.50 dB -24.99 dB 12:15 C.flac
What is going on here? Are there additional parameters in sox that can fix this?
-- If I don't see you no more on this world
Juergen Koslowski I'll meet you on the next one
[koslowj@protonmail.com](mailto:j.koslowski@tu-braunschweig.de)and don't be late!
Sent from Swiss-based encrypted [ProtonMail](https://protonmail.com), (Jimi Hendrix, Voodoo Child, SR)
Sent with [Proton Mail](https://proton.me/) secure email.
[-- Attachment #1.2: Type: text/html, Size: 4585 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 reply other threads:[~2023-02-25 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 13:32 Jürgen Koslowski via Sox-users [this message]
2023-02-25 16:20 ` discrepancy between sox and ffmpeg when extracting parts of flac file Jeremy Nicoll - ml sox users
2023-02-25 22:33 ` Jürgen Koslowski via Sox-users
2023-02-26 0:37 ` 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='hgm5uo9_nUsgeNNOPQHlRL9QtMXTlPuUfGrDHiY9b0zUNx25npm9dxZXrjxeZJTp_atcEebIvsO8yFc6hGbCyWBNjWqDSLdu_b3JUkKZd2c=@protonmail.com' \
--to=sox-users@lists.sourceforge.net \
--cc=koslowj@protonmail.com \
/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).