pfeatherstone

@davisking any ideas on how to do unit testing for this? I imagine doing the whole trick of compressing, base64-ing and inserting into a header file isn't sensible for an...

> > @davisking any ideas on how to do unit testing for this? I imagine doing the whole trick of compressing, base64-ing and inserting into a header file isn't sensible...

The code also works out the box with rtsp and camera devices. Those would be harder to test in a unit test. Unless you fancy hosting a dummy rtsp stream...

The natural follow up from this is gonna be ```dlib::video_writer```, which won't require much effort (it's similar API calls). So I think i will reinstate the following header hierarchy :...

i've added something so you can read the metadata of the video stream. You can then detect stuff like whether the video is rotated. Very useful. We could then correct...

At some point I will finish this. I'm using it all now and works fine but don't quite have the time to push it over the edge and make it...

We will be able to make this way more configurable than opencv's wrappers. Like we can set CRF values, gop sizes, the list is endless. Haven't quite decided on how...

By the way I was talking about a video encoder, not dlib::video_capture. For dlib::video_capture the options are minimal and API can be fairly tight.

For a video encoder on the other hand, most of the codec specific options are forwarded by the libavformat API as strings. Like {"preset", "slow"} for H264. So however the...

Some options will be standard and common across all codecs, and therefore we can make them typed of course, even strongly typed if we can be bothered.