Re: Unexpected quasi-pause when switching desktops
The Wanderer <[email protected]> Tue, 30 Aug 2022 09:03:40 -0400
| Newsgroups | gmane.comp.video.mplayer.user |
|---|---|
| Organization | This space intentionally left blank. |
| Message-ID | <[email protected]> |
On 2022-08-29 at 13:55, Reimar Döffinger wrote: >> On 29 Aug 2022, at 16:25, The Wanderer <[email protected]> >> wrote: >>> I don't think much changed in MPlayer, so if it's a regression >>> I'd think compositor/window manager/GPU driver to be a more >>> likely cause than MPlayer to be honest... >> >> Seems likely, yes. Doesn't rule out the possibility of being able >> to find a way to change MPlayer to correct for it, > > Ah, right, the solutions question. I was only looking at the "figure > out what goes wrong" question so far. A really good solution would > need really understanding the problem first. Inevitably and necessarily so, yes. > But if it's vsync or lack of GPU resources I would have thought that > -framedrop should work. Have you tried that? I have now, along with (per your earlier suggestion) '-vo gl:swapinterval=0'. Neither made any apparent difference. My current guess/suspicion is that something about my larger rendering-stack config (possibly even the underlying driver itself) now does detection of whether or not the display surface is currently visible and scales back the rendering resources allocated to it if it isn't, and this is an unavoidable side effect of that. As I said, I don't think the possibility of MPlayer being able to do something differently to compensate for such an environment is likely enough to justify the effort resources we'd need to invest to even verify whether it's possible at all, not given the extremely limited scale of those resources currently available. > Some people might not want to use it, for example if you are > sensitive to frames being dropped incorrectly. But I would think for > most users it's a good option to use anyway. It's documented in the man page as being for the benefit of (and, by implication, only offering any benefit for) slow computers - where "slow" is presumably relative to the needs of video being played and the display output involved - so I've been omitting it on the basis that this is not in any way a slow computer. I know there are contexts in which I can notice the results of framedropping, but I'm not sure whether it would be prominent enough to be a reason not to use the option. I'll take this under consideration as things move forward. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw _______________________________________________ MPlayer-users mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEJCOqsZEc2qVC44pUBKk1jTQoMmsFAmMOCqwACgkQBKk1jTQo Mmu4cBAAo/CBFtfb6f/WiMt2jHL+0eAON6KTWYJkD7iGhYXdumIIx5a1IEwtDD+T XPeWACeIYTkEaodZisayxi0T1NWUsoS0rMh3O9CkJj/Ue/6cRIndQ0gNDPKFDwR4 Ht3/ZbrnwjTh11xK6xWQpI6BVHEvNwc12030DqGNBU5TKeCIg6MbLOyuQv7th9kD WafQcxDhHhX6xp2IMQsIxFee7r76k48e1Lt9uJbl34z0h77ZcJK0SaHpV+dyGOfp YWTS72H/ZBunpCjTYi8TUTBc7cmgrkoqdphLhBWhLB6VKzHPJZy+JYZz9n/Psh2Z 9PjWXNJBjHehmqGliWSUOeXS5XyoyZNxkFCBVUvyLXRA/vB3GOFN2OrYptYVRS70 OaJzcbBELc3TdZYV/D5M8Fgpk2dE4+w0rg3wxkAV1Jt08cnrDrYJ9DdSzj1GeXLB JAYgANuMvEu/8hgMmAfCVoambwL3XcnudtWi0sJvLeNmKdGiVB5nnzcO8ICV20Vd iCH8Lpl5jQV7AOxVE1Hl6k+TpAZcjdqj7nFlGM7taOACBfwW0XI72uOS3Z51eNup b2mZWt0HEBxC5jBZVjsWGuLTW2qO0DkzylQsAHRvvKMpvtS6TXgKnvlj+NLf3DbV q9aquLHX0x3h+vYhBpNLvTWwe7mRSB6uzSg1a/hUCE1/SVrtI4k= =Ij+C -----END PGP SIGNATURE-----