Open Simba98 opened 2 hours ago
Threaded Lock Contention while threaded-clean thread is cleaning.
What is the actual problem here?
Well, I really want to have a way to avoid YUV420 with Xpra 6.x Windows Client.
The only h264
decoder in v6 onwards is the openh264
one: #3734
The ffmpeg decoder was removed 1.5 years ago: 20bb5f04233dc650022bc67d5904566d1b158af9
Maybe I should consider port ffmpeg from 5.x branch?
Unless you can prove that you will do the work for supporting this feature in the long term, including all the build and packaging for all platforms, I cannot merge this type of change.
Or just use 5.x client with 6.x server?
That should work.
Is this a desktop or seamless session? Setting a high enough min-quality value should let the engine decide which encoding is best and it should not use subsampling if it can be avoided. Which makes me think that the real bug is elsewhere.
Describe the bug Threaded Lock Contention while threaded-clean thread is cleaning. So that NVENC failed and fallback (see below)
Reason why I notice that: See https://github.com/orgs/Xpra-org/discussions/4343#discussioncomment-10554736 I set the parameter of
--min-quality=100
on client side, but even that, theYUV420
downsampling will still appears so that I can not see rectangle clearly.To Reproduce Steps to reproduce the behavior:
xpra start :A_DISPLAY -d video,cuda
Xpra_cmd.exe attach ssh://Server/A_DISPLAY --min-quality=100
System Information (please complete the following information):
Debug Code Change https://github.com/Xpra-org/xpra/blob/v6.2.x/xpra/codecs/nvidia/cuda/context.py#L524 To the following: (And import threading and also change slots)
Additional context
Extra Comment Well, I really want to have a way to avoid YUV420 with Xpra 6.x Windows Client. But now the H264 with YUV444 is not supported on Xpra 6.x Windows Client. Maybe I should consider port ffmpeg from 5.x branch? Or just use 5.x client with 6.x server?