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 7F15F492D9 for ; Wed, 7 Feb 2024 10:31:46 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 43C1368D0F2; Wed, 7 Feb 2024 12:31:44 +0200 (EET) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id BB4C868CDFB for ; Wed, 7 Feb 2024 12:31:37 +0200 (EET) Authentication-Results: mail0.khirnov.net; dkim=pass (2048-bit key; unprotected) header.d=khirnov.net header.i=@khirnov.net header.a=rsa-sha256 header.s=mail header.b=o58mp71l; dkim-atps=neutral Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id 723FD240DA9 for ; Wed, 7 Feb 2024 11:31:37 +0100 (CET) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavis, port 10024) with ESMTP id 0A_f5diW0JuC for ; Wed, 7 Feb 2024 11:31:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=khirnov.net; s=mail; t=1707301896; bh=r0P10iVCWXKjoenRbFjH4LSvo9kkAMx1TgsoUnyAH/8=; h=Subject:From:To:In-Reply-To:References:Date:From; b=o58mp71l7ywgnHIHmHd/8UrqmGOf2kf63Wvw2Qf1eL4SsPqibDmZDQDaclMeNB85B Lv69baez14t7cy2Lt5G2iP7SroAZry6fuhs4KNAa7FzBnAuF0sZFbAYKk9XcyKqjfH 8s1dmAEA1gt2ZbNRNYDY7b2y0o1Sxzn/A+kU2QDDsrjUipPTYBn3SexMJJFw4m79HU fCq2FIgWYmkxs53yKniWkaN+BpT0lKdmuWLPrtb4+Byt+2UEzMAVM465W4vCU97xzB t7JFoU69SaJdDaMCqrnb4eThtgOS8an/2NkLXa19hUcK0Pu32jm/82C6XrtMPeL2iJ 2uEDnZhmLbcuA== Received: from lain.khirnov.net (lain.khirnov.net [IPv6:2001:67c:1138:4306::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "lain.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id CD605240177 for ; Wed, 7 Feb 2024 11:31:36 +0100 (CET) Received: by lain.khirnov.net (Postfix, from userid 1000) id A4E001601B9; Wed, 7 Feb 2024 11:31:36 +0100 (CET) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: References: <20240204090233.1157950-1-jdek@itanimul.li> Mail-Followup-To: FFmpeg development discussions and patches Date: Wed, 07 Feb 2024 11:31:36 +0100 Message-ID: <170730189664.8914.8494485144453684698@lain.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH 0/2] Remove SDL2 output devices 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: Quoting Marton Balint (2024-02-04 11:11:12) > > The 'pipe:' output can be used with a real video player such as mpv, vlc, or > > even ffplay. For cases where the user was an application using the API they > > should supply their own renderer. > > Yeah, but I never liked when people piped uncompressed data... Not > everything that the devices support can be serialized, For instance? What do these devices support that e.g. NUT does not? > it is extra CPU, latency of the receiving app reading from pipe is a > question... People keep saying this in defence of these devices, but never support such claims with any data. I have doubts this is an actual problem in practice. > I'd be a lot more happy with this if we'd offer some replacement which has > no issues. Maybe a libplacebo based outdev. I don't think it's possible to have such a replacement, neither should we try. Muxer API is simply the wrong abstraction for playback. -- Anton Khirnov _______________________________________________ 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".