QTLite is probably in most places which is why it isn't included in the K-Lite codec pack. K-Lite has done an effort to go completely legal. I'm not sure if they currently offer a legal product or not. I'm not sure about Real Alternative though.

As for AAC, MediaMonkey of course needs an integral solution (and has one with the AAC plugin) for playback, tagging as well as analysis. You might only analyze volume, but other use MediaMonkey for other tasks like tagging and playback.

I am not suggesting that MM should use ffdshow. I mentioned it just as an example what is IMHO much better to use than QT and/or some codec pack for the _reproduction_, after you mentioned the reproduction of AAC files as an advantage of using QT. As I said, I am not using MM for reproduction and I don't care if it could reproduce AAC/MP4 files or not, with or without QT.

I'd like to use MM for analyzing/leveling of aac files and this is what the subject says. My suggestion was AACGain for that. It is not a plug-in, it has a C++ source code which could be implemented directly into the MM program in same way as it has implemented MP3 leveling using MP3Gain source code. So I suppose this is "self-contained" which you are talking about.

By the way, AFAIK all those codec packs and QT/RM alternatives are illegal since they distribute parts of some third-party commercial product.

You're being a bit picky though. What to do with those who want to avoid ffdshow or AACGain plugin because they don't like it? If it works well it shouldn't be a problem. I haven't had issues with QTLite, Real Alternative and the K-Lite Codec and have been using them for years.
I'd rather have a self-contained solution that includes all necessary components then rely on ffdshow, I really don't care though what solution is incorporated as long as it works.

At least agree that file editing/playback should use a native solution and not third party components installed on the machine.

AFAIK, MM is using MP3Gain code (I suppose so because his author is mentioned in the about box) which has same license as AACGain.

I do see a problem installing QuickTime and I would rather continue using AACGain than MM with QT. I really don't want to use some codec pack, even if it doesn't introduce a trouble. I have a standpoint if I cannot reproduce some file with ffdshow, such file is not worth to be reproduced at all. But it is hardly imaginable that some file cannot be reproduced by ffdshow when you look at its settings dialog box. And yes, you are right about RealPlayer, it is also on my top list of avoidable software.

Remember that open source doesn't equal available. If you have a commercial software depending on the license used on a particular open source component/software it wouldn't be an option.

Anyway I don't see a problem with installing these components in case you manage these files. And if you don't wish to install QuickTime there is the AAC plugin you can purchase. And yes I do support full native support of all audio file formats in MediaMonkey, but for me it's from a user friendly perspective where it's obvious that the requirement of additional components like WMP components and QuickTime is causing a lot of users issues.

You do mention the evilest of all components, Java! Together with QuickTime and Real Player my most hated software top 3. Codec packs on the other hand have served me well for many years.

I don't like to use some multi-mega-software for some trivial task. This is a reason why I hate .NET and Java. I don't like to use something which I don't want, which is hidden somewhere in my system and starts even when I don't need it. Too much codecs could lead only to trouble and this is a reason why I avoid so called codec Packs.

To be a honest, I am not using MM for playback at all, and I really don't need QuickTime to reproduce AAC/MP4 files since player which I use could reproduce such files without installed QuickTime. Well, Apple is not inveting that format, why should it have exclusive right to reproduce such files? What about ffdshow? It could also be used to reproduce such files with any DirectShow player, it is open sourced and works very well.

Regarding about AACGain disclaimer and responsibility, similar thing have many software, even my scripts

... not to mention the ominous warning on the page you've linked to:

"BACK UP YOUR MUSIC FILES BEFORE USING AACGAIN! THIS IS EXPERIMENTAL SOFTWARE. THERE HAVE BEEN BUGS IN PAST RELEASES THAT CORRUPTED MUSIC FILES. I AM NOT RESPONSIBLE FOR DAMAGED FILES."

Well it also serves other purposes like playback of M4A files. I understand your point, but in this day and age 10MB isn't that much, it's much more important how resource hungry the solution is.

I'd still like to see this natively supported in MediaMonkey though.

Of course I know for it, but even it is 9.4 MB. Why should I use such big piece of junk for something which could be done with just 300 KB? There is already a source code for AAC leveling, it is simple to implement as it is MP3 leveling.

You can use QuickTime Alternative if you don't like QuickTime. In any case the full native support of the different file format has been requested so that MediaMonkey doesn't depend on third party components.

AACGain is just 300 KB open source, why we need such multi-MB garbage as QuickTime just to analyze aac files?