-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new h264 codec implementation causes virtual screen tearing #4191
Comments
These do not look like any valid versions. |
fixed versions |
How do you configure that? Does it go away if you turn off opengl? |
Server has version Client has either the same or updated version Connection established either on local Lan via 5g wifi, or via wireguard vpn, both are working without big difference
I force specific encoding, because otherwise picture quality is very unstable and laggy |
Forcing an encoding is not how you fix whatever issues you are having, please refer to the documentation, which is plentiful. Try
|
UPD.: |
So I fail to see how this can have anything to do with new h264 codec implementation in this ticket summary. |
yeah, i know, that forcing encoding is not intended way of fixing, but that's what works in practice fixing according to documentation did not provide me the result i was satisfied with, so i went the path of try&error also rdp protocol uses h264 and it had awesome quality, so i decided to just force something similar in the end if you're interested, my setup is not following documentation either, i have server nvidia tesla gpu and i'm using xpra with GPU acceleration not with |
Maybe the encoder side is having an effect on the |
should
be used on server side or the client? client side usually has either integrated amd gpu or some other random one p.s.: i removed my testing setup for now, so i'll not be able to test it for now |
server. |
well, it has nvenc as availible one, but using |
I suppose, it would be kinda useful if i share my full configuration with you |
Defined is not necessarily the same as available, but it usually is.
Yes, that's expected.
Sounds like: https://github.com/Xpra-org/xpra/blob/master/docs/Usage/OpenGL.md#taking-over-an-existing-display |
kind of, but it's created directly by xpra |
Could be related to #4201, as it seems to be somehow worse with OpenGL enabled and with newer versions. |
I assume that this is #4201 |
version from aur
xpra-git
(4.4.r3230.g402c9173e-1 => 4.4.r3624.g05f6559850-1)
xpra v6.0-r35166 (g402c9173e) beta => xpra v6.0-r35559 (g4429944651) beta
caused screen tearing with encodings:
avif, h264, scroll
(others were not tested, because they were laggy on previous versions as well)
rolling back to previous build fixed the issue
The text was updated successfully, but these errors were encountered: