anybody using MP4Box built with jb-alvarado's media-autobuild_suite?

[stax76]

Ligh has mentioned this built so I investigated it and am now interested to use it for StaxRip. It has a compressed file size of only 1 MB compared to 2,3 MB of the official built. The official build requires VC++ 2010 to be installed which I don't like because it seems almost everybody has migrated to VC++ 2013.

Has anybody good or bad experience with it? Dependency Walker shows a MSVCRT.DLL dependency. Will it run on Win7 and Win10 without the need for installing a runtime? Are all common formats supported for muxing and demuxing?

[LoRd_MuldeR]

1. To use binaries compiled by Visual C++, you do not need to install Visual Studio. You may need to install the Visual C++ Runtime libraries, depending on how the application was linked against the Visual C++ Runtime. But don't worry! You can install the Visual C++ 2005, 2008, 2010, 2012 and 2013 Runtime libraries side-by-side perfectly fine. Chances are high you have them all (or most of them) on your system anyway, because many applications install them "silently" during setup.

2. Nonetheless, starting with Visual Studio 2010, the shared Visual C++ Runtime libraries are just "normal" DLL files. There's no WinSxS headache anymore, as was the case with Visual Studio 2008. Therefore, you can simply copy the suitable Visual C++ Runtime DLL's (e.g. "msvcr100.dll" and "msvcp100.dll" for Visual C++ 2010) into the same directory as the EXE file and that's it! There is no need to actually "install" the Visual C++ Runtime anymore. It doesn't hurt though.

3. The "msvcr.dll" and "msvcp.dll" files (note: no version number included in the file name!) are the C/C++ Runtime libraries that ship with the Windows operating system. They are used by the Windows system programs and don't need to be installed separately. The are always present. The "msvcr.dll" is also used by everything that has been compiled with MinGW/GCC. That's because MinGW/GCC doesn't have it's own C Runtime on Windows. It does have it's own C++ Runtime though.

[stax76]

Thanks for the info, do you think it's worth a try using a slim mingw build or should I just stick to the bigger official build plus the 2 runtime DLLs? It should of course be robust and support as many formats as possible.

[LoRd_MuldeR]

I don't think that you can say that MSVC or MinGW is more/less robust in general. Or that one of them produces faster/slower code in general. They both have their quirks at times.

Which compiler is recommended for a specific project probably depends mostly on what the developers used for development, testing and optimization.

And which formats are supported by MP4Box isn't related to the compiler at all. It depends on what version of M4Box was used. And maybe also on which optional libraries were enabled in the build. But that's it!

(Personally, I usually prefer MSVC binaries with static C/C++ Runtime, because it gives a 100% stand-alone binary that doesn't depend on anything else. But it really depends)

[stax76]

The file size is so small that I'm concerned features are missing like supported formats. Selur gave me a build and I tested various formats and everything worked well so I'm gonna use it. It's great that it's very small and a single file only.

[Selur]

File size is small since the binaries are stripped if I build them using media-autobuild_suite. (don't use the upx to compress them since the false-positives of av-software are just to annoying)