chris, can you take this one? or re-assign appropriately. thanks

jwalczak, do you want the error to just be logged, or are you hoping to do specific error handling? I think we just treat all errors the same for now - so bool is all we've needed. Feel free to send an illustrative patch.

I would suggest to update FFmpegGlue::OpenContext() to return the actual result of avformat_open_input() (i.e. int instead of bool). This way all the places like FFmpegDemuxer could distinguish what has actually happened e.g.:
- there was an IO error
- given container is not supported
- content is corrupted
- etc.

This sounds fine, but I'm curious how you will respond to the different error types? Do you have some recovery in mind? Do you just want a more verbose error message logged to chrome://media-internals?

At the beginning just proper logs in media. Additionally we have a downstream project that needs to distinguish more error codes. But in general it seems incorrect to hide error codes from users of the glue code.

Marking as WontFix unless someone wants to do something with these error codes; it's fine to hide stuff like this unless we actually have a use for it.