enzo1982 / superfast Goto Github PK

I encountered a serious bug in freaccmd when using the superopus codec. The problem is that the error "Could not process file" appears randomly. I don't know what it depends on, it happens completely by accident.

For testing, I used a 48000 Hz 16 bit Stereo wav file. Audio length and content don't matter.

Freaccmd version: v1.1 Alpha 20180716
OS: Windows 10 Pro

Here's a sample output:

C:\AUDIO\test>C:\soft\freac-mt\freaccmd.exe -e superopus -o "test3.opus" test3.wav
Processing file: test3.wav...done.

C:\AUDIO\test>C:\soft\freac-mt\freaccmd.exe -e superopus -o "test3.opus" test3.wav
Processing file: test3.wav...done.

C:\AUDIO\test>C:\soft\freac-mt\freaccmd.exe -e superopus -o "test3.opus" test3.wav
Processing file: test3.wav...done.

C:\AUDIO\test>C:\soft\freac-mt\freaccmd.exe -e superopus -o "test3.opus" test3.wav
Could not process file: test3.wav

C:\AUDIO\test>C:\soft\freac-mt\freaccmd.exe -e superopus -o "test3.opus" test3.wav
Processing file: test3.wav...done.

C:\AUDIO\test>C:\soft\freac-mt\freaccmd.exe -e superopus -o "test3.opus" test3.wav
Could not process file: test3.wav

C:\AUDIO\test>C:\soft\freac-mt\freaccmd.exe -e superopus -o "test3.opus" test3.wav
Processing file: test3.wav...done.

The problem only occurs with the superopus codec. When using the usual opus codec, everything is ok, but I really need superopus, since it uses multithreading.

I can understand if you do not wish to add an RC but I would like to take a chance and ask because the latest 1.3rc has quality improvement that I, and hopefully others, appreciate.