Srikanth Peddibhotla
Srikanth Peddibhotla
Related issue: https://github.com/amzn/exoplayer-amazon-port/issues/42
Can you send your address to [email protected] ? We'll check internally if we have spare devices to share.
BTW, I wound't tag it as a device specific issue. Any device can choose to support a large buffering at input port of video decoder (as the memory capacity of...
Thank you for reporting. [This](https://github.com/amzn/exoplayer-amazon-port/commit/cf81cea06d5e432b4f6c383ae2127725b7ceaf72) patch is supposed to handle switching between dolby and non-dolby content. We'll investigate this.
We found the root cause and are working on it. There will be two parts to it. One in the OS that will updated in the next system release cycle....
Fixed in https://github.com/amzn/exoplayer-amazon-port/commit/2ce7930bf834edbf2aa3de1cb8e445f6625d95c3 Currently, you need to wait for OS update also for this patch to get affect. If you want to test with existing OS, return true in useSurroundSoundFlagV17...
This will be rolled out around end of Feb 2019.
acknowledged. investigating
The decoder has a max buffer that can hold upto 2 seconds of video frames. Hence Exo ends up spending lot of time in queuing up these buffers since the...
Well, this sets the max size of every frame. I tried to find if there is any API to configure number of input buffers, but Looks like there is none....