pfeatherstone

You can do screen grab with this too. You would need to check the ffmpeg documentation. You need to lookup what to set ```args.filepath``` to, then set ```args.input_format = "x11grab"```...

For rtsp, you could do something like: ``` dlib::video_demuxer_args args; args.filepath = "rtsp://localhost:554/mystream"; args.input_format = "rtsp"; args.format_options = {{"max_delay", "5000000"}, {"rtpflags", "send_bye"}, {"rtsp_transport", "tcp"}}; dlib::video_demuxer cap(args); ``` You might need...

@arrufat @davisking Shouldn't all the cmake stuff apply to the unit test CMakeList.txt file, not the main one?

Rather than using http://dlib.net/file_to_code_ex.cpp.html to encode video into the unit tests, can we use something like https://github.com/graphitemaster/incbin to embed data into the ```dtest``` executable? It can embed arbitrarily sized files,...

Apparently ```std::pair``` has a non-trivial copy constructor which means ```memcpy``` gets upset. Weird.

So i used http://dlib.net/file_to_code_ex.cpp.html to encode a 50s clip, and the compiler timed out after 15 minutes

I could use a much smaller clip but, encoding the file as a gigantic string puts a very low upper bound on file sizes.

I tried to set the installation path of ffmpeg/libav* using ```PKG_CONFIG_PATH``` environment variable, but i don't think cmake picked it up. Would it be possible to have another option in...

Having said that, it's up to the user's build tools to link to ffmpeg correctly, not dlib's cmake file. I guess we still need something like this for the unit...

Currently i don't think cmake is using ```pkg-config --libs libavdevice``` to get the complete linker flags (for libavdevice). I think it's just using -lavdevice.