Unexpected droppedVideoFrames while using a-videosphere

[Vesper0704]

trafficstars

Description:

• A-Frame Version: 1.3.0
• Platform / Device: Intel Mac OS X 10_14_4, Chrome/108.0.0.0
• Reproducible Code Snippet or URL:

let quality = document.querySelector('a-videosphere').object3D.children[0].material.map.image.getVideoPlaybackQuality();
decoded = quality.totalVideoFrames;  // 657
dropped = quality.droppedVideoFrames; // 646

Actually, the frames are decoded successfully and the playback is not stalled. Since droppedVideoFrames are defined as the frames that are typically dropped either before or after decoding when it's determined that it will not be possible to draw them to the screen at the correct time, maybe it is reasonable that there are so many droppedVideoFrames due to partial render of the 360 video.

I wonder if there is any way to measure the dropped frames in panorama video when using a-videosphere?

[dmarcos]

Not sure what getVideoPlaybackQuality actually measures when applied to rendering video as a texture in WebGL vs a regular video on the 2D DOM.

[Vesper0704]

Thanks. I'm gonna use requestVideoFrameCallback to get the presentedFrames. But I am still curious about how getVideoPlaybackQuality works in 3D rendering.

[Vesper0704]

It seems that presentedFrames derived from requestVideoFrameCallback is less than totalVideoFrames. But they are still close. Maybe it is not a good solution.