<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Impress media player REPEAT toggle function does not loop MP4 video clip" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113021#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Impress media player REPEAT toggle function does not loop MP4 video clip" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113021">bug 113021</a> from <a class="email" href="mailto:rdbingham@verizon.net" title="R. Bingham <rdbingham@verizon.net>"> R. Bingham</a> <pre>Except that there *can be* different user-perceptible behavior depending on the combo of OpenGL use state and graphics sub-system for a given display. See bug 112958 for an example - different video presentation behavior when using OpenGL and dragging the *playing video* from one display/graphics stack to another and back. I agree that the probability of different behavior is low between among CPU embedded graphics sub-systems (Intel vs. AMD vs. whatever). But as soon as there is an external GPU graphics sub-system in the mix that is in effect an independent stack typically driving dedicated displays, user-perceptible LO behavior can be broken *differently*. Its the usual and annoying platform fragmentation the app developers have had to deal with since forever. Probably the player's Repeat (Loop) function *is* broken in a universal way but I am cautious in preemptively ruling out the various graphics stacks as breaking it in different ways after experiencing <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Embedded video clip play on NVIDIA display (yet another OpenGL workaround)" href="show_bug.cgi?id=112958">bug 112958</a>.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>