> Sorry for the ambiguity in my previous reply. The answer is yes: the current
> version of the patch will try to use the XDG portal unless a file descriptor
> is provided. The "node" option was meant to be used together with the "fd"
> option, not as an alternative to it. So when I said that I tho
1280x960
[Parsed_pipewiregrab_0 @ 0x647dc471c440] Framerate: 60/1
[Parsed_pipewiregrab_0 @ 0x647dc471c440] stream state: "error"
[Parsed_pipewiregrab_0 @ 0x647dc471c440] PipeWire core error: error
alloc buffers: Invalid argument (id=2, seq=15, res=-32: Broken pipe)
On Tue, Aug 6,
ode:
-22 (Invalid argument)
[vost#0:0/h264_vaapi @ 0x55cf4db38080] Terminating thread with return
code -22 (Invalid argument)
[out#0/mp4 @ 0x55cf4db37800] Nothing was written into output file,
because at least one of its streams received no packets.
On Fri, Aug 2, 2024 at 3:41 PM François-Simon Fau
Pipewire video capture is more generic. Some compositors like weston
support pipewire as a backend without portals. Gamescope also creates a
pipewire output without need for portals, it would be *really* nice to
support gamescope capture with this. Pipewire also gives access to video
devices direct
Is it possible to use this without using the portals API and without
systemd? That would be much appreciated if so since the portal is not very
flexible. As for systemd it would be great to be able to use this on
non-systemd platforms.
___
ffmpeg-devel ma
