search

ericmckean / webm

Automatically exported from code.google.com/p/webm
0 stars 0 forks source link

Corrupted frame warning in vp9 decoder #689

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What is the expected behavior? What do you see instead?
vpxdec decoded a test clip with warning.

./vpxdec 2T-Sp6vqwq4.original.272.webm --noblit --summary --limit=500
500 decoded frames/500 showed frames in 20138286 us (24.83 fps)
WARNING: 98 frames corrupted.

What version are you using? On what operating system?
libvpx master branch (commit 40e173ac42581159b8a96f8a000445e1fba475af)

linux

Can you reproduce using the vpxdec or vpxenc tools? What command line are
you using?

Yes.
./vpxdec 2T-Sp6vqwq4.original.272.webm --noblit --summary --limit=500

Please provide any additional information below.

Original issue reported on code.google.com by yunqingw...@google.com on 4 Jan 2014 at 1:27

GoogleCodeExporter commented 9 years ago

Original comment by yunqingw...@google.com on 4 Jan 2014 at 1:28

GoogleCodeExporter commented 9 years ago

Original comment by yunqingw...@google.com on 6 Jan 2014 at 5:17

GoogleCodeExporter commented 9 years ago 
It seems this issue was about the motion vector limit. James and I had run into 
similar problem in 4K video, and it was fixed by

https://gerrit.chromium.org/gerrit/#/c/67843/
https://gerrit.chromium.org/gerrit/#/c/68065/

Can we try to verify that the encoder used to create this bit-stream was after 
the change applied?

Original comment by jingn...@google.com on 6 Jan 2014 at 6:49

GoogleCodeExporter commented 9 years ago 
It should have:
https://gerrit.chromium.org/gerrit/#/c/68065/ is v1.3.0-247-ga67e654
encode was with v1.3.0-328-gc263418.
I'm rerunning to verify, the source is 4K.

Original comment by jz...@google.com on 8 Jan 2014 at 1:37

GoogleCodeExporter commented 9 years ago 
James, did we verify that this issue was fixed?  Seems to be a known problem 
and should have been fixed last December. Thanks.

Original comment by jingn...@google.com on 18 Jul 2014 at 4:18

GoogleCodeExporter commented 9 years ago 
I verified that this is still working with recent code: v1.3.0-3514-g597ce31. 
We have some simple large frame tests now that should prevent regressions.

Original comment by jz...@google.com on 23 Jul 2014 at 6:02