decdef12f5
* typo * - added compile time information to audio object. Not convinced this is needed actually. I'm perfectly happy just using the ffmpeg::frame object. I'm pretty sure I'm the only user who cares about audio. - created resizing_args and resampling_args * smaller videos for unit tests * shorter videos for unit tests * - decoder and demuxer: you now resize or resample at the time of read. therefore you don't set resizing or resampling parameters in constructor, but you pass them to read() - added templated read() function - simplified load_frame() * inherit from resizing_args and resampling_args * reorganised the tests to segragate decoding, demuxing, encoding and muxing as much as possible * much more basic example * demxing examples split * examples * fixing examples * wip * Fix load_frame() * added frame - specific tests * - makes sense to have a set_params() method rather than constructing a new object and moving. I mean, it works and it absolutely does the right thing, and in fact the same thing as calling set_params() now, but it can look a bit weird. * notes on defaults and good pairings * Update ffmpeg_demuxer.h Watch out for `DLIB_ASSERT` statements. Maybe one of the unit tests should build with asserts enabled. * Update ffmpeg_details.h * Update ffmpeg_muxer.h * WIP * WIP * - simplified details::resizer - added frame::set_params() - added frame::clear() - forward packet directly into correct queue * pick best codec if not specified * added image data * warn when we're choosing an appropriate codec * test load_frame() * - for some reason, you sometimes get warning messages about too many b-frames. Resetting pict_type suppresses this. - you can move freshly decoded frames directly out. * callback passed to push() * I think it's prettier this way * WIP * full callback API for decoder * updated tests * updated example * check the template parameter is callable and has 1 argument first before getting it's first argument * Potential bug fix * - write out the enable_if's explictly. It's fine. I think it's clear what's going on if someone cares - guard push() with a boolean which asserts when recursion is detected * pre-conditions on callbacks: no recursion --------- Co-authored-by: pf <pf@me> Co-authored-by: Your name <you@example.com> |
||
|---|---|---|
| .github | ||
| dlib | ||
| docs | ||
| examples | ||
| python_examples | ||
| tools | ||
| .gitignore | ||
| CMakeLists.txt | ||
| LICENSE.txt | ||
| MANIFEST.in | ||
| README.md | ||
| setup.py | ||
dlib C++ library 
Dlib is a modern C++ toolkit containing machine learning algorithms and tools for creating complex software in C++ to solve real world problems. See http://dlib.net for the main project documentation and API reference.
Compiling dlib C++ example programs
Go into the examples folder and type:
mkdir build; cd build; cmake .. ; cmake --build .
That will build all the examples. If you have a CPU that supports AVX instructions then turn them on like this:
mkdir build; cd build; cmake .. -DUSE_AVX_INSTRUCTIONS=1; cmake --build .
Doing so will make some things run faster.
Finally, Visual Studio users should usually do everything in 64bit mode. By default Visual Studio is 32bit, both in its outputs and its own execution, so you have to explicitly tell it to use 64bits. Since it's not the 1990s anymore you probably want to use 64bits. Do that with a cmake invocation like this:
cmake .. -G "Visual Studio 14 2015 Win64" -T host=x64
Compiling your own C++ programs that use dlib
The examples folder has a CMake tutorial that tells you what to do. There are also additional instructions on the dlib web site.
Alternatively, if you are using the vcpkg dependency manager you can download and install dlib with CMake integration in a single command:
vcpkg install dlib
Compiling dlib Python API
Before you can run the Python example programs you must compile dlib. Type:
python setup.py install
Running the unit test suite
Type the following to compile and run the dlib unit test suite:
cd dlib/test
mkdir build
cd build
cmake ..
cmake --build . --config Release
./dtest --runall
Note that on windows your compiler might put the test executable in a subfolder called Release. If that's the case then you have to go to that folder before running the test.
This library is licensed under the Boost Software License, which can be found in dlib/LICENSE.txt. The long and short of the license is that you can use dlib however you like, even in closed source commercial software.
dlib sponsors
This research is based in part upon work supported by the Office of the Director of National Intelligence (ODNI), Intelligence Advanced Research Projects Activity (IARPA) under contract number 2014-14071600010. The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of ODNI, IARPA, or the U.S. Government.