Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

codec.queueSecureInputBuffer() calls taking too long for 60fps on AFTTIFF43 and INSIGNIA_NS_43F301NA22 #123

Open
mbolaris opened this issue Oct 17, 2022 · 0 comments
Labels

Comments

@mbolaris
Copy link

In our testing with ExoPlayer on 60fps Widevine encrypted content we've observed calls to codec.queueSecureInputBuffer() are taking ~8-12ms on the AFTTIFF43 and INSIGNIA_NS_43F301NA22. On the other platforms, we've checked the time is around ~4ms. These long queueSecureInputBuffer() times combined with needsSynchronizationWorkaround being set in doQueueSecureInputBuffer() prevent ExoPlayer from processing an audio and video sample on average every 16ms.

If we don't set needsSynchronizationWorkaround and feed audio and video in parallel we can mostly meet the ~16ms average time but it's still close.

Our questions are:
Any idea why codec.queueSecureInputBuffer() calls are so slow on the AFTTIFF43 and INSIGNIA_NS_43F301NA22? Is there anything we can do about it?

Any idea if it's safe to disable the needsSynchronizationWorkaround for these and other FireTV platforms so that we are calling codec.queueSecureInputBuffer() for audio and video in parallel from separate threads? On other platforms(Broadcom) we see video corruption without needsSynchronizationWorkaround but so far our limited testing of FireTV devices has not shown any issues with needsSynchronizationWorkaround set to false.

abshankr pushed a commit that referenced this issue Dec 27, 2022
PiperOrigin-RevId: 476376463
(cherry picked from commit 8623f1f01657abc6a1359f3677a59d1cbde07b37)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant