Pipewire DMA & EGL hardware support (Wayland/x11 grabber) #556
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
awawa-dev
force-pushed
the
pipewire_hardware
branch
from
dda5e54 to
38d29a4
Compare
This was referenced Apr 29, 2023
Closed
awawa-dev
changed the title
|
I tried this branch, no success for me. I can use USB capture but not screen grabbing. Kubuntu 23.04 x64 If you need more info please let me know... And yes I ran this as user and not as service or from the terminal. |
|
Hi |
|
Please ignore the comment that I deleted, I was logged in to an X server session. The log in the comment thats still there is correct. |
|
Attempt number 2: here is the output from launching from terminal: |
|
Again: no restoration token and CreateSession failed. Were you asked to allow the screen capture (some kind of dialog should popup)? In this logs the situation is completly different than in the first one. |
|
I think I know what window you mean. The one where you can select which window to record? It does not appear. |
|
Are you logged in the Wayland session (locally) and run HyperHDR from terminal like |
|
Yes, I'm in Wayland. I selected the Wayland session at the login screen and I logged out and back in and this time I did get the window selection pop-up. Screen grabbing still not working tho. |
|
In logs everything is fine. What do you see in the HyperHDR live preview? |
What live preview do you mean? Where can i find it? |
|
This one?
|
|
No, icon in left menu, top, under HyperHDR logo. https://github.com/awawa-dev/HyperHDR/wiki/Quick-start#first-steps "live video" button should be enabled - green. Make sure in the "Remote control" left menu item that the software capturing is also working (priority 245 should be active). |
|
On the remote control page there is no mention of software capturing, even though screen capture is enabled. I got the pipewire popup dialog to select a screen and the system tray icon says screen casting is enabled.
|
|
Screen capturing works OK, but the pipewire stream provides only black frames: nvidia symptom described in the PR info. Otherwise you would see the 'Rainbow swirl' background effect in the live preview. |
|
Okay so the problem is the crappy Nvidia drivers? Wouldn't be the first time... |
|
I will test it on my PC with gfx1060 later using your configuration. Maybe I will find out some workaround. |
|
Awesome, thanks. |
|
Did you follow any specific steps to install the NVidia drivers on your KUbuntu? My gtx1060 is out of luck. |
|
Seems |
|
I just installed IDK what DMA is but $ apt list --installed | grep nvidia
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
libnvidia-cfg1-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
libnvidia-common-535/lunar-updates,lunar-updates,lunar-security,lunar-security,now 535.54.03-0ubuntu0.23.04.2 all [installed,automatic]
libnvidia-compute-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
libnvidia-compute-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 i386 [installed,automatic]
libnvidia-decode-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
libnvidia-decode-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 i386 [installed,automatic]
libnvidia-egl-wayland1/lunar,now 1:1.1.10-1 amd64 [installed,auto-removable]
libnvidia-encode-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
libnvidia-encode-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 i386 [installed,automatic]
libnvidia-extra-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
libnvidia-fbc1-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
libnvidia-fbc1-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 i386 [installed,automatic]
libnvidia-gl-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
libnvidia-gl-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 i386 [installed,automatic]
nvidia-compute-utils-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
nvidia-dkms-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
nvidia-driver-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed]
nvidia-firmware-535-535.54.03/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
nvidia-kernel-common-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
nvidia-kernel-source-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
nvidia-prime/lunar,lunar,now 0.8.17.1 all [installed,automatic]
nvidia-settings/lunar,now 510.47.03-0ubuntu1 amd64 [installed,automatic]
nvidia-utils-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
nvidia-vaapi-driver/lunar,lunar,now 0.0.8-1 amd64 [installed]
xserver-xorg-video-nvidia-535/lunar-updates,lunar-security,now 535.54.03-0ubuntu0.23.04.2 amd64 [installed,automatic]
|
|
This package was definitely missing from my new KUbuntu 23.04 install (I chose a minimal & no-proprietary drivers setup and installed the drivers later). Yesterday I tested it and had some success with NVidia, but:
|
|
@awawa-dev This is working for me so far on an AMD 5700XT and fairly recent mesa drivers. I am running |
|
Can someone a quick overview which preconditions/packages need to be installed to test this on Intel? |
|
@fightforlife Pipewire and x11 only work in desktop environments that implemented them, e.g. supposedly Gnome |
awawa-dev
force-pushed
the
pipewire_hardware
branch
3 times, most recently
from
2defb7f to
939cc29
Compare
awawa-dev
force-pushed
the
pipewire_hardware
branch
from
939cc29 to
e061f34
Compare
awawa-dev
added a commit
that referenced
this pull request
Oct 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for hardware capturing (video Direct Memory Access buffers) and acceleration (including non-linear tiled or compressed formats EGL decoding) to already implemented software capturing using Pipewire/Portal Linux screen grabber. Should extend the compatibility and reduce the CPU load.
NVidia users please read it: #556 (comment)
Its correct operation, of course, depends on quality of Pipewire and gfx driver support. Based on my tests, Intel was the best here, NVidia was the worst depending on the version of the drivers (for some versions e.g. only black image as a result). Portal authorization should already work in most distributions as over time Portal version 4 protocol has been fully implemented for most desktop environments. There was also an issue with Pipewire's stream auto-resume: the stream was interrupted when the application, for example, switched to fullscreen or a screensaver was activated, yet pipewire did not initialize the auto-resume later and even the application did not receive any events that indicate problems (didnt retested it from some time so don't know if they fixed it).
Currently more detailed logging is available when you run HyperHDR from the console.
Latest pipewire should work with x11 sessions also (Gnome).
Please share here reports of successes or problems you have encountered so that other users know about the current status of this PR.