Hacklin

You could try [this build script](https://github.com/ponchio/untrunc/pull/114). See: `./build.sh --help` for help on its usage.

Untrunc doesn't only repair files; it also allows you to analyze a file (option `-a`). Changing the log level allows you to change the presented info by FFmpeg/Libav, when analyzing...

The code has quite some logging in `#ifdef VERBOSE` sections. Do all that `#ifdef VERBOSE` logging belong in the `debug` log level?

@anthwlock In your fork, you use the log levels/modes: `E`, `W`, `I`, `V`, `VV`. Could you describe when to use Verbose (`V`) and VeryVerbose (`VV`) ?

Logging (Severity) Levels: - Programming All logging levels should be available for use and they should follow some _"standard"_. This allows a programmer concentrate on the code, instead of thinking...

Hmmm , In `file.cpp` you use `VV` like `Trace`, but in `nal-slice.cpp` you use `VV` for user output for `-a` option. And I see that you use `V` like `Debug`.

You are using @anthwlock [Untrunc](https://github.com/anthwlock/untrunc) repository. Please, post issues [there](https://github.com/anthwlock/untrunc/issues) and close this issue.

You should split this PR into seperate ones, as you do to much in a single PR. Notes: > - removed dependency on internal libavcodec code (added sps-decoder) You forgot...

Like your idea that if you build the docker with an empty context, you use the sources from the git master.

> You **should not** access it if ... And **that** is a problem. sps_info_ is a **public** member. Meaning that anyone at anytime can access and change it. If one...