Open den-jones opened 11 months ago
@ychsieh please triage
There's a very real tradeoff between quality and buffering that is exacerbated on the earlier pages of the story (especially the first page). When the use first loads a story, the videos have not yet downloaded enough to play back, and so the highest priority thing is to download the bytes of the video as quickly as possible. Having higher quality video obviously makes this more costly to download.
We should tread carefully here, especially given the data on (a) higher quality leading to rebuffers, and (b) rebuffers leading to abandonment.
cc @banaag please chime in if you have any addtl info
Description
When I create a Web Story that contains a video on each page of the story and I enable Video Cache in the settings of the Web Story plugin, the video on the first page is always shown in bad quality (data-bitrate=”720″) the first times I look at the Web Story.
The cached videos on the next pages are always shown in the better quality. (data-bitrate=”2000″)
It only shows the best quality (data-bitrate=”2000″) on the cached video on the first page when you refresh the first page a couple of times.
My questions:
Reproduction Steps
Here is an example of a Web Story that contains videos on each page to make it easier for you to test: https://liesbethdiels.be/web-stories/video-quality/
When I inspect the html of the page I can see that the cached video with the bitrate of 2000kb/s is not in the html code of the first page or if it is in the source code, it is the 3rd url in the source (the video player plays the first url if I'm not mistaken). Only when you refresh the page a couple of times, the url with the data-bitrate=”2000″ appears or becomes the first url.
Relevant Logs
No response
Browser(s) Affected
No response
OS(s) Affected
No response
Device(s) Affected
No response
AMP Version Affected
No response