From: Quack Doc <quackdoctech@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] libavfilter: add PipeWire-based grab
Date: Fri, 2 Aug 2024 12:11:19 -0400
Message-ID: <CALRFuf4OR1TpwoFesme_ndb8tbMsqcujzu6_efr7aTfeGz+B+Q@mail.gmail.com> (raw)
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 directly as well without needing portals, which allows
ergonomically letting multiple apps accsess v4l2 devices for instance like
firefox and say discord. So being able to support the file descriptor
directly, or using target-object much like the pipewiresrc gstreamer would
be greatly appreciated.
Many XDG portals are not limited to systemd either. However as long as we
can provide a file descriptor at the very minimum a small python script can
be used to get the file descriptor.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next reply other threads:[~2024-08-02 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 16:11 Quack Doc [this message]
2024-08-02 19:41 ` François-Simon Fauteux-Chapleau
2024-08-04 20:11 ` Quack Doc
2024-08-06 15:34 ` François-Simon Fauteux-Chapleau
2024-08-06 16:39 ` Quack Doc
2024-08-07 3:00 ` Quack Doc
2024-08-07 17:29 ` François-Simon Fauteux-Chapleau
-- strict thread matches above, loose matches on Subject: below --
2024-07-28 14:53 Quack Doc
2024-07-30 19:53 ` François-Simon Fauteux-Chapleau
2024-08-01 7:44 ` Anton Khirnov
2024-08-01 11:34 ` Rémi Denis-Courmont
2024-05-10 21:12 François-Simon Fauteux-Chapleau
2024-05-11 14:08 ` Andrew Sayers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALRFuf4OR1TpwoFesme_ndb8tbMsqcujzu6_efr7aTfeGz+B+Q@mail.gmail.com \
--to=quackdoctech@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git