Originally posted by Sachankara Could anyone compile it for me...? I can´t seem to get it to work correctly with VC++ 6.0...
Originally posted by Speek I've uploaded a Win32 binary here:http://home.wanadoo.nl/~w.speek/download/Eaqual.zip
Originally posted by Speek I get this with death2.wav:c:ProgsEncodersEaqual>eaqual -fref d:testgeluidendeath2.wav -ftest d:death2.wav -offset 2048 -srate 44100EAQUAL - Evaluation of Audio QualityVersion: 0.1alphaAuthor: Alexander Lerch, zplane.developmentCopyright: Heinrich- Hertz-Institut (http://www.hhi.de) zplane.development (http://www.zplane.de)_______________________________________________________Reference File: d:testgeluidendeath2.wavTest File: d:death2.wavSample Rate: 44100Number of Channels: 2Press Escape to cancel...Frame: 806Time elapsed: 41.39Resulting ODG: -3.9122Resulting DIX: -4.1096BandwidthRef 21521.9414BandwidthTest 16249.1914NMR 41.9918WinModDiff1 163.0067ADB 3.1234EHS 1.4913AvgModDiff1 200.9328AvgModDiff2 573.1494NoiseLoud 53.7488MFPD 1.0000RDF 0.9988Is there something wrong in my command line?Edit: I forgot to mention that the test file was encoded with Psytel aacenc 2.0 and decoded with a recent version of FAAD.
Originally posted by Ivan Dimkovic Here are some ODG (Objective Difference Grade) results, difference from the original (1 to 4), for castanets encoding:Psytel AACEnc 2.0 @ 128 Kbits/s: -0.6833Psytel AACEnc 2.0 @ 96 Kbits/s: -1.3516Fraunhofer AACDemo @ 128 Kbits/s: -0.7383LAME --nspsytune @128 Kbits/s: -0.9899MP3Enc -qual 9 @128 Kbits/s: -0.7479
Originally posted by dosdan Ivan, I think that LAME you used is a bit old. I found no offset when comparing the original wav to the LAME decoded wav in CoolEdit (both had the first positive peak at sample 7905) and then I looked carefully at the decoding screen display where it mentions that the offset was removed:
Originally posted by Skeeve242 Doesn't the readme say best ODG would be 0.0 which means identical file? I had -0.05 for MPC -xtreme, but I didn't checked for correct offset so it's unlikely it's a valid result.
Hi,It's true that a positive ODG should not occur(theoretically). However, the ITU recommendation does allow positive ODGs,because this could also happen in listening tests, where thefile under test is rated better than the reference file.Furthermore you may not forget, that there is a neural networkbuiltin which was trained on real listening test ratings. Theconfidence intervall in those tests may ly between 0 and 0.5,and thus EAQUAL may be wrong within those intervalls.
Originally posted by Benjamin Lebsanft hehe only ogg sounds better then the original the only positive value in speeks tests
Originally posted by Ivan Dimkovic Here is what alexander told me regarding positive ODG:[some text]
I posted some results here: http://home.wanadoo.nl/~w.speek/eaqual.htm
Originally posted by ff123 I'm not sure if using --scale is such a good idea for this test (changes the amplitude vs. the original). However, it may not have a big impact on the results.ff123