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 AA14042401 for ; Mon, 17 Jan 2022 14:12:44 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 0FB7468B00F; Mon, 17 Jan 2022 16:12:42 +0200 (EET) Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com [209.85.210.42]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 9240A68AF6F for ; Mon, 17 Jan 2022 16:12:36 +0200 (EET) Received: by mail-ot1-f42.google.com with SMTP id g1-20020a9d6481000000b00592d01f2b6eso15831990otl.5 for ; Mon, 17 Jan 2022 06:12:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=pqyt5kKtuNCbOfB5xQmvrzrwGOXeSnFw5AkfuOWLJT0=; b=WOkPLpdGuRbiFb7wVO2lnZVCWUKshF1O+wJG1lodTSH1mx+Gr68AaA7lACK4g8ZP/y 9gkVnFK6cHPVt3zIlhzSuriTbEjAaaubPB6q+spqOKf5K+rlYK5CCU7yTk+kDH6HXeUA 7jE7oxv9WhmqGOnVLxBHcYKS7r3g1m2aaQNbo2L+1EhsJ24dSlrIfu7HKzycgIVak2we csdtOR8+KUZwU+8gnpoXyS6SuHngMqMbyQRDHx4e3Le/evkWRcPhNXX8riNOD0YjRV4b pmeuziSlHjqJzjoBBoMCMKrtUGgY5rCtMC+6oLQJjXaZcV6s8SF1jVRqa4ZwHGNPDLRd TsWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=pqyt5kKtuNCbOfB5xQmvrzrwGOXeSnFw5AkfuOWLJT0=; b=4mpUkIOG7ZjJHGlIjvKE+Ud5iJUnrjtXUY2sO31Iq1wRB0HM/24a0rMFq61AGniuvT iJcZII0Qd2m5Bl0s4KTK4eDq822D1KO9bwW0UvVkT6PrTPVXZzYlwL/LboOIKsF6sxNF S/+k2JtRNnxlGeR2YCxzHzcFlrwuY+ZQNJKh96mkVET5w1IN3j5kwZJ0c9fmdmsYcnEk U9i1g58zb4UtScSwvykb1UTdrgmBY97k6uNTCwavmabhtNSLBG1ZUGLRl4tQPOiiS9uU nbygg+JuL6cxUf5X1XX+g/mYUubjXxGkP3FsoJvFZUQ3gzqWEtcCd4u0CR1EysOLmB4r OiFg== X-Gm-Message-State: AOAM533dCWDf6C5hcur/sUc8lwkGuxmqLCl63Qu9tJ9cYgKnKpQEJWHu vER/22NXuomLvqt7KXRmWj1pfNUWMTo= X-Google-Smtp-Source: ABdhPJwZJc7SNg261b5/cg6YrV4MMkplfsFs9nVD0m9gyDXQVPqD4SGeMwQn14XVTf1my9gXGOnXyw== X-Received: by 2002:a9d:5d05:: with SMTP id b5mr15897725oti.306.1642428754733; Mon, 17 Jan 2022 06:12:34 -0800 (PST) Received: from [192.168.0.13] ([186.136.131.95]) by smtp.gmail.com with ESMTPSA id g7sm5275607oon.27.2022.01.17.06.12.33 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 17 Jan 2022 06:12:34 -0800 (PST) Message-ID: <0b212a73-4bdf-1d52-35cc-79b7cde6a4ce@gmail.com> Date: Mon, 17 Jan 2022 11:12:31 -0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Content-Language: en-US To: ffmpeg-devel@ffmpeg.org References: <20220113015101.4-1-jamrial@gmail.com> <20220113015101.4-2-jamrial@gmail.com> From: James Almer In-Reply-To: Subject: Re: [FFmpeg-devel] [PATCH 001/281] Add a new channel layout API 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 1/17/2022 10:51 AM, Nicolas George wrote: > James Almer (12022-01-17): >> And they can if they want to. It has a very specific purpose and it fulfills >> it. > > Just be clearer in the documentation. > >> Please, stop asking for this. It's an incredibly niche usecase you want for >> libavfilter, so you can and should implement it there. The API is there and >> you can use it, you don't need to overdesign these general purpose helpers >> to create these bizarre scenarios just to remove one or two filters from >> your chain. > > I will not stop asking for this, it is not specific to libavfilter: with > a quick search, I spot -map_channel that requires exactly the same > feature. -map_channel works perfectly with the current bitmask API, and the new one. > > There may be filters that require an option to distinguish one channel > in particular; even if there are no now, there may be in the future. Can > you guarantee it does not and will not happen? Look at their IDs? Look at their names? Give them names if you need to? And again, you keep talking about filtering scenarios. Lavfi can and should handle all this on its own internally, just like it was designed to, and not pollute an API meant to define the position a channel is supposed to be. > > This use case happens at several places, therefore the parsing belongs > in a common API. > > Regards, > > > _______________________________________________ > 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". _______________________________________________ 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".