From: Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk>
To: sox-users@lists.sourceforge.net
Subject: Re: convert wav to ogg twice produces diffrent binary files
Date: Sun, 15 Oct 2017 21:44:12 +0100 [thread overview]
Message-ID: <4fae60bf37ba5977e6282bb030390d6b@wingsandbeaks.org.uk> (raw)
In-Reply-To: <yw1xy3ocmegd.fsf@mansr.com>
On 2017-10-15 19:52, Måns Rullgård wrote:
> Dennis Muratshin <frankinshtein85@gmail.com> writes:
>
>> for example run these commands:
>>
>> sox.exe src.wav dest1.ogg -G rate 44100
>> sox.exe src.wav dest2.ogg -G rate 44100
>>
>> It will produce two files with small difference between them:
>> http://prntscr.com/gxdifd
>> Is there any way to avoid it?
>
> It could be due to dither. Try the -R option to use a fixed seed for
> the random number generator.
It's hard to tell from the screenshot how big the files are... but they
look as if they might be tiny. The line 1 difference might I guess be
a date/time stamp, if the file format allows that.
Then ... do we have just one or two 'frames' (if that's an appropriate
term) of audio? Might they also have a date/time stamp in them?
I'd have thought a dither difference would affect many bytes in the
audio
stream, but then again maybe that depends on what the audio in the file
actually is - silence, test tones, real music?
--
Jeremy Nicoll - my opinions are my own
------------------------------------------------------------------------------
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
next prev parent reply other threads:[~2017-10-15 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 16:16 convert wav to ogg twice produces diffrent binary files Dennis Muratshin
2017-10-15 18:52 ` Måns Rullgård
2017-10-15 20:44 ` Jeremy Nicoll - ml sox users [this message]
2017-10-16 13:54 ` Dennis Muratshin
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=4fae60bf37ba5977e6282bb030390d6b@wingsandbeaks.org.uk \
--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).