From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 1308F474E0 for ; Tue, 6 Aug 2024 15:34:50 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id D081868D5FF; Tue, 6 Aug 2024 18:34:46 +0300 (EEST) Received: from mail.savoirfairelinux.com (mail.savoirfairelinux.com [208.88.110.44]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 8048568D5FF for ; Tue, 6 Aug 2024 18:34:39 +0300 (EEST) Received: from localhost (localhost [127.0.0.1]) by mail.savoirfairelinux.com (Postfix) with ESMTP id C5D939C5B9D for ; Tue, 6 Aug 2024 11:34:37 -0400 (EDT) Received: from mail.savoirfairelinux.com ([127.0.0.1]) by localhost (mail.savoirfairelinux.com [127.0.0.1]) (amavis, port 10032) with ESMTP id jO1pHEtWoecK for ; Tue, 6 Aug 2024 11:34:37 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.savoirfairelinux.com (Postfix) with ESMTP id 552EB9C5DD7 for ; Tue, 6 Aug 2024 11:34:37 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.savoirfairelinux.com 552EB9C5DD7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=savoirfairelinux.com; s=DFC430D2-D198-11EC-948E-34200CB392D2; t=1722958477; bh=9BmnQYonQS7H0RzSVUf2KuCwQ+g9NTJNQ4i7ts5ZbLU=; h=Date:From:To:Message-ID:MIME-Version; b=Wrm9JrLlPNpb/E2Y8lZuytQ3k/e6Xc/00IzCeKx/QItITTaJfgGo4OS6ppzOiNH1r tzV4U/Oww2Y8kdXCWKyuzNVXGx+ElGt1zpHatEK61MQ1nuZoBE//DunPFHeRGn7SeN K+jY+g46Spec35kNsNuZLvfgFb6PbrKQqkFSMGM+tJMKdYOXWOdm2TFWzhlUbNVWPR 90rYtQtydUyXZ5FglI/Xo5Hasw26OsIMbAsyIl87A/HXUKqDjRFKpnuJINTq93HuFp 7NarPNJf4ni/tAHf3XBjxeQoY5oh8XXnZnKhSrDSog37lm3d/RuTe0zVMAupvrjsIs cOuQnf3wwwGtg== X-Virus-Scanned: amavis at mail.savoirfairelinux.com Received: from mail.savoirfairelinux.com ([127.0.0.1]) by localhost (mail.savoirfairelinux.com [127.0.0.1]) (amavis, port 10026) with ESMTP id XaVPNVjQBD-l for ; Tue, 6 Aug 2024 11:34:37 -0400 (EDT) Received: from mail.savoirfairelinux.com (mail.savoirfairelinux.com [192.168.48.237]) by mail.savoirfairelinux.com (Postfix) with ESMTP id 36CF99C5B9D for ; Tue, 6 Aug 2024 11:34:37 -0400 (EDT) Date: Tue, 6 Aug 2024 11:34:37 -0400 (EDT) From: =?utf-8?Q?Fran=C3=A7ois-Simon?= Fauteux-Chapleau To: FFmpeg development discussions and patches Message-ID: <886200727.588674.1722958477137.JavaMail.zimbra@savoirfairelinux.com> In-Reply-To: References: <1977752609.532131.1722627661551.JavaMail.zimbra@savoirfairelinux.com> MIME-Version: 1.0 X-Mailer: Zimbra 8.8.15_GA_4581 (ZimbraWebClient - FF128 (Linux)/8.8.15_GA_4581) Thread-Topic: libavfilter: add PipeWire-based grab Thread-Index: zVHfjNPwi3NAVvw88g6OgT/VZfXdxw== Subject: Re: [FFmpeg-devel] [PATCH v2] libavfilter: add PipeWire-based grab X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: ----- On Aug 4, 2024, at 4:11 PM, Quack Doc quackdoctech@gmail.com wrote: > I see, I tried to pull the patch and test it. How does invocation with > node work? I'm a bit confused with the invocation. For testing I tried > using "gamescope --headless -- glxgears" to generate a raw pipewire > stream. (cameras will automatically create one with pipewire) used > "pw-dump | jq '.[] | select(.info.props["node.name"] == "gamescope") | > .id'" to get the node id and tried to use it but it still seemed to > trigger the portal. If you have a camera installed I use the below > command to dump all of the video sources, gamescope and cameras > included > > pw-dump | jq '.[] | select(.info.props["media.class"] == > "Video/Source") | .info.props."node.name" + " | " + > .info.props."node.description" + " | " + (.id|tostring)' > > does the current patch have a hard requirement on file descriptors to > not use xdg? 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. > I did also test xdg capture on cosmic, it seems to only sporadically > work, usually spitting out the below error. I can spam it to keep > retrying it until it works > > [Parsed_hwmap_0 @ 0x79fabc003600] Mapping requires a hardware context > (a device, or frames on input). > [Parsed_hwmap_0 @ 0x79fabc003600] Failed to configure output pad on > Parsed_hwmap_0 > [vf#0:0 @ 0x55cf4daff480] Error reinitializing filters! > [vf#0:0 @ 0x55cf4daff480] Task finished with error code: -22 (Invalid argument) > [vf#0:0 @ 0x55cf4daff480] Terminating thread with return code -22 > (Invalid argument) > [vost#0:0/h264_vaapi @ 0x55cf4db38080] Could not open encoder before EOF > [vost#0:0/h264_vaapi @ 0x55cf4db38080] Task finished with error code: > -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. Does it work reliably if you don't try to use hardware acceleration? (You'll have to set the "enable_dmabuf" option to 0 for that.) _______________________________________________ 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".