lag and vpx_codec_control_

[GoogleCodeExporter]

If you call vpx_codec_control_  and then pass a frame to the encoder the 
control takes affect on the next frame you get back from the encoder not the 
one that you pass to the encoder.   That is different from the flags you pass 
which attach to the frame you pass.   

As an example: Imagine a lag of 25 frames in a file of 100 frames.  When you 
call vpx_codec_encode the first 25 times you get nothing back.   So if you call 
vpx_codec_control_ on any of the first 25 files it will affect frame 0, not 
frame 1-24..     If you call it on frame 35 it will affect frame 10.  

I think that we lack a test that tests this affect and perhaps documentation to 
make it understood. 

Original issue reported on code.google.com by jimbanko...@chromium.org on 6 Sep 2013 at 11:56

[GoogleCodeExporter]

Original comment by jimbankoski@google.com on 6 Sep 2013 at 11:57

• Changed state: Assigned

[GoogleCodeExporter]

Original comment by ya...@google.com on 17 Oct 2013 at 10:17