Issue 1772 in webm: vpx_temporal_svc_encoder's lower temporal layers fail to decode

[anton… via monorail]

Status: Untriaged
Owner: ----
Labels: Type-Bug Pri-2
Components: libvpx

New issue 1772 by anton...@easy-bits.com: vpx_temporal_svc_encoder's lower temporal layers fail to decode
https://bugs.chromium.org/p/webm/issues/detail?id=1772

For temporal svc it is expected for the lower temporal layers to be decodable without the upper ones e.g. we should be able to decode layer 0 without the other ones. Instead when trying to decode to not full frame rate using vpxdec or inline API one gets:
"Warning: Failed to decode frame 2: Corrupt frame detected
Warning: Additional information: Failed to decode tile data"

Version: v1.11.0-226-g9d279c88c
OS: Ubuntu 18.04.4 LTS

To reproduce encode video with any mode above 0: ./examples/vpx_temporal_svc_encoder ./9.yuv svc vp9 256 256 1 25 9 0 0 1 1 5000 5000
And then try to decode first temporal layer:
./vpxdec --i420 -o 'out%1.yuv' svc_0.ivf

Seems like the issue has to do with updates to entropy context.

--
You received this message because:
1. The project was configured to send all issue notifications to this address

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

[jz… via monorail]

Updates:
Cc: ji...@google.com
Owner: mar...@google.com
Status: Assigned

Comment #1 on issue 1772 by jz...@google.com: vpx_temporal_svc_encoder's lower temporal layers fail to decode
https://bugs.chromium.org/p/webm/issues/detail?id=1772#c1

(No comment was entered for this change.)

[anton… via monorail]

Comment #2 on issue 1772 by anton...@easy-bits.com: vpx_temporal_svc_encoder's lower temporal layers fail to decode
https://bugs.chromium.org/p/webm/issues/detail?id=1772#c2

When error resilient mode is enabled the issue goes away

[mar… via monorail]

Updates:
Status: WontFix

Comment #4 on issue 1772 by mar...@google.com: vpx_temporal_svc_encoder's lower temporal layers fail to decode
https://bugs.chromium.org/p/webm/issues/detail?id=1772#c4

Error resilient mode needs to be on/enabled for this case, as noted in #2.