in the new 1.1 beta... made a joint stereo mp3 with vbr settings pretty high, and compared the result to the wave file i started with (a 32-bit wav that was almost 80 minutes in length). on two or three seperate tries, i came out with a very small glitch somewhere about an hour in that showed when i compared the resulting mp3 to the original wave file inverted. when lined up near the beginning precisely and rendered together, there was a spot where the output was very different (the tracks didn't line up anymore, about 80 miliseconds off). i'm fairly certain the glitch is a loss of data, as the thing that really cued me to it was the mp3 i was making with superfast mode on was slightly shorter than the wav file i stated with. i turned off superfast mode, and no more glitch when i ripped another mp3 at the same vbr settings. while i don't know exactly how superfast mode works, i'm thinking maybe it splits up the workload so more cores can be used? maybe there's an error when it puts these parts back together? maybe this only happens on long files, or is related to using vbr encoding?just thought i'd report this.
Yes, that's right. The SuperFast code has been merged into the fre:ac development branch in August 2018, but remained disabled by default. The last bug had been reported in November 2018, so I assumed it was time to give it some more exposure by enabling it by default a few weeks before the beta. This got some testing by users of the continuous Linux builds - also without any issues turning up - , so I left it enabled for the beta.
Beta [1992-MP3-VBR-320Kbps]
i had a win7 machine with the 20190423 alpha installed, so i decided to do some testing on this machine. i had to click the checkbox to turn SF mode on in this alpha version, and the first time i encoded VBR 320/192 it went pretty slow. i closed fre:ac and opened it again, and the encode went much faster. both times the glitch did not happen. then i deleted that apha's folder, and installed the 1.1 beta1 so i could confirm that the glitch does happen on that version with that OS, which it did. then i dirty installed the new 1.1 "beta1a" into the freac folder, and all went fine.if i find anything different on win10, i'll let you know. 2ff7e9595c
Comments