and is also a healthy demonstration why bit exact is not truly
necessry, just mean squared error (or something like that) .
The other thing that needs to beĀ tested is backward compatibility
with previous versions for again, MSE.
On 17/09/2016 11:
Hi,
of course it is
"import struct". This somehow got lost when I pasted it in.
Danilo
Am 17.09.2016 um 03:21 schrieb Danilo Beuche:
Hi,
I solved my "difference analysis" problem with a simple python script,
which takes 2 files (left.out and right.out) as input and does 16 bit
value comp
Hi,
of course it is
"import struct". This somehow got lost when I pasted it in.
Danilo
Am 17.09.2016 um 03:21 schrieb Danilo Beuche:
Hi,
I solved my "difference analysis" problem with a simple python script,
which takes 2 files (left.out and right.out) as input and does 16 bit
value comp
good work
1 LSB can come from anywhere.
usually truncation bias.
On 17/09/2016 11:21 AM, Danilo Beuche
wrote:
Hi,
I solved my "difference analysis" problem with a simple python
script, which takes
Hi,
I solved my "difference analysis" problem with a simple python script,
which takes 2 files (left.out and right.out) as input and does 16 bit
value compares. It expects both files to be of same length. Difference
is written to diff.out
It compares against an absolute error ( for me set to
it's fairly easy to just use a sliding correlatorĀ and sync up
the audio for the compare/ MSE computation etc
you might want to oversample it say 4x inside the PC before the
correlation- up to 32ksps from 8ksps
assumption is it is all done in the di
Hi,
to extended my own post:
On 17.09.2016 01:13, Danilo Beuche wrote:
> Hi,
>
> If the goal is to identify regressions, comparing the previously
> generated output data to the output of the changed code is sufficient.
> And for this we can simply compare the value by value difference since
> besi
Hi,
If the goal is to identify regressions, comparing the previously generated
output data to the output of the changed code is sufficient. And for this we
can simply compare the value by value difference since beside rounding errors
the output should be very close. For that a simple value by v
My video compression work tells me we almost need something else rather
than a bit for bit compares.
something like a SN or difference merit
Anyone familiar with video compression will understand this concept .
We would do an encode- decode and then look at the RMS, peak, and
various other sta