Re: best converter for xhe aac encoder
Reply #28 – 2022-10-21 15:43:48
No, I am not speaking at the browser level (it is a problem of current operating systems that decode Opus in Webm only at the browser level). I'm talking about iOS, if the decoder (and the container too) is implemented by the operating system it will be available for every app.
My contents are normalized to -23dBFS (EBU R128), on the treble we talk about perception, the Opus encoder exploits our poor resolving capacity so it can happen with loudness war contents to perceive the opposite. I propose a test to prove the problem: get a file containing white noise, at each frequency you will have exactly the same noise level in absolute values. Open the terminal and ask sox to generate the spectrogram for you: sox file.wav -n spectrogram -o wave.png You will get something like the following: Now compress the file with Opus: opusenc file.wav file.opus and decompress it again as Wave: opusdec file.opus opus.wav Now ask the Sox for a new spectrogram and admire the nonexistent bit depth reserved for the treble: sox opus.wav -n spectrogram -o opus.png The result will look like the following: I hate HE-AAC, therefore until now I serve the contents I produce to Windows as Opus in Webm and therefore I am absolutely sure of what I write on the bandwidth, at 36kbps a mono file containing only voice is reproduced by Opus in an excellent way with cutting higher frequencies. Should I make the comparison in stereo? I guess not, you will have to do this with music, but I already know that xHE-AAC offers the best on vocals. If Opus were superior to xHE-AAC for in newest TV standard and DRM radio we found Opus instead MPEG-D USAC, broadcast contents are mainly vocal and therefore the advantage of one of the two emerges, although Opus is the best opensource lossy encoder I have ever tried.