From: Quack Doc <quackdoctech@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] libavfilter: add PipeWire-based grab
Date: Tue, 6 Aug 2024 23:00:13 -0400
Message-ID: <CALRFuf42PyYLAxTNjESNUQtpqO6F9EUUBz=vPx1ojVMYpOk5_Q@mail.gmail.com> (raw)
In-Reply-To: <886200727.588674.1722958477137.JavaMail.zimbra@savoirfairelinux.com>
> 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 thought these
> options could be used to bypass the portal, I should have specified I was
> thinking of the case where FFmpeg is used by a program as a library (which
> is what we're doing at my company); we'll need a different solution if we want
> this to work when using the command-line tool. Sorry again for the confusion.
For a POC I commented out the fd stuff so it wouldn't fail on me and
replaced pw_context_connect_fd() with pw_context_connect() and it
seemed to work fine with gamescope, gamescope only produces RGB frames
and not YUV frames however. I did try my camera and it did not seem to
work, which is more or less what I had expected.
perhaps a couple simple if statements would be good enough and adding
YUV formats?
also Looking at it, it seems like this only supports 8bit formats?
Though it didn't make my capture fail despite my monitor running in
10bit so perhaps pipewire can handle that itself?
_______________________________________________
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 prev parent reply other threads:[~2024-08-07 2:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 16:11 Quack Doc
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 [this message]
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='CALRFuf42PyYLAxTNjESNUQtpqO6F9EUUBz=vPx1ojVMYpOk5_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