Some videos can't loop
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
People
(Reporter: tgnff242, Assigned: alwu)
References
(Regression, )
Details
(Keywords: nightly-community, regression)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0
Steps to reproduce:
This is the same bug/STR as Bug 1789103 with a different regressor.
You can use the video in Bug 1789103#comment 12, but make sure its sound is on.
Actual results:
No loop.
Expected results:
Comment 1•2 years ago
|
||
:alwu, since you are the author of the regressor, bug 1262276, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 2•2 years ago
|
||
What's the expected behavior here? I can play the video with sound, and once it reaches the end initiate play again.
Yes, that is the expected behaviour, however, unless I set media.seamless-looping-video:false, it's not met. The video stops at 00:21, it never reaches the end of 00:22 and it doesn't loop.
It doesn't seem to affect the current release channel at v115, but Nightly when was at v115 was affected.
| Assignee | ||
Comment 5•2 years ago
|
||
I will take a look at this.
| Assignee | ||
Comment 6•2 years ago
|
||
I can't reproduce this on Nightly 117 on Windows 11, I suppose this problem might have been fixed by the recent patches I landed for seamless looping. Could you try to use the latest Firefox Nightly to see if this issue still exists on your side? Thank you.
Yes, I have reproduced it on Nightly 20230711040652 on both Linux and Win11.
Something I hadn't thought of checking before, is hardware video decoding. Indeed, if I disable it, the video loops as expected (both OSs). That's the reason it didn't reproduce on the Release channel before, since I always test in clean profiles and it's disabled by default on Linux.
So to recap, 1) the sound needs to be turned on and 2) hardware video decoding needs to be supported and enabled.
| Assignee | ||
Comment 8•2 years ago
|
||
Thanks, I can now reproduce this. Will take a look on this.
Comment 9•2 years ago
|
||
Set release status flags based on info from the regressing bug 1262276
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Comment 10•2 years ago
|
||
I'm going to fix the issue in bug 1844772.
Updated•2 years ago
|
Description
•