I'm trying to fit music into an old phone with low space, and it seems that HE-AACv2 and Opus are the best candidates.
I'm new to encoding aac, so I searched a lot and didn't find the fdk aac encoder for windows, just a lot of source code for android.
Also, I know there are other aac encoders like nero and apple but I want to stick to something free/open source.
http://wlc.io/2015/06/20/fdk-aac/ <--- here's one.
Just google for "fdk aac windows build" or something.
I notice the lack of compiled tools, though. However this might be some sort of licensing issue.
I believe the licensing issue is that the license on the source code does not protect anyone from patent licensing issues on the codec.
Couldn't you make a "totally not an AAC encoder" type thing similar to LAME?
LAME developers do not distribute binaries either. For approximately the same reasons.
But I've heard it's not too hard to build.
it seems that HE-AACv2 and Opus are the best candidates
If I were you, I'd just use Opus.
LAME developers do not distribute binaries either. For approximately the same reasons.
No, but there were plenty of builds around and they were relatively easy to get. Also, since MP3 patents have expired, the binaries are now considered free. Fedora has them in their main repos now, etc.
That aside: AAC (with the HE-AACv2 profile) encoding should be possible with Winamp. According to http://wiki.hydrogenaud.io/index.php?title=Fraunhofer FhG AAC is included in Winamp.
Believe it or not, you can still download Winamp from winamp.com, even though the page says "there's more coming soon", that page has been in that state for at least four years.
Since the FDK AAC is released as source from Fraunhofer, is it nonetheless prohibited to release builds? Technically all FDK AAC encoders that you download on your Android phone are compiled binaries. As I understand it, having FDK AAC builds for Windows etc, shouldn't be a problem. Or is Android paying some sort of license fee to Fraunhofer, so they can put FDK AAC encoder binaries onto people's phones?
https://github.com/nu774/fdkaac_autobuild/
simply follow the guides with internet connection on.
https://github.com/nu774/fdkaac_autobuild/
simply follow the guides with internet connection on.
As is written in the README, it doesn't work until MSYS updates it's OpenSSL library.
Maybe it should be rewritten to use MSYS2, but honestly I'm not interested in maintaining fdkaac_autobuild.
You can still build fdkaac yourself:
https://github.com/nu774/fdkaac/blob/master/INSTALL
MSYS2 has an even better issue, last time I checked. It apparently uses the wrong subsystem type, or at least has some other issue, causing its console binaries to only emit output under MSYS2 shells.
The fdkaac_autobuild suite will need an overhaul as the fdk-aac library now updated its API and renamed several struct fields (e.g. encoderDelay is now nDelay).
The discussion about the merge patch contains a link to a patch for libav which you might find useful.
I noticed that while running the media-autobuild suite (https://github.com/jb-alvarado/media-autobuild_suite/), which took some inspiration from the fdkaac_autobuild batch.
Updated fdkaac repo.
As for fdkaac_autobuild, just let it die.
It feels home in MABS now.
Also, I know there are other aac encoders like nero and apple but I want to stick to something free/open source.
In that case, I would use Opus since it's the best lossy encoder right now especially at lower bit rates.
I suggest no lower than 64kbps for your old phone if you don't want to gamble on sound quality too much or you got plenty of music you want to fit on it and don't mind sacrificing some sound quality to do it you can go lower to say 32kbps or 48kbps. you can stick with v1.2.1 (currently included in the Foobar2000's Encoders Pack) or use the v1.3RC (see Opus section of these forums for download info) as it supposedly has a bit better sound quality than v1.2.1 at low bit rates.
p.s. if you go with AAC it's best to use Apple AAC (or the FhG one from WinAMP as a alternative) with Foobar2000's QAAC which is included in the Foobar2000 Encoders Pack for best sound quality. once the Encoders Pack is installed, to make it easy for you... just extract the following file to your 'Foobar2000\Encoders' folder and then you can create Apple AAC files... http://www.mediafire.com/file/kfq40f76vym2680/Foobar2000_-_Apple_AAC_Encoding_%2528iTunes_v12.7.4_Mar29th2018_-_extract_to_foobar2000-encoders%2529.7z/file
@ThaCrip, can't share that file/files here, why do you think no one ever linked it?
@nu774, the autobuild doesn't work for me. I had to manually download mingw then run and that's all good but when I run the other two .bats it doesn't create anything. When you have 5 mins if you could double check. Thank you.
@eahm I would remove the link myself, but I can no longer edit my post.
but I am surprised it's a big deal as no one is making any $ off of it or doing anything shady with it. would Apple care that much to pursue legal action on this site over it?
We just don't link proprietary libraries etc., Apple would like you to download and install iTunes to have that.
I can compile current master with MinGW but not with MSVC 2015. Can anyone help or assist me for that? Thanks
The problem was from my Visual Studio installation actually. Sorry. :)
Please delete wtf forum, redirect to another thread after logging in.
Hi
A have the similar issue.
Based on wiki by hydrogenaudio: What's the best AAC encoder? (https://wiki.hydrogenaud.io/index.php?title=AAC_FAQ#What.27s_the_best_AAC_encoder.3F) information I wanted to use the 2nd most recommended AAC(FDK) encoder.
I use foobar2000 (v1.4.3) with Free_Encoder_Pack_2018-10-19.
(https://abload.de/img/foobar_encodercjjvk.png)
The foobar2000's link directs me to Cabinet site (https://sites.google.com/site/qaacpage/cabinet).
I downloaded the "fdkaac_autobuild.zip" file to create "fdkaac.exe".
However executing install-mingw.bat does not create it.
What am I doing wrong?
How can I get a most recent "fdkaac.exe"?
Regards
szabi
Surprise ... install-mingw.bat installs MinGW. Only. If you want to build fdkaac, why not run build_fdkaac.bat after installing MinGW?
P.S.: This script is not updated anymore; but the media-autobuild_suite (https://github.com/jb-alvarado/media-autobuild_suite) can do it as well (besides building a lot more codecs, and finally ffmpeg using them all).
There are 3 steps instruction to get fdkaac.exe
1) Execute install-mingw.bat.
MinGW and MSYS are installed under current directory.
Sub directories such as bin, include, lib,... are created.
2) Execute build_libfdk_aac.bat.
3) Execute build_fdkaac.bat.
When the 1st step fails the other steps does not do anything.
Now this media-autobuild_suite runs.
I just wanted fdkaac.exe however there were near 50 another question which most of them I did not know what it is.
It was written ffmpeg is more recommended to create aac audio than fdkaac.
Does it mean wiki by hydrogenaudio: What's the best AAC encoder (https://wiki.hydrogenaud.io/index.php?title=AAC_FAQ#What.27s_the_best_AAC_encoder.3F) is not correct?
It says ffmpeg is the last in quality.
This media-autobuild runs since15 minutes.
It is the most overcomplicated process ever seen to get one single "fdkaac.exe" file.
Is that ok?
Fraunhofer FDK AAC (https://github.com/mstorsjo/fdk-aac) and CLI QuickTime AAC/ALAC encoder (https://github.com/nu774/qaac) both available just an exe file would be needed.
for windows:
https://github.com/jb-alvarado/media-autobuild_suite
More than one hour running for nothing.
It did not create fdkaac.exe file.
Are there any way to create aac audio by apple or fraunhofer aac?
try this
this tool works because i use it and you get fdk aac.
Well, ffmpeg is a "Swiss Army Knife" tool at the command line. But there are several configurations.
Among all the available AAC encoders, Fraunhofer FDK-AAC and Apple CoreAudioToolbox (the encoder used by iTunes) are some of the very best. You can have them separately (either qaac with the extracted DLLs from iTunes, or fdkaac), or you can integrate FDK-AAC into an ffmpeg. But noone is allowed to distribute such an encoder set or ffmpeg completely and ready-to-use.
Alternatively, ffmpeg also has a free AAC encoder in its libavcodec core. You can distribute this kind of ffmpeg. But its quality is not as good as the others.
@szabi: You say it did not create fdkaac.exe? Why not? Where did you look? How did you configure the suite? Are there any erro rmessages to report? ... We don't have crystal balls to guess what happened. But to solve media-autobuild suite related issues, a separate forum thread is preferred, that won't fit in here anymore. I can confirm that it usually works.
As I start my post I download "fdkaac_autobuild.zip"
I used it few years ago that time it run for few minutes and create fdkaac.exe.
Now I wanted to have newest version of it but fdkaac_autobuild not working anymore.
The linked media-autobuild run more than hour and did not create fdkaac.exe.
I mentioned there were near 50 question before starts doing something however I did not understand most of them.
I do not want to run once more because asking so many question from an end-user is nonsense as well as the running time.
This is the log file:
Starting 64bit compilation of all tools
Imported default FFmpeg options from .bat
License: lgplv3
Imported default mpv options from .bat
Starting 64bit compilation of global tools
Running git clone for libtiff...
- libtiff git ....................................... [Recently updated]
+ Running cmake...
+ Running build...
+ Running install...
+ Stripping...
L libtiff-git ................................................ [Updated]
Starting 64bit compilation of audio tools
Installing libvorbis... done
Running git clone for fdk-aac...
- fdk-aac git ....................................... [Recently updated]
+ Running autoreconf...
+ Running configure...
+ Running make...
+ Running install...
+ Stripping...
L fdk-aac-git ................................................ [Updated]
Installing faac... done
Running git clone for opus...
- opus git .......................................... [Recently updated]
+ Running autogen...
+ Running configure...
+ Running make...
+ Running install...
+ Stripping...
L opus-git ................................................... [Updated]
Starting 64bit compilation of video tools
Finished 64bit compilation of all tools
Deleting status files...
Zipping man files...
Deleting temporary build dirs...
Compilation successful.
This window will close automatically in 5 seconds.
Successfull just the file do not created.
So I have a different approach.
I used the old fdkaac.exe which was created few years ago.
The encoded file has the following tool's information: fdkaac 0.6.3, libfdk-aac 3.4.22, VBR mode 4
Can media-autobuild create newer version of "fdkaac.exe"?
If you want to build fdkaac, you must set up ffmpeg to compiling for a "non-free" license. MABS wrote the warning in the configuration text that enabling a GPL compliant license disables OpenSSL and FDK-AAC. Furthermore, if you want a separate fdkaac.exe, you need to enable the compilation of standalone codecs.
Try the attached build/media-autobuild_suite.ini to have MABS compile as little as possible besides fdkaac.exe.
Based on wiki by hydrogenaudio: What's the best AAC encoder? (https://wiki.hydrogenaud.io/index.php?title=AAC_FAQ#What.27s_the_best_AAC_encoder.3F) information I wanted to use the 2nd most recommended AAC(FDK) encoder.
I wonder who put it into the 2nd place and why.
Since my last post I tried the following:
I used google how to create fdkaac.exe from FDK AAC by mstorsjo (https://github.com/mstorsjo/fdk-aac)
This guide found: How to Compile From Source Code (https://github.com/PKISharp/win-acme/wiki/How-to-Compile-From-Source-Code).
I downloaded visual studio but what to do definetly over my knowledge.
Failure.
However I found something what worked finally not only one but 3 solution.
After install apple itunes foobar2000 was able to encode with apple-aac.
Unfortunately after I need to spend few minutes to clean my PC from apple's garbage.
I found the qaac.exe (https://www.videohelp.com/software/qaac) but I could not use and no guide how to.
Secondly installing winamp 5.66 also provide success for fhg-aac.
Disadvantage of it is quite obsolete.
Third was the most preferred solution. Searching fdkaac.exe (https://www.google.com/search?source=hp&ei=qPa9XNsax62uBJqwutgB&q=fdkaac.exe&btnK=Google-keres%C3%A9s&oq=fdkaac.exe&gs_l=psy-ab.3..0j0i30l5.2043.4952..5899...0.0..0.149.1199.1j9......0....1..gws-wiz.....0..0i131j0i10j0i10i30j0i8i10i30._zCGmkPlOpg) had success.
There are few users who try to help on some like me and after creating it is uploaded.
Still not the newest i think but much newer than my old version.
Find version: fdkaac 1.0.0, libfdk-aac 4.0.0, VBR mode 4
All of these above steps were done less time than suite did run with no result.
They are not the solution I looked for but better than playing with suite hours by hours in hoping of getting the expected result.
It might be a good tool however overcomplicated for an end-user.
To use qaac, you either have to install iTunes, or unpack its codec core DLLs using the content of makeportable.zip from the qaac download folder (cabinet). That's pretty simple. And the best advantage of the Apple AAC codec it its superior configurability (FDK-AAC has only very distinct bitrate classes; may it have the advantage to be supported by foobar2000, but that is a severe disadvantage to me).
Encoding audio was much simple with lame.
Anyway your ini copid to build directory but suit also runs since 30 minutes.
Why it takes so much time to get a sinlge file which size propable will be around 1MB?
Ehm, well ... MABS is optimized to build ffmpeg. Disabling ffmpeg, unfortunately, does not reliably exclude all the libraries required for ffmpeg only. The author of MABS did not expect anyone using MABS for building "anything except ffmpeg". You may report this as issue. Or not. It may be "fixed". Or not.
At least ... once it has been built once, MABS will detect libraries being up-to-date and won't compile them unnecessarily.
I do not understand why so much time need to create ffmpeg.exe if it can be downloaded from official page (http://ffmpeg.org/download.html)?
No. Because of its license. The FDK-AAC license is not compatible to the GPL, not even to the LGPL. Hence it cannot be distributed in any ffmpeg build in binary form, even if it can be built.
GPL compatibility would require the license of a linked project to be GPL compliant ... starting with OpenSource code.
More than one hour but finally fdkaac.exe created.
It has the same version I already found by google (fdkaac 1.0.0, libfdk-aac 4.0.0, VBR mode 4).
However the file I found has size 4.5MB the created one only 0.7MB
The size difference is interesting.
I wonder about the reason. May it just be that I disabled UPX packing (which isn't very important in these days)...
Media Autobuild Suite doesn't strip anything. Locate strip.exe inside its folders, run it from a command prompt (cmd.exe or powershell, your choice) and pass the paths to the compiled executables or dll files as command line parameters, and it should reduce their size significantly.
It does not? Well, please search for do_strip() in build/media-suite_helper.sh and tell me what else this does (P.S.: if you selected strip=1 in build/media-suite_helper.ini). 8) OK, it may exclude some tools from being stripped. Probably for reasons.
Okay then, then that setting is not the default, and I must have missed it when configuring my build setup.
Hi
I did use last year created fdkaac (fdkaac 1.0.0, libfdk-aac 4.0.0, VBR mode 4) since.
After one year I wanted to check whether a new version is available.
Unfortunately I could not find any new fdkaac by google.
Does it means still media-autobuild_suite (https://github.com/m-ab-s/media-autobuild_suite) torture is the only way for casual user?
After download and run of course it do not create what I want.
Are there any new fdkaac since one year old ((fdkaac 1.0.0, libfdk-aac 4.0.0, VBR mode 4)) version?
If no I am happy to use it further.
If yes I ask help how to create new one?
Regards
Szabi
I am not sure if this will be useful or not but I have created fdkaac 1.0.0 binaries for Windows here:
- fdkaac-1.0.0-win32-ads.zip (http://www.andrews-corner.org/downloads/fdkaac-1.0.0-win32-ads.zip): For 32bit Windows (and 64bit of course)
- fdkaac-1.0.0-win64-ads.zip (http://www.andrews-corner.org/downloads/fdkaac-1.0.0-win64-ads.zip): For 64bit Windows
Tested fine here on a 64bit Windows 10 VM. Perhaps if you want to 'build your own' the details of the build are here:
Using MXE under Slackware Linux...
http://www.andrews-corner.org/mxe.html
If placing packages binaries in this manner is an issue I can ask for this post to be removed but the intention is to be helpful as well as to spin out some the endless lock down free time :).
Hi
This seems the same version I mentioned my post.
It seems there was no update since more than a year.
Whether is Most recommended AAC Encoder list by Hydrogenaudio Knowledgebase Wiki (https://wiki.hydrogenaud.io/index.php?title=AAC_encoders) list still valid?
The most recommended Apple AAC encoder is not available without itunes install.
2nd is gone with winamp and 3rd seems not updated any longer.
Nice story of AAC encoding.
Anyway I appreciate for your help, thx.
Regards
szabi
Well, aac encoders are pretty mature now, they won't be updated so much as they were twenty years ago. Use one that sounds best to you for the bitrate you want to use.
MSVC2015 compiles:
www.rarewares.org/files/aac/fdkaac-1.0.0-x64.zip (http://www.rarewares.org/files/aac/fdkaac-1.0.0-x64.zip)
www.rarewares.org/files/aac/fdkaac-1.0.0-x86.zip (http://www.rarewares.org/files/aac/fdkaac-1.0.0-x86.zip)
The x86 compile should run on XP.
I found these compiles to be considerably faster than the ones above but YMMV. ;)
Great improvement john33 :)
option win32 ads (kbps) john33 x86 (kbps) fdkaac32 (kbps)
--------- ------- ------- ------- ------- ------- -------
-b 64000 10.945x 63.968 46.779x 63.968 66.367x 63.968
-b 80000 10.286x 79.592 43.540x 79.592 62.164x 79.592
-b 96000 10.103x 95.216 42.794x 95.216 60.441x 95.216
-b 112000 9.739x 110.835 41.092x 110.835 58.837x 110.835
-b 128000 9.669x 126.461 40.903x 126.461 58.054x 126.461
-m 1 11.125x 95.128 47.408x 95.120 67.641x 95.120
-m 2 11.042x 101.083 47.156x 101.075 66.868x 101.075
-m 3 10.420x 113.114 44.085x 113.128 63.033x 113.128
-m 4 9.804x 134.535 41.583x 134.539 58.824x 134.539
-m 5 8.042x 238.083 33.124x 238.071 47.540x 238.071
Note: At the last minute I remembered having the fdkaac32 binary from somewhere else (contains string GCC GNU 9.2.0) that produces the exact same file sizes as john33 compile, but utterly fails binary comparisons.
Tests ran on Sandy Bridge processor, win32 OS.
Wow, do those numbers show that the binaries I produced are really painfully slow?
I think the speed of the binaries reflects the compiler used and the options which are used regarding instruction sets, possibly SSE/SSE2 (not sure if MMX is going to affect FDKAAC code).
There also is a difference in the code used, hence the slight difference in file size of the VBR modes. The john33 and GCC compiles match in exact file size with the only difference being rounding errors. (Might as well state for the new HA members that rounding errors are comparatively inaudible due to the internal math differences are very tiny numbers.)
I did actually try 32 and 64 bit Intel compiles but although they compiled OK, they failed at run time. I confess that I didn't spend any time trying to figure out why! ;)
I think the speed of the binaries reflects the compiler used and the options which are used regarding instruction sets, possibly SSE/SSE2 (not sure if MMX is going to affect FDKAAC code).
Interesting... I admit that I am more used to compiling under Linux than cross compiling for Windows but I sense a challenge here so I will dig a little deeper and see if I can optimise the compile (I did not set any extra flags with my current fdkaac binaries) and produce a faster binary. Where did the values such as: '10.945x' come from?
Well, I have spotted the '10.945x' numbers in the fdkaac output and I presume that this is where the testing output numbers have come from. I have updated the cross compiled binaries having made a few small compiling changes:
- Unbeknownst to me MXE was using an ancient version of gcc so I have set it to a more acceptable 9.3.0 and rebuilt all MXE packages. I note that MXE runs fdk-aac 2.0.0 rather than 2.0.1 but I doubt that is making much of a difference...
- I have taken an uneducated punt and added in standard (Slackware) compiler flags to the 32bit: CFLAGS="-O3 -march=i686 -mtune=i686" and to the 64bit: CFLAGS="-O3 -fPIC". Mind you Slackware is a little conservative than this and will usually use 02...
Small changes but on my testing I have gained a little speed but absolutely nothing like that seen in the other 2 compiled binaries. So I am either bumping up against a limit of cross compiling or more likely a limitation in my knowledge of cross compiling :).
I have
replaced the two online packages here (http://www.andrews-corner.org/downloads/) if anybody is interested in retesting...
@andrew.46 After re-running the tests I have the same encoding speeds as the previous version, as far as the 32-bit binary.
FYI, my script calculates encoding speeds by:
(number_of_samples / sampling_rate) / encode_time.
This way I can get figures many places past the decimal point. This comes in handy when benching xHE which needs 22khz or 32khz files.
edit: I was supposed to mention all tests were run on 16-bit 44khz stereo files.
@andrew.46 After re-running the tests I have the same encoding speeds as the previous version, as far as the 32-bit binary.
Thanks for having another look, I will leave things as they are then as I cannot improve from a cross compiling point of view. Interesting to see if you have tested fdkaacenc on a native Linux platform, a quick look on my Slackware system seems to suggest that encoding may be considerably faster than has been demonstrated here?
MSVC2015 compiles:
www.rarewares.org/files/aac/fdkaac-1.0.0-x64.zip (http://www.rarewares.org/files/aac/fdkaac-1.0.0-x64.zip)
www.rarewares.org/files/aac/fdkaac-1.0.0-x86.zip (http://www.rarewares.org/files/aac/fdkaac-1.0.0-x86.zip)
The x86 compile should run on XP.
I found these compiles to be considerably faster than the ones above but YMMV. ;)
Hi
I found this: fdk-aac-2.0.1.tar.gz (https://sourceforge.net/projects/opencore-amr/files/fdk-aac/)
It means a newer fdkaac version available on linux?
Regards
I haven't checked it in detail, but I believe the library versions to be the same. I think the 1.0.0 designation relates to the Windows wrapped version.
Someone at doom9 compiled fdkaac a while back. A quick comparison using my quite old XP box seems to indicate the 32 bit version is about 30% faster than the build john33 linked to back in April. There's also a 64 bit build.
I don't really understand the version numbers.
What do frontend version 1.0.0 and libfdk version 2.0.1 actually mean (as described in the doom9 thread)?
Doom9 post:
https://forum.doom9.org/showthread.php?p=1892458#post1892458
Mediafie link:
http://www.mediafire.com/file/jphuy8iljrf9mf0/fdkaac-v2.0.1.7z/file
Version numbers of this code are rather arbitrary anyway, since the code was ripped from the Android source code, and is only updated when newer AOSP packages are published from which to rip newer source files.
Not exactly new but here is fdkaac 1.0.1 using libfdk-aac 4.0.1 (VS2015):
www.rarewares.org/files/aac/fdkaac-1.0.1-x64.zip (http://www.rarewares.org/files/aac/fdkaac-1.0.1-x64.zip)
www.rarewares.org/files/aac/fdkaac-1.0.1-x86.zip (http://www.rarewares.org/files/aac/fdkaac-1.0.1-x86.zip)
Hi John,
Few weeks ago I come to check whether a new version exists.
I did find a link above to doom9 forum where I could download this version (fdkaac 1.0.1, libfdk-aac 4.0.1) added by user kedautinh12 (https://forum.doom9.org/showthread.php?p=1932064#post1932064).
I see you linked the same version however size of files are different.
Can u tell me what cause this differences?
Did you compare them regarding speed?
Regards
Szabi
john33 is a build with the visual studio 2015 compiler.
kedauthinh12 is a build with mingw64 GCC 10 compiler.
Even using the same compiler, you could get speed diferences.
I haven't compared these two specific builds so I can't comment.
As [JAZ] has said, different compilers will produce executables of different sizes and, on top of that, some people like to use 'packers' to reduce the size further.
Regarding relative speeds, I have no idea as I haven't compared them.
FDK-AAC v1.0.4 (x86 & x64)
Built on August 04, 2022, GCC 12.1.0
https://www.mediafire.com/file/y7x0nmiurqq9e7c/
Thank you
@john33 for all the updates on RareWares!
Hello. On the rarewares site, I see that version 1.0.5 of this codec is available. When I download the archive there is only an .exe file inside. There is no dll file. What else do I need to download and where? Also, the link https://sites.google.com/site/qaacpage/cabinet is dead.
FDK-AAC v1.0.5 (2023-03-08)
Built on March 08, 2023, GCC 12.2.0
DL :
https://www99.zippyshare.com/v/fHD6l5b9/file.html
Hello. On the rarewares site, I see that version 1.0.5 of this codec is available. When I download the archive there is only an .exe file inside. There is no dll file. What else do I need to download and where? Also, the link https://sites.google.com/site/qaacpage/cabinet is dead.
No dll required, it's statically linked.
Hi all,
This isn’t completely related, but all the fdkaac binaries I tested have a problem with -vbr 2 producing files that are the same size (or sometimes smaller) than -vbr 1. This problem also exists in the ffmpeg version (external libfdk_aac, to be clear that it is not included with the main ffmpeg binary).
The last binary that worked accordingly was dated Dec 2019.
These are the numbers I got FYI:
binary (32-bit) VBR-1 VBR-2 VBR-3 VBR-4 VBR-5 binary date
------------------------ -------- ------ -------- ------ -------- ------ -------- ------ -------- ------ ----------
fdkaac105-gcc122 91.38786 67.62x 89.97161 66.12x 106.5377 57.86x 142.2259 56.19x 212.2021 52.17x 2023/02/15
fdkaac105 91.38785 46.92x 89.97161 45.77x 106.5377 39.94x 142.2259 39.10x 212.2021 36.55x 2023/02/16
fdkaac104 91.38785 46.41x 89.97161 45.26x 106.5377 39.05x 142.2259 38.60x 212.2021 36.07x 2022/08/04
fdkaac32-102 91.38786 46.26x 89.97161 45.44x 106.5377 39.60x 142.2259 38.77x 212.2021 36.40x 2022/01/17
ffmpeg52 libfdk-056d3040 91.32316 68.80x 89.90692 67.58x 106.4733 58.78x 142.1620 57.62x 212.1392 53.63x 2022/08/23
ffmpeg51 libfdk-054ce304 91.32316 66.02x 89.90692 65.84x 106.4733 57.41x 142.1620 56.31x 212.1392 52.10x 2022/05/06
ffmpeg45 libfdk-053fca80 91.32316 65.84x 89.90692 65.82x 106.4733 57.51x 142.1620 56.35x 212.1392 52.45x 2021/09/10
fdkaac32-201 89.23201 65.90x 96.10717 65.75x 110.6252 61.05x 134.9785 57.77x 214.9248 50.40x 2019/12/08
fdkaac32t 89.23201 66.10x 96.10717 65.24x 110.6252 61.01x 134.9785 57.42x 214.9248 50.44x 2019/12/08
fdkaac-100-x86 89.23201 46.51x 96.10717 46.28x 110.6252 42.95x 134.9785 40.36x 214.9248 35.57x 2020/04/13
fdkaac-100-win32-ads-new 89.23414 10.84x 96.10956 10.78x 110.6260 10.06x 134.9776 9.51x 214.9284 8.49x 2020/04/23
fdkaac-100-win32-ads-old 89.23414 10.93x 96.10956 10.83x 110.6260 10.15x 134.9776 9.58x 214.9284 8.52x 2020/04/13
@Destroid - Maybe you should report it to the authors then
https://github.com/nu774/fdkaac/
https://github.com/mstorsjo/fdk-aac/
@NetRanger Neither I nor mstorsjo is the auther of the FDK-AAC codec.
The codec is developed by Fraunhofer IIS.
@Destroid I believe it's changed since this commit:
https://github.com/mstorsjo/fdk-aac/commit/443d38963e804ce1133e2338937e1cf389092b52
As the latest aacEncoder.pdf doc says:
The VBR mode 1 is tuned for HE-AACv2, for VBR mode 2, HE-AACv1 should be used. VBR modes 3-5 should be used with Low-Complexity AAC.
Although encoder API (and fdkaac command line) allows setting VBR mode and AOT(profile) independently, I think you'd better follow the recommendation.
@NetRanger
Neither I nor mstorsjo is the auther of the FDK-AAC codec.
The codec is developed by Fraunhofer IIS.
That is so true but i maybe thought that this was something u guys could look into